x402 Universal Payer

It requires MCP_BRIDGE_EVM_PRIVATE_KEY and MCP_BRIDGE_SVM_PRIVATE_KEY, which can directly authorize on-chain payments. Combined with the stated 'auto-paying bridge' capability, leakage, misconfiguration, or induced use could lead to real fund spending. MAX_PRICE/MAX_TOTAL/ALLOWED_* settings help mitigate this, but the credentials are highly sensitive and carry a clear risk of monetary misuse.

No fixed remote host is listed, but the description indicates it can pay x402 endpoints on the open web and use Bazaar discovery. The presence of RPC_URL_8453, MCP_BRIDGE_BAZAAR_URL, ALLOWED_HOSTS, and ALLOW_HTTP also shows it may connect to discovery services, blockchain RPC, and allowed payment endpoints. This is typical network behavior for this type of tool, but host allowlists and any HTTP enablement should be reviewed carefully.

The system checks indicate that this tool executes code/spawns processes. For an MCP tool, this is a normal capability. The provided material does not show system permissions clearly beyond its stated function, nor any suspicious execution chain, but it should still be run with least privilege and in a constrained host environment.

The presence of X402_MCP_BRIDGE_CHANNELS_DIR suggests it may read/write local channel or state data. Together with private keys and spend settings, related local files may contain sensitive financial or channel information. The material does not indicate broad file-system access beyond its payment function, so this currently looks like limited local state access rather than excessive authorization.

It comes from an official registry, has a public open-source repository, and was updated within the last year, all of which are positive supply-chain signals. However, the missing README, unspecified license, and 0-star community adoption reduce verifiability and maturity confidence. Overall, supply-chain risk does not appear high, but source and dependency review is still advisable before deployment.