Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MCPVOT — x402 Facilitator Machine

REMOTE · MCPVOT.XYZ

x402 paid APIs for AI agents on Base. Blockchain, wallet, DEX, crypto, web search.

Available components

−89 this week 0 Trust /100

Last scanned (1 day ago)

Scores higher than 0% of remote servers

Unreachable for 7 days in a row. Last reached 29 Oct 2026.

Category Crypto and Web3

Dead

Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.

Trust breakdown (7 categories)

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 Security0
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (3)

  • HTTPS
  • DNSSEC
  • Transport

Checks we could not complete (8)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 5 Nov 26 −18

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 4 Nov 26 −18

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 3 Nov 26 −17

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 2 Nov 26 −18

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 1 Nov 26 −18

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 30 Oct 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • HTTPS: pass → fail ▼ security
    • Transport: pass → fail ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 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
  • 25 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
Diagnostics

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 5 Nov 2026 · Probed https://mcpvot.xyz/api/mcp

TLS unreached
DNSSEC insecure

Validation of mcpvot.xyz. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
xyz. DS published 3599, 18130 8, 8 Verified
mcpvot.xyz. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcpvot.xyz/api/mcp Unreachable
http (plaintext) http://mcpvot.xyz/api/mcp Served over HTTP 200
MCP tools · 5 exposed · ~431 tokens

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 →

Tool Tokens
get_ecosystem_status ~37

Get mcpvot.xyz server health, available x402 services, and MCP endpoint info. FREE endpoint (no payment required).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_race_results ~96

Full iRacing race results including finish order (P1, P2, P3), laps completed, incidents, iRating changes, and weather/track info. Takes a subsession_id (from search_hosted_races). Requires active iRacing subscription. Costs $0.02 USDC per call.

NameTypeReqDescription
subsession_idintegeryesiRacing subsession ID (from search_hosted_races)

No output schema declared.

No examples provided.

lookup_driver ~78

Look up an iRacing driver profile by customer ID — iRating, license class, safety rating, career stats (starts, wins, top5s, avg finish, avg incidents). Requires active iRacing subscription. Costs $0.01 USDC per call.

NameTypeReqDescription
cust_idintegeryesiRacing customer ID (numeric)

No output schema declared.

No examples provided.

search_hosted_races ~148

Search iRacing hosted race results by date range, driver, or session name. Returns list of races with subsession IDs, track info, winner, driver count. Use subsession_id with get_race_results for full results. Requires active iRacing subscription. Costs $0.02 USDC per call.

NameTypeReqDescription
cust_idinteger–Filter by driver customer ID
session_namestring–Filter by session name (partial match)
start_range_beginstring–Start of date range (YYYY-MM-DD, default: 7 days ago)
start_range_endstring–End of date range (YYYY-MM-DD, default: today)

No output schema declared.

No examples provided.

search_web ~72

Search the web via SerpAPI (Google search). Returns organic results with rankings. Costs $0.01 USDC per call. Requires SERPAPI_KEY env var configured on backend.

NameTypeReqDescription
limitinteger–Max results (default 10, max 20)
qstringyesSearch query

No output schema declared.

No examples provided.

Install

How do I install the MCPVOT — x402 Facilitator Machine MCP server?

MCPVOT — x402 Facilitator Machine is a hosted endpoint at https://mcpvot.xyz/api/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 · mcpvot.xyz

# add to Claude Code
claude mcp add --transport http mcpvot-mcpvot 'https://mcpvot.xyz/api/mcp'
Common questions

What is the MCPVOT — x402 Facilitator Machine MCP server?

MCPVOT — x402 Facilitator Machine is an MCP server listed in the public MCP registry as io.github.MCPVOT/mcpvot. x402 paid APIs for AI agents on Base. Blockchain, wallet, DEX, crypto, web search. This page covers its hosted endpoint (https://mcpvot.xyz/api/mcp).

Is the MCPVOT — x402 Facilitator Machine MCP server safe to use?

MCPVOT — x402 Facilitator Machine scores 0 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 MCPVOT — x402 Facilitator Machine MCP server expose?

MCPVOT — x402 Facilitator Machine exposes 5 tools: search_web, get_race_results, lookup_driver, search_hosted_races, get_ecosystem_status. Their descriptions and schemas cost roughly 431 tokens of context every time the server is loaded.

Does the MCPVOT — x402 Facilitator Machine MCP server require authentication?

Its publisher declares no required credentials for MCPVOT — x402 Facilitator Machine. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the MCPVOT — x402 Facilitator Machine MCP server still maintained?

MCPVOT — x402 Facilitator Machine has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 29 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the MCPVOT — x402 Facilitator Machine MCP server?

VerifyMCP ran 3 checks on MCPVOT — x402 Facilitator Machine, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about MCPVOT — x402 Facilitator Machine: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.