Skip to main content
Glama

autonomousintelligence-mcp

MCP server for Autonomous Intelligence — the non-custodial, rug-gated crypto action layer for AI agents. Give any MCP client (Claude, Cursor, ChatGPT, …) the power to discover, safety-check, quote and execute multi-chain token swaps.

  • Non-custodial: build_swap returns an unsigned transaction; your agent signs it locally with the user's own wallet; submit_swap only ever receives an already-signed tx. Keys never leave your environment.

  • Rug-gated: check_token_safety flags honeypots, mint/freeze authority, liquidity locks, holder concentration.

  • Keyless discovery: quotes, safety, gems, token info, tradeable list — no key. A self-serve key is only needed for execution.

Install

claude mcp add autonomous-intelligence -e AI_AGENT_KEY=YOUR_KEY -- npx -y autonomousintelligence-mcp

Or in ~/.cursor/mcp.json (Cursor / VS Code / Windsurf):

{ "mcpServers": { "autonomous-intelligence": {
  "command": "npx", "args": ["-y", "autonomousintelligence-mcp"],
  "env": { "AI_AGENT_KEY": "YOUR_KEY" } } } }

Hosted, no install: https://autonomousintelligence.io/mcp

Related MCP server: near-intent-swaps

Tools

get_quote · check_token_safety · find_gems · get_token_info · list_tradeable_tokens · build_swap* · submit_swap* (* need a key)

Get a key (self-serve)

curl -s -X POST https://autonomousintelligence.io/v1/agent/register \
  -H 'content-type: application/json' -d '{"agent_name":"my-agent"}'
# -> { "ok": true, "key": "ai_live_..." }

AI_AGENT_KEY is only used for build_swap / submit_swap. A 2% platform fee is included in every built swap.

Non-custodial swap flow

get_quote  ->  build_swap (unsigned tx + build_id)  ->  [sign locally with the user's wallet]  ->  submit_swap

Docs: https://autonomousintelligence.io/docs#agents · Drop-in SDKs (JS/Python) + framework adapters: https://autonomousintelligence.io/sdk/

MIT © Autonomous Intelligence

Available Tools

7 tools
build_swapA

Build an UNSIGNED swap transaction (2% fee baked in) + a build_id. Requires an API key. Sign it locally with your own wallet, then call submit_swap with the same build_id. Your key never leaves your environment.

Inputs: args.

check_token_safetyC

Rug-gate a token: honeypot, mint/freeze authority, liquidity lock, holder concentration.

Inputs: args.

find_gemsC

Rug-gated new/trending tokens. tab: new | trending | graduated.

Inputs: args.

get_quoteA

Get a swap quote (route, expected out, 2% fee disclosed) for inputMint→outputMint of amount in base units.

Inputs: args.

get_token_infoB

Live price, liquidity and market cap for a mint.

Inputs: args.

list_tradeable_tokensD

Every token swappable on the DEX.

Inputs: args.

submit_swapA

Broadcast an already-signed swap transaction with its build_id. Requires an API key. Returns the signature and confirmation status.

Inputs: args.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct concern: quoting, safety checks, discovery, token info, listings, and two-step swap transaction handling. Even the overlapping price-related tools (get_quote vs get_token_info) are clearly differentiated by their context: swap quotes versus general token metrics.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with lowercase and underscores: get_quote, check_token_safety, find_gems, get_token_info, list_tradeable_tokens, build_swap, submit_swap. There are no mixed conventions or irregular verbs, making the API easy to predict.

    Tool Count5/5

    With seven tools, the server is well-scoped for a DEX integration. Each tool serves a clear purpose in the workflow—from discovery and safety to quote and transaction execution—without unnecessary bloat or redundancy.

    Completeness5/5

    The tool surface covers the core lifecycle for token swapping: discovering tokens, checking safety, fetching token data, quoting, building, and submitting swaps. No major operation is missing; the two-step build/submit flow is logically complete for a secure MCP library.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers