Pairity runs an MCP server (Model Context Protocol), so AI assistants like Claude or Cursor can look up coins, quote trades, build unsigned trades and prepare launches by themselves. It uses the same operations, rules and rate limits as the Agent API.
Note
Connection details#
| Endpoint | https://pairity.wtf/api/mcp |
| Transport | Streamable HTTP, JSON responses only (no SSE stream). POST one JSON-RPC 2.0 message or a batch of up to 20. |
| Auth | None. No key or account. |
| Sessions | Stateless. Nothing is stored between requests. |
| Protocol versions | 2025-06-18 (default), 2025-03-26, 2024-11-05 |
| Methods | initialize, ping, tools/list, tools/call |
| Rate limit | 60 HTTP requests per minute per IP, and each tool call also counts in its Agent API bucket |
Add it to your AI client#
Claude Code
claude mcp add --transport http pairity https://pairity.wtf/api/mcpProject config (.mcp.json)
{
"mcpServers": {
"pairity": {
"type": "http",
"url": "https://pairity.wtf/api/mcp"
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"pairity": {
"url": "https://pairity.wtf/api/mcp"
}
}
}Claude (web and desktop)
Add a custom connector in Claude's connector settings and paste the endpoint URL above.
Any other MCP client that supports remote HTTP servers works the same way: give it the endpoint URL.
Tools#
| Tool | Read-only | What it does |
|---|---|---|
list_tokens | yes | List or search coins. sort: new | trending | graduating; q, limit (1–50), offset. |
get_token | yes | One coin: price, market cap, curve progress, on-chain fee split, traders, holders, links. |
get_trades | yes | Recent trades of a coin, newest first (limit 1–100). |
quote_trade | yes | Quote a buy or sell in base units, with site fees and the minimum output after slippage. |
build_trade_tx | no | An UNSIGNED base64 v0 transaction for user (fee payer and only signer). |
get_tx_status | yes | confirmed | failed | expired | pending. Pass lastValidBlockHeight to detect expiry. |
list_skills | yes | The AI skills catalog (content only; skills never move funds). |
get_launch_config | yes | Fee split rules, AI coin split, pair types, field limits and the launch flow. |
prepare_launch | no | Unsigned launch transactions and a sealedToken, exactly like the website. |
Each tool's input schema comes from the same validation as the REST API, so the parameters match the Agent API one to one. Note one difference: get_tx_status takes signature and lastValidBlockHeight, while the REST route uses the query name lvbh.
How a trade works through MCP#
- The assistant calls
quote_trade, thenbuild_trade_txwith your wallet address asuser. - You (or your wallet software) sign the transaction. Then it is sent with
POST /api/sendon this site. - The assistant polls
get_tx_statusuntil it is no longer pending.
Amounts are base units: lamports for SOL (1 SOL = 1000000000), and 6 decimals for coins.
Raw JSON-RPC#
curl -s https://pairity.wtf/api/mcp \
-H 'content-type: application/json' \
-H 'accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_tokens","arguments":{"sort":"trending","limit":5}}}'{
"jsonrpc": "2.0",
"id": 1,
"result": {
"content": [{ "type": "text", "text": "{\"sort\":\"trending\",\"count\":5,…}" }],
"structuredContent": { "sort": "trending", "count": 5, "offset": 0, "tokens": [] }
}
}- Every result has the data twice: as JSON text in
contentand as an object instructuredContent. - Bad arguments return a JSON-RPC error (code -32602). Errors while running a tool, such as a rate limit or an unknown coin, come back as a result with
isError: trueso the assistant can read and react. - Notifications get HTTP 202 with no body. GET and DELETE on the endpoint return 405.
Important