dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market-intel-vet-schema
REMOTE · GHOST-IDENTITY.GHOST-AGENT-OS.WORKERS.DEV
Web search for agents, one x402 payment: real results, provider failover, signed receipt. $0.01.
Available components
Last scanned (9 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1831 tokens (~366/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 70% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “ghost_pre_spend_gate” rewrote its description, which is the text the model reads security
- Tool “ghost_web_search” rewrote its description, which is the text the model reads security
- 10 Oct 26 +50
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 6 Oct 26 −50
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 30 Sept 26 0
- Stability: 0.97 → pass security
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://ghost-identity.ghost-agent-os.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ghost-agent-os.workers.dev | CN=WE1,O=Google Trust Services,C=US | 30 Aug 2026 | 28 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | f47595e8e8701762131c2645dbbfd527 |
| SANs: ghost-agent-os.workers.dev, *.ghost-agent-os.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ghost-identity.ghost-agent-os.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ghost-identity.ghost-agent-os.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://ghost-identity.ghost-agent-os.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ghost_commerce_search ~294
Decide 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; free preflight at /v1/commerce/search/preflight (3/day).
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | – | Capability keyword(s), e.g. 'search' |
| limit | integer | – | – |
| max_price_usd | number | – | 0 means no price ceiling |
| min_payers | integer | – | Only providers with at least this many independent payers in 30d |
| network | string | – | CAIP-2 filter, e.g. eip155:8453 |
| payment_signature | string | – | x402 PAYMENT-SIGNATURE header value. Omit it to receive the payment terms; call again with it to run the tool. |
| query | string | – | Free-text need, e.g. 'solana market data with recent buyers' |
No output schema declared.
No examples provided.
ghost_commerce_vet ~206
Before 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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | The seller's payment address (payTo). Optional if endpoint_url is given — the 402 names its own address. |
| advertised_amount | – | – | The price a listing advertised, in minor units, to compare against the live quote. |
| endpoint_url | string | – | The seller's paid endpoint, probed with one unpaid request to read its x402 terms. |
| payment_signature | string | – | x402 PAYMENT-SIGNATURE header value. Omit it to receive the payment terms; call again with it to run the tool. |
No output schema declared.
No examples provided.
ghost_pre_spend_gate ~640
THE PRE-SPEND GATE. Call this immediately before your agent pays an x402/API provider, with the task's own economics. Returns ALLOW / FALLBACK / DECLINE / INSUFFICIENT_EVIDENCE — not advice: a decision your payment path should enforce. It joins the provider's measured record (independent payers, concentration, price drift, reachability, funding links, on-chain verdict) to YOUR numbers (customer_revenue, value_of_success, max_budget, required_margin, failure_cost, switching_cost) and answers the question ranking cannot: is paying for THIS task profitable, and at which provider. Where the task's value is known it maximises expected net value; where it is not, it minimises cost per verified success — which is why it will refuse the cheapest call when a cheaper provider succeeds less often. Unknown economics stay UNKNOWN and are never invented. Report the result afterwards to /v1/gate/outcome (free) — that is the only source of the success rates it uses. Paid per decision via x402, or drawn from prepaid credit. On prepaid credit a cached decision inside valid_until and an INSUFFICIENT_EVIDENCE answer draw nothing; on the per-decision x402 rail the fee settles before the decision runs, whatever it says.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | – |
| customer_revenue | – | – | – |
| failure_cost | – | – | – |
| fallback_authorized | boolean | – | May Ghost route to a different candidate than the first? Off by default: an unrequested reroute is a payment the operator did not choose. |
| max_budget | – | – | – |
| payment_signature | string | – | x402 PAYMENT-SIGNATURE header value. Omit it to receive the payment terms; call again with it to run the tool. |
| provider_candidates | array | yes | – |
| required_margin | – | – | – |
| revenue_models | array | – | Optional. Say what the task is worth in the terms you actually measure, and Ghost derives value_of_success / customer_revenue / max_budget from it — never overriding a value you stated yourself. Each… |
| success_definition | string | yes | What counts as success, written down BEFORE paying. verified_success is later judged against this. |
| switching_cost | – | – | – |
| task_id | string | yes | – |
| task_type | string | yes | What kind of job this is. Success history is pooled under it, so it must be stable. |
| value_of_success | – | – | – |
No output schema declared.
No examples provided.
ghost_schema_freshness ~141
Has 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.
| Name | Type | Req | Description |
|---|---|---|---|
| known_fingerprint | string | – | The fingerprint from a previous check. Empty means first observation. |
| payment_signature | string | – | x402 PAYMENT-SIGNATURE header value. Omit it to receive the payment terms; call again with it to run the tool. |
| url | string | yes | Public URL of a JSON Schema or OpenAPI document |
No output schema declared.
No examples provided.
ghost_web_search ~275
Search 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. It fails over from Serping to Serper, so one dead upstream costs a retry. Payment settles before the search runs; if no upstream delivers, the fee becomes Ghost service credit, not an on-chain refund. The DSSE receipt is Ghost's signature over your query, the returned URLs and the provider that served them. It proves what Ghost returned and from which upstream; it does not verify that the results are accurate, complete or current. Search only: Ghost does not fetch the pages. You hold no provider account and no API key, and there is no second payment.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Country code for localisation, e.g. 'us', 'de'. |
| language | string | – | Interface language, e.g. 'en', 'es'. |
| payment_signature | string | – | x402 PAYMENT-SIGNATURE header value. Omit it to receive the payment terms; call again with it to run the tool. |
| query | string | yes | What to search the web for. |
| results | integer | – | How many organic results to return. |
No output schema declared.
No examples provided.
How do I install the dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market… MCP server?
dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market… is a hosted endpoint at https://ghost-identity.ghost-agent-os.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ghost-identity.ghost-agent-os.workers.dev
claude mcp add --transport http dev-workers-ghost-agent-os-ghost-identity-ghost- 'https://ghost-identity.ghost-agent-os.workers.dev/mcp'
What is the dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market… MCP server?
dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market… is an MCP server listed in the public MCP registry as dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market…. Web search for agents, one x402 payment: real results, provider failover, signed receipt. $0.01. This page covers its hosted endpoint (https://ghost-identity.ghost-agent-os.workers.dev/mcp).
Is the dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market… MCP server safe to use?
dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market… scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market… MCP server expose?
dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market… exposes 5 tools: ghost_web_search, ghost_schema_freshness, ghost_commerce_vet, ghost_commerce_search, ghost_pre_spend_gate. Their descriptions and schemas cost roughly 1,556 tokens of context every time the server is loaded.
Does the dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market… MCP server require authentication?
No. We connected to dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market… MCP server still maintained?
dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market… is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.