x402 Doctor

x402 Trust Index record (free)

x402_trust_record

Read-only

Free: the daily track record of a paid x402 or MPP endpoint from the x402 Trust Index: on how many of the last 30 scanned days an agent could pay it, the latest verdict and reasons, price and networks. found: false when it is not in the index; add your own endpoint with x402_trust_add. Limited to 10 calls per hour. Before paying, x402_preflight ($0.001) checks the live 402 and includes this record.

Input Schema

Name	Required	Description	Default
`url`	Yes	The x402 endpoint (public http(s) URL), e.g. https://api.example.com/paid

Output Schema

Name	Required	Description
`url`	Yes
`last`	No	Latest day: g go, c caution, n no_go, x unreachable
`found`	Yes	false: not in the Trust Index (see how_to_list)
`last_scan`	No	The latest verdict, reasons, price and networks
`submitted`	No	Added by its seller, not listed in a registry
`how_to_list`	No
`days_checked`	No
`days_payable`	No	Days the daily scan found it payable (go or caution)
`payable_ratio`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 29, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```

changedOutput schema / properties / last_scan / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

AddedOct 19, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Adds real context beyond readOnlyHint/openWorldHint: it is free vs the $0.001 preflight, capped at 10 calls per hour, and returns found:false rather than erroring for unknown endpoints. The only minor gap is not saying how stale the daily data can be relative to the current scan.

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

Conciseness4/5

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

One dense but front-loaded block leading with 'Free' and the resource, then constraints. Every clause carries information (cost, limit, absence case, alternatives), though the sentence is long enough that the rate limit is buried mid-string rather than set off.

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?

Given an output schema exists, the description needn't document return shape, yet it still summarizes verdict/reasons/price/networks and covers the not-found case, cost, and rate limit — everything needed to call it correctly. Only freshness semantics are left implicit.

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 coverage is 100% and the single url parameter is fully documented with an example, so the schema carries the load. The description reinforces that the target is an x402 or MPP endpoint, but adds no format or normalization guidance (e.g. trailing slash, scheme handling) beyond the schema.

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 resource (the daily track-record of a paid x402/MPP endpoint from the Trust Index) and enumerates the returned content: uptime across last 30 scanned days, latest verdict and reasons, price and networks. Names the sibling it complements (x402_trust_add for endpoints not indexed) so it is distinguishable 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?

Explicitly frames the use case (check the historical record) and routes to x402_preflight for a live pre-payment check, plus x402_trust_add when the endpoint is absent. It does not address the other near siblings (x402_quick_check, x402_delivery_check, x402_preflight_deep), so the alternative mapping is not exhaustive.

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

All x402 Doctor tools Inspect

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.