assay-mcp
Related Servers
Alternatives to assay-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables MCP tools to be gated behind per-call USDC micropayments with direct on-chain verification and settlement, removing the need for third-party payment facilitators.MIT
- AlicenseAqualityBmaintenanceEnables MCP-capable agents to run pay-per-call trading checks and quant tools, including pre-trade GO/CAUTION/NO_GO verdicts, futures event gates, session briefs, SEC insider-buy lookups, Base token safety verdicts, and small calculators, with automatic x402 USDC payments on Base.102,220 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to call pay-per-use tools for search, PDF processing, web reading, extraction, summarization, fact-checking, translation, jobs, and discovery, with each call paid in USDC on Base via x402 and no API key or account required.AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to perform paid claim checks, scouting, and deep dives against public URLs via x402 payments in USDC on Base, with a configurable per-call spend cap.MIT
- AlicenseNot gradedqualityCmaintenanceEnables paid access to Polymarket odds, cross-venue disagreement data, attested market data packages, and Hyperliquid funding rates through MCP tools using x402 USDC payments on Base.MIT

monospay-mcpofficial
AlicenseNot gradedqualityDmaintenancePay per MCP tool call in USDC on Base. Non-custodial settlement, no admin keys, 30 bps fee.MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: querying Base pools, verifying claims against pasted passages, and checking account/status information. There is no overlap or realistic chance of selecting the wrong tool.
All names use lowercase snake_case, but the pattern is mixed: verify_claim is verb_noun, new_base_pools is modifier_noun, and assay_status is noun_noun. The names are still readable and predictable, but they do not follow a single consistent convention.
Three tools is appropriate for this focused paid-data server: one data query, one verification action, and one status/account tool. Each tool earns its place and the count is not excessive or thin for the stated functionality.
The core interactions are covered, but new_base_pools returns only a condensed page plus a path to the full paid answer, and no tool exists to retrieve that full answer. There is also no way to fetch past results or revisit prior purchases from within the server, leaving a notable workflow gap.