Overview
The ACN MCP Server is a remote Model Context Protocol server hosted at mcp.acn.exchange. It exposes ACN’s capabilities as tools that any MCP-compatible agent can call natively.
Instead of writing HTTP client code, your agent sees ACN services as tools it can invoke directly.
Authentication is optional. Any agent can discover, execute, and pay for capabilities without signing up. Payment is the authentication — the on-chain transaction proves intent and identity.
Configuration
Zero-friction (no auth)
Connect with no credentials — your agent can immediately discover and use capabilities:
{
"mcpServers": {
"acn": {
"type": "url",
"url": "https://mcp.acn.exchange/mcp"
}
}
}
Wallet-identified (recommended)
Provide your wallet address for better rate limits and reputation tracking:
{
"mcpServers": {
"acn": {
"type": "url",
"url": "https://mcp.acn.exchange/mcp",
"headers": {
"x-acn-wallet": "0xYourWalletAddress"
}
}
}
}
Fully authenticated
For full features (balance checks, call history, spend limits):
{
"mcpServers": {
"acn": {
"type": "url",
"url": "https://mcp.acn.exchange/mcp",
"headers": {
"x-acn-api-key": "acn_sk_your_api_key"
}
}
}
}
Identity Tiers
| Tier | How | Rate Limit | Features |
|---|
| Anonymous | No headers | 20 req/min (by IP) | Discover, execute, pay |
| Wallet-Identified | X-Acn-Wallet header | Trust-tier based (30–500/min) | Above + reputation accrual |
| Authenticated | API key or wallet signature | Entity-based (100–500/min) | All above + balance, history, spend limits |
acn_discover
Search the ACN marketplace for capabilities.
| Parameter | Type | Required | Description |
|---|
query | string | No | Natural language search query |
domain | string | No | Filter by domain (data, communication, utility, etc.) |
category | string | No | Filter by category within domain |
max_price | string | No | Maximum price in USDC per call |
limit | number | No | Max results (default: 10, max: 20) |
acn_execute
Execute a capability on the ACN network. Works without authentication.
| Parameter | Type | Required | Description |
|---|
capability | string | Yes | Capability identifier (e.g., data.crypto.price) |
params | object | No | Input parameters matching the capability schema |
optimize_for | string | No | Routing preference: price, latency, reliability, or balanced |
acn_submit_payment
Submit payment to complete a capability execution.
| Parameter | Type | Required | Description |
|---|
call_id | string | Yes | The call ID from the payment challenge |
tx_hash | string | No | Already-broadcast transaction hash |
signed_tx | string | No | Raw signed transaction hex (server broadcasts) |
tx_hash or signed_tx is required.
acn_auth_status
Check your current identity tier and rate limits. Works without authentication.
Returns your current tier (anonymous, wallet-identified, or authenticated), trust tier, rate limits, and available auth upgrades.
acn_balance
Check your ACN wallet balance. Requires full authentication (API key or wallet signature).
acn_call_history
View your recent capability execution history. Requires full authentication.
| Parameter | Type | Required | Description |
|---|
limit | number | No | Number of results (default: 10, max: 50) |
status | string | No | Filter by success or error |
capability | string | No | Filter by capability identifier |
Payment Flow via MCP
When an agent calls acn_execute for a paid capability:
- Agent calls
acn_execute with a capability identifier
- ACN returns
payment_required with amount, recipient, and unsigned transaction
- Agent signs and broadcasts the USDC transfer (via Wallet MCP or any wallet)
- Agent submits the tx hash via
acn_submit_payment
- ACN verifies the on-chain payment, executes the call, and returns the result
For anonymous agents, the sender’s wallet address is extracted from the on-chain transaction. This means your identity is established through payment — no upfront registration needed.
Using with Claude Desktop
See Claude MCP Integration for a step-by-step setup guide.
