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.

io.github.paladinfi/paladin-swap

REMOTE · SWAP.PALADINFI.COM · SCANNED AUG 23

Multi-aggregator swap router for AI agents on Base. 10 bps fee. MCP-native, non-custodial.

−77 this week 0 Trust /100

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 Security11
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 Safety

Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.

Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 4 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 io.github.paladinfi/paladin-swap MCP server?

io.github.paladinfi/paladin-swap is a hosted endpoint at https://swap.paladinfi.com/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 · swap.paladinfi.com

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

  • 23 Aug 26 −15

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

  • 22 Aug 26 −16

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

  • 21 Aug 26 −15

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

  • 20 Aug 26 −16

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

  • 19 Aug 26 −15

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

  • 17 Aug 26 0
    • Endpoint reachability: reachable → unreachable security
    • HSTS header: fail → unverified security
    • Authorization: partial → unverified security
    • Stability: 0.70 → unverified security
    • TLS certificate: pass → unverified security
    • Transport: pass → fail security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 16 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.

  • 14 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 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 23 Aug 2026 · Probed https://swap.paladinfi.com/mcp

TLS unreached
DNSSEC insecure

Validation of swap.paladinfi.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
paladinfi.com. absent 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://swap.paladinfi.com/mcp Unreachable
http (plaintext) http://swap.paladinfi.com/mcp HTTPS enforced
MCP tools · 3 exposed · ~905 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
swap_health ~26

Return the swap router's health + configuration (fee recipient, bps, supported chains).

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

swap_quote ~233

Get a competitive multi-aggregator swap quote with ready-to-execute calldata. PaladinFi does not represent any returned route as the best available across the broader DeFi market.

NameTypeReqDescription
buyTokenstringyesERC20 contract address to buy (e.g. WETH on Base = 0x4200000000000000000000000000000000000006)
chainIdintegerEVM chain ID (default 8453 = Base). Currently only Base is supported.
sellAmountstringyesAmount to sell in smallest unit (decimal string; e.g. "1000000000" = 1000 USDC)
sellTokenstringyesERC20 contract address to sell (e.g. USDC on Base = 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913)
slippageBpsOptional slippage tolerance in basis points (default from provider)
takerstringyesWallet address that will execute the swap (the agent's wallet)

Structured output declared, but exposes no named fields.

No examples provided.

trust_check_preview ~646

Get a SAMPLE-FIXTURE preview of the PaladinFi token-contract trust check. ⚠️ NOT a real evaluation. Returns fixed sample data with `_preview: true`, every factor marked `real: false`, and recommendation prefixed `sample-` (`sample-allow` / `sample-warn` / `sample-block`). Use this for shape-testing your integration; DO NOT use the verdict to gate real swaps, signing, or any production agent decision. **Programmatic safety check**: before consuming any field of this response, agents should test `resp.get("_real") is True` (top-level) — preview always returns `_real: false`. Substring-matching on `recommendation` (e.g. `"allow" in resp["trust"]["recommendation"]`) will INCORRECTLY match `sample-allow`; use exact-equality (`resp["trust"]["recommendation"] == "allow"`) or test the `_real` field instead. For REAL evaluations (3 paths, cheapest -> most-featured): - **Free wallet-OFAC screen (v0.11.77+)**: `POST https://swap.paladinfi.com/v1/trust-check/ofac` - anonymous, rate-limited (1 r/s + burst 3), runs only the OFAC SDN wallet-screen leg with real data (`_real: true`). Returns the same `recommendation: "allow" | "block"` shape as the full endpoint (no `warn` state — OFAC is binary). Useful for agents that just need sanctions screening without the full composition. Includes `_paid_endpoint_info` upgrade hint pointing at the paid endpoint. Wallet-OFAC scope — the Treasury SDN list carries wallet/EOA addresses, not token contracts. Use the paid endpoint for token-contract risk. - Install `@paladinfi/eliza-plugin-trust` (ElizaOS) or `@paladinfi/agentkit-actions` (Coinbase AgentKit). Both handle x402 payment ($0.001 USDC per call on Base) automatically and expose a `paladin_trust_check` action to your agent. - OR call `POST https://swap.paladinfi.com/v1/trust-check` via an x402-capable HTTP client. See https://paladinfi.com/trust-check/ for full integration docs. The paid endpoint composes live OFAC SDN screen…

NameTypeReqDescription
addressstringyesERC20 contract address to evaluate (Base 8453 only currently; must match `^0x[a-fA-F0-9]{40}$`)
chainIdintegerEVM chain ID (default 8453 = Base; only chain supported)

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the io.github.paladinfi/paladin-swap MCP server?

io.github.paladinfi/paladin-swap is an MCP server listed in the public MCP registry as io.github.paladinfi/paladin-swap. Multi-aggregator swap router for AI agents on Base. 10 bps fee. MCP-native, non-custodial. This page covers its hosted endpoint (https://swap.paladinfi.com/mcp).

Is the io.github.paladinfi/paladin-swap MCP server safe to use?

io.github.paladinfi/paladin-swap 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 io.github.paladinfi/paladin-swap MCP server expose?

io.github.paladinfi/paladin-swap exposes 3 tools: swap_quote, trust_check_preview, swap_health. Their descriptions and schemas cost roughly 905 tokens of context every time the server is loaded.

Does the io.github.paladinfi/paladin-swap MCP server require authentication?

Its publisher declares no required credentials for io.github.paladinfi/paladin-swap. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the io.github.paladinfi/paladin-swap MCP server still maintained?

io.github.paladinfi/paladin-swap 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 16 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.