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.

x402card: Virtual Cards + Freeland eSIM

REMOTE · API.X402CARD.ORG

Issue and top up x402 virtual cards or buy Freeland travel eSIMs with Base USDC.

Available components

0 this week 76 Trust /100

Last scanned (20 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

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 Security63
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 425 tokens (~35/item across 12 items; 12 tools + 0 resources), lean.Pass
  • 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 Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

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.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 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
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
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 21 Nov 2026 · Probed https://api.x402card.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.x402card.org CN=YE2,O=Let's Encrypt,C=US 5 Nov 2026 3 Feb 2027 ECDSA 256 ECDSA-SHA384 61c69536f630f06cd5005ab8957fca40eec
SANs: api.x402card.org
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.x402card.org. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
org. DS published 725 8 Verified
x402card.org. No DS 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy no-referrer

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.x402card.org/mcp Verified 200
http (plaintext) http://api.x402card.org/mcp HTTPS enforced 301 https://api.x402card.org/mcp
MCP tools · 12 exposed · ~388 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
x402card.get_agent_contract ~25

Return the complete machine-readable x402card API/agent contract.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

x402card.get_card_contract ~34

Return the virtual-card direct x402 purchase, payer-ownership, issuance, economics, and credential-security contract.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

x402card.get_card_topup_contract ~39

Return the separate direct x402 card top-up, active-card ownership, amount, fee, replay, and asynchronous funding contract.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

x402card.get_config ~33

Return public runtime config: network, USDC asset, receive address, fees, limits, and treasury mode.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

x402card.get_esim_contract ~36

Return the Freeland eSIM catalog, direct x402 purchase, payer-ownership, fulfillment, and privacy contract.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

x402card.get_esim_readiness ~27

Return eSIM-only readiness without unrelated card-provider or treasury gates.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

x402card.get_install_command ~22

Return the shell install command and CLI discovery commands.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

x402card.get_openapi ~27

Return the OpenAPI 3.1 document for direct HTTP API usage.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

x402card.get_payable_url ~34

Build the public payable x402 URL for an existing order id.

NameTypeReqDescription
orderIdstringyes–

No output schema declared.

No examples provided.

x402card.get_readiness ~35

Return sanitized public readiness. Deep provider balances and BIN internals are admin-only.

NameTypeReqDescription
deepboolean––

No output schema declared.

No examples provided.

x402card.get_wallet_requirements ~31

Return signer-agnostic owner authentication, x402 payer, credential, and adapter requirements.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

x402card.list_esim_plans ~45

List live Freeland prepaid travel eSIM plans and current Base USDC prices.

NameTypeReqDescription
countryCodestring––
typestring––

No output schema declared.

No examples provided.

Install

How do I install the x402card: Virtual Cards + Freeland eSIM MCP server?

x402card: Virtual Cards + Freeland eSIM is a hosted endpoint at https://api.x402card.org/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 · api.x402card.org

# add to Claude Code
claude mcp add --transport http org-x402card-freeland-esim 'https://api.x402card.org/mcp'
Common questions

What is the x402card: Virtual Cards + Freeland eSIM MCP server?

x402card: Virtual Cards + Freeland eSIM is an MCP server listed in the public MCP registry as org.x402card/freeland-esim. Issue and top up x402 virtual cards or buy Freeland travel eSIMs with Base USDC. This page covers its hosted endpoint (https://api.x402card.org/mcp).

Is the x402card: Virtual Cards + Freeland eSIM MCP server safe to use?

x402card: Virtual Cards + Freeland eSIM scores 76 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 x402card: Virtual Cards + Freeland eSIM MCP server expose?

x402card: Virtual Cards + Freeland eSIM exposes 12 tools: x402card.get_agent_contract, x402card.get_wallet_requirements, x402card.get_config, x402card.get_esim_contract, x402card.get_card_contract, and 7 more. Their descriptions and schemas cost roughly 388 tokens of context every time the server is loaded.

Does the x402card: Virtual Cards + Freeland eSIM MCP server require authentication?

No. We connected to x402card: Virtual Cards + Freeland eSIM without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the x402card: Virtual Cards + Freeland eSIM MCP server still maintained?

x402card: Virtual Cards + Freeland eSIM is still listed as active in the MCP registry. We last reached this channel on 21 November 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 x402card: Virtual Cards + Freeland eSIM MCP server?

VerifyMCP ran 12 checks on x402card: Virtual Cards + Freeland eSIM, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about x402card: Virtual Cards + Freeland eSIM: Authorization. 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.