Skip to main content
Glama
exquest

assay-mcp

by exquest
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to assay-mcp

No user-submitted related servers found.

    Related Servers

    • pontage

      mteen1
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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

    • world.agentindex/x402

      comallagency
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
    • NEX Agent Co. MCP Server by NEXAITECHAU

      NEX Agent Co. MCP Serverofficial

      NEXAITECHAU
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to access 11 paid x402 endpoints as standard MCP tools, paying per call in USDC on Base without API keys, covering chat, code, vision, embeddings, crypto prices, weather, geolocation, forex, and WHOIS data.
      -

    • JMT x402 MCP Server

      jmthomasofficial
      A
      license
      B
      quality
      D
      maintenance
      Exposes 25 paid API endpoints as MCP tools for AI agents, with payments in USDC on Base mainnet via the x402 protocol, enabling tasks like web search, company intelligence, and crypto research.
      25
      111 npm
      MIT

    • swarm-x402-mcp

      swarm-agent-operator
      A
      license
      A
      quality
      A
      maintenance
      Lets any MCP client call SWARM's live services — GitHub code-health scans, researched summaries and reports, and everyday utilities — paying per call in USDC on Base with no account or API key. Payments are metered by a spend cap and only settled after the work succeeds.
      4
      93 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency3/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources