x402-mcp-server_by_milza
Related Servers
Alternatives to x402-mcp-server_by_milza
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceProduction-grade Model Context Protocol (MCP) server delivering paywalled Web3 micro-services powered by autonomous x402 payment challenges on Base Mainnet.-
- AlicenseNot gradedqualityBmaintenanceMCP server that lets AI agents scrape web pages as clean markdown for a micro-payment in USDC, using the x402 protocol on Base network. No API keys or signup required.MIT
- FlicenseNot gradedqualityBmaintenanceA small, autonomous, pay-per-call MCP server that AI agents discover and pay for per call, with revenue landing directly in a USDC wallet on Base via the x402 payment protocol.-
- AlicenseNot gradedqualityCmaintenanceMCP server that provides AI agents with pay-per-call access to a suite of tools (honeypot check, token market, DeFi yields, etc.) via USDC on Base using the x402 protocol.1 npmMIT
- AlicenseAqualityBmaintenanceMCP server for the CortexCloud API, enabling pay-per-call AI generation, web search, market data, and blockchain RPC endpoints via the x402 protocol, billed in USDC on Base without API keys or subscriptions.412 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server providing 11 pay-per-call web intelligence tools (page reading, PDF extraction, RSS parsing, screenshots, summarization, structured data extraction) for AI agents, paid automatically in USDC via the x402 protocol on Base mainnet with no API keys required.19 npmMIT
TDQS
Scored across 4 tools
Each tool targets a distinct domain: secret vaulting, markdown extraction, SPA rendering, and SVG chart generation. There is no functional overlap between any pair of tools.
Names are descriptive and readable, but they do not follow a single verb_noun or noun_verb pattern. Three use hyphenated noun phrases (burn-once-secret-vault, spa-dom-to-md, svg-bar-chart-renderer) while one uses a noun-noun compound (markdown-extractor).
Four tools is a reasonable, focused set for a paid utility server. It is slightly thin for a general-purpose toolkit, but each tool is substantial and earns its place.
The tools are independent utilities rather than a CRUD domain, so completeness is hard to assess. Each tool appears self-contained for its stated purpose, but the set lacks any broader workflow cohesion and there is no obvious way to manage or inspect the x402 payment side.