Skip to main content
Glama
Sign In
vet402

vet402

by kzmttkc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to vet402

No user-submitted related servers found.

    Related Servers

    • RouteX402

      msurfx
      A
      license
      A
      quality
      B
      maintenance
      This MCP server provides verified payment reputation for AI agents operating on Solana. It allows users to ask AI models to check the reliability of a seller before proceeding with a payment.
      2
      370 npm
      MIT

    • robotsshop-mcp

      AnalogHubris
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for verifying agent payment integrity on x402, providing tools to check payTo mismatches, market stats, and lookup endpoints.
      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
      20 npm
      MIT

    • 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
      20 npm
      1
      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.6/5.0

    Scored across 7 tools

    Disambiguation2/5

    Three tools — check_agent_trust, check_wallet_trust, and check_payee_trust — all perform essentially the same address/agent trust lookup, and their descriptions repeat the identical "decide on decision and safe_to_pay" boilerplate rather than drawing a clear boundary. check_resource_decision also overlaps with all three while adding policy, leaving an agent unsure which entry point to use. Only explain_trust_score, attest_x402_payment, and pay_if_trusted are clearly distinct.

    Naming Consistency4/5

    All names are snake_case with a leading verb (check_*, explain_*, attest_*, pay_if_*), which reads predictably. Minor deviations like pay_if_trusted (conditional phrasing) and attest_x402_payment (embedded protocol token) are still legible and do not break the pattern.

    Tool Count5/5

    Seven tools is well within a comfortable range for a trust-gating server, and each remaining tool (explain, attest, decide, pay) maps to a distinct stage of the x402 flow. The only count concern is redundancy among the three check_* tools, not raw volume.

    Completeness4/5

    The surface covers check → explain → attest → decide → pay, which is the full payment-gating lifecycle. Gaps exist around reading back attestations or querying score history, but an agent can work around them via the check tools.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled

    Resources