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.

Tollbooth Swap API

REMOTE · API.TOLLBOOTHSWAP.XYZ · 2 COMPONENTS

Token swaps and honeypot/rug checks for AI agents on 8 chains, paid per-call in USDC via x402.

0 this week 23 Trust /100

Last scanned (14 hours ago)

Scores higher than 7% 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 Security57
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 (5)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (6)

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 yet verified: we couldn't confirm whether this endpoint requires 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.

  • 7 Nov 26 0
    • Endpoint reachability: unreachable → not serving MCP ▼ security
  • 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
  • 4 Nov 26 0
    • Endpoint reachability: not serving MCP → unreachable ▼ security
    • HSTS header: fail → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
  • 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
  • 4 Sept 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 3 Sept 26 0
    • Stability: 0.97 → pass security
  • 26 Aug 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 21 Nov 2026 · Probed https://api.tollboothswap.xyz/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.tollboothswap.xyz CN=YE1,O=Let's Encrypt,C=US 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA384 6aa5f68238f00f1b37beb65a28f18982c21
SANs: api.tollboothswap.xyz
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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.tollboothswap.xyz. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
xyz. DS published 3599, 18130 8, 8 Verified
tollboothswap.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
HTTP status 404

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.tollboothswap.xyz/mcp HTTP error 404
http (plaintext) http://api.tollboothswap.xyz/mcp HTTPS enforced 301 https://api.tollboothswap.xyz/mcp
MCP tools · 6 exposed · ~593 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
build_swap ~207

Build an unsigned swap transaction for the taker wallet to sign and submit. Costs an x402 toll in USDC (paid automatically when the x-tollbooth-payer-key header is set). Returns the transaction, quote, and a signed receipt.

NameTypeReqDescription
amountstringyesSell amount as an integer string in the input token's base units
chainstringyesChain to operate on
inputTokenstringyesToken being sold: mint address (solana) or ERC-20 address (EVM chains)
outputTokenstringyesToken being bought: mint address (solana) or ERC-20 address (EVM chains)
safeModeboolean–Screen both tokens first; refuses the build if either is critical-risk (honeypot etc.)
slippageBpsinteger–Max slippage in bps (default 100)
takerstringyesWallet address that will sign and send the swap
NameTypeReqDescription
acceptsarray–x402 payment options when unpaid
chainstring––
errorstring–Present when the request failed or payment is required
nextobject–Suggested follow-up calls
quoteobject–Quote the transaction was built from
receiptobject–Signed receipt for this build
safetyobject–Safety reports when safeMode was requested
transactionobject–Unsigned transaction for the taker to sign

No examples provided.

check_token ~96

Token safety screen before trading: honeypot, rug-pull, freeze/mint authority, transfer hooks, sell tax, blacklists. Returns verdict (ok/warn/critical/unknown), risk score, and findings. Costs an x402 toll.

NameTypeReqDescription
chainstringyesChain to operate on
tokenstringyesToken to screen: mint address (solana) or ERC-20 address (EVM chains)
NameTypeReqDescription
acceptsarray–x402 payment options when unpaid
chainstring––
errorstring–Present when the request failed or payment is required
findingsarray–Individual risk findings
nextobject–Suggested follow-up calls
riskScorenumber–0 (safe) to 100 (critical)
sourcestring–Data source used for the screen
tokenstring––
verdictstring–ok, warn, critical, or unknown

No examples provided.

get_quote ~139

Get a free indicative swap quote (output amount includes Tollbooth's fee). Use before build_swap to decide whether to trade.

NameTypeReqDescription
amountstringyesSell amount as an integer string in the input token's base units
chainstringyesChain to operate on
inputTokenstringyesToken being sold: mint address (solana) or ERC-20 address (EVM chains)
outputTokenstringyesToken being bought: mint address (solana) or ERC-20 address (EVM chains)
slippageBpsinteger–Max slippage in bps (default 100)
NameTypeReqDescription
chainstring––
feeBpsnumber–Tollbooth fee in basis points
inputAmountstring–Sell amount in base units
inputTokenstring––
nextobject–How to build the swap transaction
outputAmountstring–Estimated buy amount in base units, after fees
outputTokenstring––
slippageBpsnumber––

No examples provided.

get_receipt ~36

Fetch a signed Tollbooth receipt by id and verify its signature.

NameTypeReqDescription
idstringyesReceipt id returned by build_swap
NameTypeReqDescription
errorstring–Present when the receipt was not found
idstring–Receipt id
receiptobject–Receipt payload
signaturestring–Server signature over the receipt
validboolean–Whether the signature verified

No examples provided.

get_service_info ~27

Get Tollbooth service metadata: supported chains, swap fee, x402 toll pricing.

Input schema present but exposes no named parameters.

NameTypeReqDescription
descriptionstring–What the service does
endpointsobject–HTTP endpoints exposed by the service
namestring–Service name
paymentobject–x402 payment networks and pricing

No examples provided.

resolve_token ~88

Resolve a token ticker symbol (e.g. PEPE, WIF, USDC) to contract addresses on a chain, free. Curated majors return one verified match; others return live DEX matches ranked by liquidity.

NameTypeReqDescription
chainstringyesChain to operate on
symbolstringyesTicker symbol to resolve, e.g. USDC, PEPE, WIF
NameTypeReqDescription
chainstring–Chain searched
matchesarray–Matching tokens, best first
nextobject–Suggested follow-up calls
symbolstring–Symbol searched

No examples provided.

Install

How do I install the Tollbooth Swap API MCP server?

Tollbooth Swap API is a hosted endpoint at https://api.tollboothswap.xyz/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.tollboothswap.xyz

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

What is the Tollbooth Swap API MCP server?

Tollbooth Swap API is an MCP server listed in the public MCP registry as xyz.tollboothswap.api/tollbooth. Token swaps and honeypot/rug checks for AI agents on 8 chains, paid per-call in USDC via x402. This page covers its hosted endpoint (https://api.tollboothswap.xyz/mcp).

Is the Tollbooth Swap API MCP server safe to use?

Tollbooth Swap API scores 23 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 Tollbooth Swap API MCP server expose?

Tollbooth Swap API exposes 6 tools: get_service_info, resolve_token, get_quote, build_swap, check_token, get_receipt. Their descriptions and schemas cost roughly 593 tokens of context every time the server is loaded.

Does the Tollbooth Swap API MCP server require authentication?

Its publisher declares no required credentials for Tollbooth Swap API. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Tollbooth Swap API MCP server still maintained?

Tollbooth Swap API 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 Tollbooth Swap API MCP server?

VerifyMCP ran 5 checks on Tollbooth Swap API, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Tollbooth Swap API: Authorization, Schema quality, Stability, Tool coverage and 2 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.