Skip to main content
Glama
Sign In
x402 Discovery & Trust MCP

x402 Discovery & Trust MCP

by JonasFuchss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

x402 Trust leaderboard

x402_trust_leaderboard

Rank x402 hosts by measured trustworthiness across their full surface; page through the list so agents can assess reputation before paying.

Instructions

Top-100 ranking of the most trustworthy x402 hosts, scored by their whole measured surface. Page with offset, then use x402_search to list a host's endpoints.

Input Schema

NameRequiredDescriptionDefault
limitNoPage size (1-25, default 25)
offsetNoSkip this many ranked hosts for the next page (default 0). The board holds at most 100 hosts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.15.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Page size (1-25, default 25)",
+  "maximum": 25,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Skip this many ranked hosts for the next page (default 0). The board holds at most 100 hosts.",
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the behavioral burden. It discloses the 100-host cap and pagination nature, but does not state that this is a read-only operation, whether any auth is required, or what 'whole measured surface' scoring actually means. Adequate for a low-risk read listing, but thin given zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with what the tool returns, followed by the pagination mechanic and the sibling handoff. No filler, no repetition of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should hint at the return shape; it conveys 'ranking ... scored' but not which fields (host, score, rank) come back. Combined with the missing read-only/auth disclosure, it is nearly complete for such a simple paginated listing but leaves minor gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% – both limit and offset are already documented, including the 1-25 bounds and the 100-host board size. The description's 'Page with offset' adds no syntax or format detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: a ranked top-100 list of trustworthy x402 hosts. It distinguishes itself from siblings like x402_trust_score (single host score) and x402_trust_preview by describing a cross-host leaderboard, so an agent can route correctly without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear usage context ('Page with offset') and explicitly routes follow-up work to x402_search for a host's endpoints, which is a real alternative for adjacent intent. It stops short of stating when to prefer the leaderboard over x402_trust_score or x402_trust_preview, so no explicit exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools