x402-triage-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| triage_x402_surfaceA | Run a no-payment external pass against one public x402, MPP, Pay.sh, OpenAPI, manifest, or HTTP 402 endpoint. The tool calls the Tate Programs public triage API and returns status, payment headers, parsed challenge shape, attack-class checks, cache/CORS notes, and paid review handoff. It does not send X-PAYMENT, wallet signatures, API keys, private tokens, or paid calls. |
| watch_402_indexA | Look up public 402 Index service records by provider, domain, endpoint URL, or search term. Use this before listing, outreach, launch review, or re-check work to spot down services, invalid payment requirements, and unverified domains. This is public metadata only and does not send payment headers or paid calls. |
| x402_paid_pathsA | Return the Tate Programs paid x402 API endpoints, service catalog, AgentCard, and fixed-scope review handoff URLs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| usage | How to use x402-triage-mcp safely. |
TDQS
Scored across 3 tools
Each tool targets a distinct function: triaging a live endpoint, looking up public index metadata, and retrieving paid service paths. There is no overlap in purpose or output.
The naming convention is inconsistent: triage_x402_surface and watch_402_index follow a verb_noun pattern, but x402_paid_paths is a noun phrase. Additionally, the use of 'x402' vs '402' varies across tool names.
Three tools is well-scoped for a specialized triage service, covering the core actions without redundancy. Each tool earns its place in the set.
The set covers the main workflows: triage, index lookup, and paid path discovery. Minor gaps exist such as not offering a way to update index records, but these are likely external concerns.