Skip to main content
Glama
Sign In
Snap Router

Snap Router

by trigeochiral
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Snap Router

No user-submitted related servers found.

    Related Servers

    • NEX Agent Co. MCP Server

      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.
      -
    • AgentBIT MCP Server

      AgentBIT MCP Serverofficial

      socialbitro
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to call 50+ pay-per-request tools covering onchain and crypto data, web research, security, compliance screening, business intelligence, and infrastructure checks. Payments settle per call in USDC on Base through the x402 protocol with no accounts, API keys, or subscriptions, and the first call is free for new wallets.
      MIT

    • SiteCheck

      bck-stack
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to call pay-per-request AI and web tools—including web-to-Markdown reading, PDF extraction, translation, compliance lookups, domain/email/Solana data, and prediction-market intelligence—without accounts or API keys, settling each call in USDC via x402 on Base, Solana, or Arc.
      MIT

    • Genesis402

      FTHTrading
      A
      license
      A
      quality
      C
      maintenance
      Pay-per-call data and tools for AI agents over x402, by UnyKorn. 360 endpoints: DeFi and market data, multi-chain wallet reads, wallet and token risk signals, SEC filings, web and domain intel, and AI text tools. Settled per call in USDC on Base ($0.001-$0.25). No API keys or subscriptions; unpaid calls return the exact quote first.
      21
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of misselection or overlap; its stated purpose (catalog discovery before loading tools) is unambiguous. An agent cannot confuse it with anything else in this server.

    Naming Consistency5/5

    The single tool follows a clean snake_case verb/resource-style name (snap_router) that matches the server name. There is no second convention to conflict with.

    Tool Count3/5

    A one-tool surface is inherently thin, even though a discovery router is arguably a single-purpose operation. The rubric treats 1-2 tools as borderline, and this sits right at that edge.

    Completeness3/5

    For a pure discovery role, the tool covers the core 'find candidates' operation, but the surface is a dead end: no way to fetch full details for a given service/tool ID, filter by price/category, or paginate the 16k-entry catalog. Agents can work around this by rerunning searches, but it is a notable gap.

    Maintenance

    ActivityStale
    ResponsivenessUnresponsive

    Resources