Skip to content

ghost-x402-market-intel-vet-schema MCP server

dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market-intel-vet-schemaghost-identity.ghost-agent-os.workers.devstreamable-httpv1.1.0Scanned

Web search for agents, one x402 payment: real results, provider failover, signed receipt. $0.01.

5 tools: 3 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 3 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the ghost-x402-market-intel-vet-schema MCP server can do

The ghost-x402-market-intel-vet-schema MCP server is published by ghost-identity.ghost-agent-os.workers.dev, a domain the MCP Registry verified. It has 5 tools. It can create or change data (3 tools: ghost_schema_freshness, ghost_commerce_vet and ghost_pre_spend_gate), but cannot delete data. 2 tools only read.

1 tool brings in text other people can write (ghost_web_search); 1 tool can send data out of your system (ghost_schema_freshness).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 15, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 3Claude Code: ask
  • ghost_commerce_vetBefore paying an x402 seller you do not know: settlement history, payer structure, funding links, endpoint liveness, quote-vs-advertised price.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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. PROCEED means no blocker or concern was found in what Ghost checked. Payability, transfer history, independent demand, seller identity and delivery are reported separately under `evidence`, with anything unresolved listed under `unresolved`; Ghost does not verify who the seller is or that it delivers. Paid per call via x402. Payment: $0.01 USDC on Base per call over x402, settled before the tool runs. An x402 MCP client such as x402-proxy pays it automatically; if you use x402-proxy, set its spend limits first (spendLimitPerTx 0.01, spendLimitDaily 0.10; see /llms.txt). A funded payment and delivery through x402-proxy has not been verified yet.
  • ghost_pre_spend_gateTHE PRE-SPEND GATE.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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 an INSUFFICIENT_EVIDENCE question is refused before any terms are quoted, so nothing settles for it; any other decision is paid upfront. Payment: $0.01 USDC on Base per call over x402, settled before the tool runs. An x402 MCP client such as x402-proxy pays it automatically; if you use x402-proxy, set its spend limits first (spendLimitPerTx 0.01, spendLimitDaily 0.10; see /llms.txt). A funded payment and delivery through x402-proxy has not been verified yet.
  • ghost_schema_freshnessHas this published JSON Schema or OpenAPI document changed since a fingerprint you hold?Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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. Payment: $0.01 USDC on Base per call over x402, settled before the tool runs. An x402 MCP client such as x402-proxy pays it automatically; if you use x402-proxy, set its spend limits first (spendLimitPerTx 0.01, spendLimitDaily 0.10; see /llms.txt). A funded payment and delivery through x402-proxy has not been verified yet.
Only reads 2Show 2 read-only tools

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:53 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://ghost-identity.ghost-agent-os.workers.dev/mcp: tools/list returned 5 tools to an anonymous client, including ghost_schema_freshness (write), ghost_commerce_vet (write), ghost_pre_spend_gate (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools5 changed.~5 changedView diff

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http ghost-x402-market-intel-vet-schema https://ghost-identity.ghost-agent-os.workers.dev/mcp
claude mcp add --transport http ghost-x402-market-intel-vet-schema https://ghost-identity.ghost-agent-os.workers.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__ghost-x402-market-intel-vet-schema__ghost_web_search",
      "mcp__ghost-x402-market-intel-vet-schema__ghost_commerce_search"
    ],
    "ask": [
      "mcp__ghost-x402-market-intel-vet-schema__ghost_schema_freshness",
      "mcp__ghost-x402-market-intel-vet-schema__ghost_commerce_vet",
      "mcp__ghost-x402-market-intel-vet-schema__ghost_pre_spend_gate"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ghost-x402-market-intel-vet-schema. Review it before you use it.

Capability tags behind 2 rules
  • mcp__ghost-x402-market-intel-vet-schema__ghost_web_search untrusted-input
  • mcp__ghost-x402-market-intel-vet-schema__ghost_schema_freshness outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market-intel-vet-schema/verify?hash=573aa6dd6c9318a017b2eae66642376127098fd0b4eb607c3e196ab5910b6554" | jq -e '.changed == false'

Pinned hash 573aa6dd6c93, from Nov 15, 2026, 04:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market-intel-vet-schema/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market-intel-vet-schema
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market-intel-vet-schema.svg)](https://radar.anlyon.com/servers/dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market-intel-vet-schema)

Source: MCP Registry. Synced Oct 21, 2026, 18:12 UTC.

ghost-x402-market-intel-vet-schema MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the ghost-x402-market-intel-vet-schema MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the ghost-x402-market-intel-vet-schema MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the ghost-x402-market-intel-vet-schema MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the ghost-x402-market-intel-vet-schema MCP server have?

5 tools: 3 write, 2 read. ghost_schema_freshness, ghost_commerce_vet, ghost_pre_spend_gate, ghost_web_search and ghost_commerce_search.

Does the ghost-x402-market-intel-vet-schema MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the ghost-x402-market-intel-vet-schema MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): ghost_schema_freshness.

Has the ghost-x402-market-intel-vet-schema MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 2, 2026. Every change is on this page and in its Atom feed.