dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market-intel-vet-schema
dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market-intel-vet-schema · 1.1.0
Web search for agents, one x402 payment: real results, provider failover, signed receipt. $0.01.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 35 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://ghost-identity.ghost-agent-os.workers.dev/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 5 tools.
- Protocol
- 2025-06-18
- Calls itself
- ghost 1.0.0
- Handshake time
- 478 ms
- HTTP status
- 200
The tools it lists (5, as of 2 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
ghost_web_searchSearch the web and get the results, in ONE payment. Ghost runs the search on its own provider account and returns the actual results — organic hits with title, url and snippet, plus answer box, knowledge panel, related questions — normalised into one shape. Three things most paid search tools do not do: it runs on more than one search provider and fails over between them, so a dead upstream costs you a retry rather than an answer; it never charges you for a search that did not come back, returning the fee as credit instead; and every answer carries a DSSE-signed receipt naming the provider tha
ghost_schema_freshnessHas this published JSON Schema or OpenAPI document changed since a fingerprint you hold? The schema-drift recheck of the pre-spend policy: run it when a provider's published contract may have moved before you pay it again. Paid per call via x402; DSSE-signed receipt.
ghost_commerce_vetBefore paying an x402 seller you do not know: settlement history, payer structure, funding links, endpoint liveness, quote-vs-advertised price. Use when one named provider or payment address is already in hand and you need a verdict before you pay it. PROCEED/CAUTION/REJECT/INSUFFICIENT_EVIDENCE with a signed receipt. Paid per call via x402.
ghost_commerce_searchDecide which x402 provider to pay, before paying it. Consult when the provider is unknown, when a decision you hold has passed its valid_until, or when the price, health, verdict or funding of one materially changed. Finds providers by need and ranks them by real economic evidence: independent payers, calls-per-payer (the repeat signature), last settlement, on-chain trust verdicts and change history. Returns USE/WATCH/AVOID with the exact call, a fallback, valid_until and recheck_when — reuse a held decision until it expires or a trigger fires, rather than asking again. Paid per call via x402;
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market-intel-vet-schema, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 32 days ago. The registry entry