gold402-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gold402_searchA | Search the gold-402 curated directory of x402 services, MCP servers, SDKs, facilitators and tools. Every entry was hand-probed by a maintainer and answered an x402 request correctly at the time of review. Filter by free text and/or shelf; supports pagination. Returns name, URL, description, shelf and the date first listed, with a provenance stamp. |
| gold402_list_sectionsA | List the shelves (categories) of the gold-402 directory with an entry count for each. Use the returned section id as the 'section' filter in gold402_search. |
| gold402_get_entryA | Fetch a single gold-402 entry by name (exact match preferred, falls back to partial). Returns the full record including URL, description, shelf, the date it was first listed, and the permanent listing page. |
| gold402_check_endpointA | Live-probe ANY x402 endpoint — listed or not — before paying it. Sends one unpaid request and reports: whether it answered, the HTTP status, whether it returned a real 402 payment challenge, and the payment terms found (scheme, network, price, payTo, asset). Also checks the /.well-known/x402 manifest on the same origin. This is the same liveness-and-protocol check the gold-402 maintainers run at the door. It does NOT spend money and does NOT verify delivery — a valid 402 proves the door works, not that the service is good. |
| gold402_verdictA | PAID ($0.001 USDC on Base) — the 24K Labs editorial verdict for one x402 resource, plus aggregated independent rater grades, as JSON. This is the human judgement layer: a maintainer looked at this service and put a name behind it. Distinct from gold402_check_endpoint, which is FREE and only reports whether the door answered. Call once with no payment_signature to receive the exact payment terms; call again with the signature to settle. This server never holds a wallet — you pay 24K Labs directly from yours. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct operation: browsing shelves, searching entries, fetching one entry, live-probing an endpoint, and retrieving a paid verdict. The free technical probe and paid editorial verdict are explicitly differentiated, so there is no realistic confusion.
Most tools follow a consistent gold402_verb_noun pattern (gold402_list_sections, gold402_get_entry, gold402_check_endpoint, gold402_search). The one exception is gold402_verdict, which uses a noun instead of a verb, creating a minor but noticeable deviation.
Five tools is exactly right for this directory-style MCP server. Each tool earns its place: browse, search, detail, live verification, and paid human judgment. The scope is tight and no tool feels redundant.
The server covers the full user workflow: discover categories, search entries, retrieve full records, independently probe any endpoint, and optionally purchase an editorial verdict. The paid verdict flow with signature-based settlement is included, so there are no dead ends.