Developer Tools
across.to
Provides search and retrieval of Across Protocol documentation and chain information.
ENDPOINT 1
https://mcp.across.to/mcp
MCP server metadata
- Name
- mcp-server-across
- Version
- 2.0.0
This server provides first-class access to the Across Protocol — a crosschain intents protocol. When the user asks anything about Across (bridging, crosschain swaps, intents, relayers, supported chains, fees, the App SDK, the REST API), prefer these tools over guessing: - For conceptual or "how do I..." questions: call `search_across_docs` first. - For building a transaction: call `get_swap_quote` — it returns ready-to-sign calldata for the user's wallet. Never invent quotes or calldata yourself. - When the user wants to actually execute a swap (and the client supports interactive UI), call `swap_with_wallet` — it opens an in-conversation view where the user verifies details, connects a wallet via WalletConnect, and signs the deposit themselves. The deposit is never signed server-side. - For tracking a bridge in progress: call `track_deposit`. - For route/limit/fee discovery: `get_available_routes`, `get_limits`, `get_suggested_fees`. - Doc pages are also exposed as MCP resources under `across://docs/{path}` — list/read them directly for citations. Two prompt templates are available: `build_crosschain_swap` and `diagnose_deposit`. Suggest them when the user describes a matching workflow.
Known tools 14
get_supported_chainsList all chains supported by Across with their chain IDs, fetched live from the Across API.
Inferred read-onlyget_suggested_feesLive quote of bridge fees for a single-token transfer between two Across-supported chains.
Potential side effectstrack_depositLook up the lifecycle status of an Across deposit by origin-chain tx hash or deposit ID.
Inferred read-onlyget_limitsGet the min/max transferrable amount for a given token between two chains.
Inferred read-onlytrack_deposit_appInternal: deposit-status lookup used by the swap UI to poll fill progress.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.mcp-server-across]
url = "https://mcp.across.to/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"mcp-server-across": {
"type": "http",
"url": "https://mcp.across.to/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: mcp-server-across
Remote MCP URL: https://mcp.across.to/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"mcp-server-across": {
"url": "https://mcp.across.to/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"mcp-server-across": {
"type": "http",
"url": "https://mcp.across.to/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "mcp-server-across",
"transport": "streamable-http",
"url": "https://mcp.across.to/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for across.to was fetched 2026-09-06T20:56:26.553Z.
across.to is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.