Skip to main content
Glama
Sign In
RouteX402

RouteX402

by msurfx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to RouteX402

No user-submitted related servers found.

    Related Servers

    • trust-mcp

      Schmoll86
      A
      license
      A
      quality
      D
      maintenance
      MCP server for AI agent trust verification, enabling agents to verify identities, check trust scores, and build reputation across multiple blockchain and web platforms.
      12
      15 npm
      1
      MIT

    • trust-mcp

      BillyTheManBot
      A
      license
      A
      quality
      D
      maintenance
      MCP server that enables AI agents to verify each other's trust scores, register, submit reviews, and find trusted agents before transacting.
      4
      15 npm
      MIT
    • acuris-agent-guard

      acuris-agent-guardofficial

      Acuris-GmbH
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that verifies storefront merchants before AI agents make payments, checking if the merchant is a real legal entity bound to the domain, and returning a PROCEED, ABORT, or REVIEW decision to prevent payment to clones or fraudulent stores.
      MIT

    • token-rugcheck

      AetherCore-Dev
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server for real-time Solana token risk analysis. Cross-references RugCheck.xyz, DexScreener, and GoPlus Security to generate three-layer reports: machine verdict → LLM analysis → raw on-chain evidence. Live on Solana mainnet with USDC micropayments ($0.02/audit). Give any AI agent the ability to check if a token is safe before trading.
      2
      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.8/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one performs a targeted lookup for a specific agent, while the other returns a ranked discovery list. An agent can easily choose between checking a known seller and browsing top sellers.

    Naming Consistency5/5

    Both names follow a consistent snake_case verb_noun pattern: check_agent_reputation and list_top_agents. The verbs and object nouns are predictable and readable.

    Tool Count3/5

    Two tools is thin for a reputation/discovery server, even if both are useful. It covers the two headline workflows but leaves little room for filtering, detail lookup, or supporting operations.

    Completeness3/5

    The core workflows of checking a known agent and listing top agents are covered, but the surface lacks search/filtering, detailed agent profiles or history, and any mechanism for submitting or updating reputation data. These are notable gaps for a reputation-oriented server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources