Server data from the Official MCP Registry
MCP server exposing 8004Swap (no-KYC agent-to-agent RFQ swap) as tools any MCP agent can call.
About
MCP server exposing 8004Swap (no-KYC agent-to-agent RFQ swap) as tools any MCP agent can call.
Security Report
The MCP server is well-architected for its purpose as an autonomous agent trading interface, with appropriate authentication and reasonable permission scoping. However, several security concerns exist: the MCP server requires an agent private key stored in environment variables without explicit warnings about key management, the x402 payment handler accepts arbitrary HTTP resources without URL validation, and there are missing input validations on quote amounts. These are moderate-severity issues that users should be aware of before deploying this server with real credentials or funds. Supply chain analysis found 5 known vulnerabilities in dependencies (0 critical, 4 high severity). Package verification found 1 issue.
8 files analyzed · 13 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
What You'll Need
Set these up before or after installing:
Environment variable: AGENT_PRIVATE_KEY
Environment variable: RELAY_URL
Environment variable: RPC_URL
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-stakemate369-8004swap-mcp": {
"env": {
"RPC_URL": "your-rpc-url-here",
"RELAY_URL": "your-relay-url-here",
"AGENT_PRIVATE_KEY": "your-agent-private-key-here"
},
"args": [
"-y",
"@stakemate/8004swap-mcp-server"
],
"command": "npx"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
8004Swap
Non-custodial RFQ exchange built only for autonomous agents (not humans). Every trade is a direct match between two agents (maker/taker), settled atomically on-chain — no pre-funded liquidity pool, following the 0x Protocol / CoW Swap pattern.
Differentiator: no-KYC access + on-chain reputation via ERC-8004, not just another exchange with a bot layer bolted onto infra that still requires human KYC.
Status: testnet (Base Sepolia). No real funds at risk. No formal audit yet.
Architecture
Maker agent ──┐ ┌── Taker agent
│ WebSocket (RFQ, off-chain │
▼ EIP-712 signature, gasless) ▼
┌─────────────────────────────────────────────┐
│ Relay (relay/) │
│ RFQ matching, best-price ranking │
└─────────────────────┬─────────────────────────┘
│ signed quote
▼
┌───────────────────────────┐
│ Settlement.sol │ ← atomic settlement,
│ (contracts/Settlement.sol)│ Chainlink oracle,
└─────────────┬───────────────┘ risk caps
│ isActive() / recordFill()
▼
┌───────────────────────────┐
│ Registry.sol │ ← who's allowed to trade
│ (contracts/Registry.sol) │
└───────────────────────────┘
- Registry.sol — registry of authorized agents (self-registration,
msg.senderproves key control). Owner can pause globally. - Settlement.sol — settles an EIP-712-signed
Quote. Requires a Chainlink oracle registered per pair (deny-by-default), checks staleness, applies risk caps (maxTradeAmount,maxVolumePerWindow) and an optional anti-sybil fee (feeBps). - relay/ — WebSocket server that authenticates agents (login signature), matches
RFQs by token pair, and returns the best signed quote to the taker, who settles
on-chain by calling
fillQuotedirectly. - sdk/ (
@stakemate/8004swap-agent-sdk) — TypeScript client that wraps the WS handshake, EIP-712 signing and on-chain settlement, for anyone integrating an agent without reimplementing the protocol from scratch. Seesdk/README.md. - sdk-python/ (
8004swap-agent-sdk) — same thing, in Python (eth_account+websockets+web3.py). Seesdk-python/README.md. - mcp-server/ (
@stakemate/8004swap-mcp-server) — exposes the protocol as MCP tools (request_quote,fill_quote,check_agent_status,register_agent), so any MCP-capable agent can trade directly without a human in the loop. Seemcp-server/README.md.
See PROTOCOL.md for the exact Relay message format.
Running locally
Contracts (Foundry)
forge build
forge test
Relay
cd relay
npm install
cp .env.example .env # fill in BASE_RPC_URL, REGISTRY_ADDRESS
npm run dev
Agent examples (maker/taker) live in relay/examples/ — they run against the local
or hosted Relay. To integrate a new agent, prefer sdk/ (@stakemate/8004swap-agent-sdk), which
wraps the same flow as those examples as a library.
Contract deployment
forge script script/DeploySepolia.s.sol --rpc-url <sepolia_rpc> --private-key <key> --broadcast
script/Deploy.s.sol is the mainnet version (4 pairs against USDC) — do not run
without an explicit decision, contracts have not gone through a formal audit yet.
Current network (Base Sepolia)
- Registry:
0x7Bb793b6Ada038cf9c26c6BB54cA15Db6BD35ed1 - Settlement:
0x5Cc2558dF13739c05cb57Caf0E9cfe1629a6a945 - Active pair: WETH/test-USDC
Contributing
Open to external contributors — contracts, relay, SDKs in other languages, support
for new chains. See CONTRIBUTING.md.
License
MIT
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Fetch
Freeby Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
mcp-creator-python
Freeby mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
MarkItDown
Freeby Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption