@hpp-io/x402-mcp-bridgeofficial
A
licenseNot graded
qualityB
maintenanceEnables AI agents to autonomously pay for and discover services using HPP USDC.e over the x402 protocol, without API keys or manual signing.
421 npm
Apache 2.0
@bridgenode/mcp
OfficialRelated Servers
Alternatives to @bridgenode/mcp
- AlicenseAqualityBmaintenanceEnables AI agents to discover and pay for x402-gated HTTP APIs, handling 402 Payment Required flows with local signing. Supports EVM and Solana with non-custodial wallet management.3337 npmMIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to make micropayments using USDC on Solana via the x402 protocol, supporting payment requests, on-chain verification, and revenue tracking.MIT
- AlicenseNot gradedqualityCmaintenanceEnables autonomous AI agents to make policy-gated Solana micropayments, fetch x402 paid APIs, send SOL/USDC, and perform Jupiter swaps using an isolated burner wallet with enforced spend limits.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to check their wallet address and USDC balance, preview the cost of an x402 call, and pay for API requests in USDC on Base without an account or API key. Spend caps, allow-lists and blocked contracts are enforced in code before anything is signed, so a prompt injection cannot bypass them.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to make pay-per-call USDC payments on Base via x402 for headless page rendering, temporary file hosting, scheduled callbacks, and pump.fun launch and trend feeds.MIT
- AlicenseAqualityDmaintenanceEnables AI agents to access Solana wallet analytics, token data, and DeFi tools via pay-per-request USDC micropayments using the x402 protocol, without API keys or subscriptions.1369 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to securely access x402-protected APIs on Base L2 with automatic USDC payments under deterministic spending limits, domain and contract allowlists, transaction simulation, and audit logging.4128 npmMIT
TDQS
A4.7/5.0
Scored across 3 tools
Disambiguation5/5
Each tool has a clearly distinct role: list_models returns the catalog, get_price_estimate prices a specific request, and chat_completions performs inference. The descriptions explicitly cross-reference each other ('use chat_completions', 'use get_price_estimate'), eliminating any realistic misselection.
Naming Consistency4/5
get_price_estimate and list_models follow a clean verb_noun pattern, but chat_completions is a bare noun naming a resource/action endpoint. The deviation is minor and the naming remains predictable and readable.
Tool Count4/5
Three tools is lean but plausibly matches the narrow gateway scope: inspect models, estimate cost, generate text. It sits at the low edge of the ideal range, with little redundancy, though it leaves almost no room for ancillary operations.
Completeness4/5
The core pay-per-request lifecycle (discover models, price a request, execute) is fully covered, including the 402 payment retry flow. Minor gaps exist: no streaming option, no balance/usage or payment-status tool, and no embeddings or other model modalities.
Maintenance
ActivityNo data
ResponsivenessOutdated data