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 · SCANNED SEP 22

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
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.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.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools.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.

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'
// .cursor/mcp.json
{
  "mcpServers": {
    "xyz-tollboothswap-api-tollbooth": {
      "url": "https://api.tollboothswap.xyz/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "xyz-tollboothswap-api-tollbooth": {
      "type": "http",
      "url": "https://api.tollboothswap.xyz/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.xyz-tollboothswap-api-tollbooth]
url = "https://api.tollboothswap.xyz/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-tollboothswap-api-tollbooth": {
      "type": "remote",
      "url": "https://api.tollboothswap.xyz/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add xyz-tollboothswap-api-tollbooth --url 'https://api.tollboothswap.xyz/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  xyz-tollboothswap-api-tollbooth:
    url: "https://api.tollboothswap.xyz/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "xyz-tollboothswap-api-tollbooth": {
      "Transport": "http",
      "Url": "https://api.tollboothswap.xyz/mcp"
    }
  }
}
# add to Vellum
assistant mcp add xyz-tollboothswap-api-tollbooth -t streamable-http -u 'https://api.tollboothswap.xyz/mcp'
// mcp.json
{
  "mcpServers": {
    "xyz-tollboothswap-api-tollbooth": {
      "type": "http",
      "url": "https://api.tollboothswap.xyz/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 4 Sept 26 −55
    • Endpoint reachability: reachable → not serving MCP security
    • Tool safety: pass → unverified security
    • Stability: pass → unverified security
    • Transport: pass → fail security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 3 Sept 26 0
    • Stability: 0.97 → pass security
  • 1 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Aug 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
  • 25 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

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 Sept 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 4 Aug 2026 2 Nov 2026 ECDSA 256 ECDSA-SHA384 6f0df45d130e98d67bab9669bdea4f3f610
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. present 3599, 18130 8, 8 Verified
tollboothswap.xyz. 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 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)
safeModebooleanScreen both tokens first; refuses the build if either is critical-risk (honeypot etc.)
slippageBpsintegerMax slippage in bps (default 100)
takerstringyesWallet address that will sign and send the swap
NameTypeReqDescription
acceptsarrayx402 payment options when unpaid
chainstring
errorstringPresent when the request failed or payment is required
nextobjectSuggested follow-up calls
quoteobjectQuote the transaction was built from
receiptobjectSigned receipt for this build
safetyobjectSafety reports when safeMode was requested
transactionobjectUnsigned 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
acceptsarrayx402 payment options when unpaid
chainstring
errorstringPresent when the request failed or payment is required
findingsarrayIndividual risk findings
nextobjectSuggested follow-up calls
riskScorenumber0 (safe) to 100 (critical)
sourcestringData source used for the screen
tokenstring
verdictstringok, 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)
slippageBpsintegerMax slippage in bps (default 100)
NameTypeReqDescription
chainstring
feeBpsnumberTollbooth fee in basis points
inputAmountstringSell amount in base units
inputTokenstring
nextobjectHow to build the swap transaction
outputAmountstringEstimated 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
errorstringPresent when the receipt was not found
idstringReceipt id
receiptobjectReceipt payload
signaturestringServer signature over the receipt
validbooleanWhether 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
descriptionstringWhat the service does
endpointsobjectHTTP endpoints exposed by the service
namestringService name
paymentobjectx402 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
chainstringChain searched
matchesarrayMatching tokens, best first
nextobjectSuggested follow-up calls
symbolstringSymbol searched

No examples provided.

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?

No. We connected to Tollbooth Swap API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.