Sato Hub
MCP

Across MCP

Official Across Protocol hosted MCP: docs search, chain data, and live bridge fees at mcp.across.to.

  • Sato Score74
  • ChainsMultichain
ActiveSelf-ReportedRecent · 3mo ago

Across MCP is an open-source MCP server by Across Protocol, with last code activity on 2026-07-20 (Recent). Sato Score 74/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-15. How the score works →

See how to install Across MCP →

Last commit Jul 20, 2026 · ★ 1

Listed from across.to on 2026-07-13. Install: not attempted. Evidence →

Next step

Watch Across MCP

One email if what we observe changes — its endpoint stops answering, or the listing is retired. Nothing else.

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Run Sato Hub Preflight on https://mcp.across.to/mcp before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

Across Protocol runs a hosted MCP server (mcp.across.to/mcp) that exposes full-text search over Across documentation, supported-chain lookups, real-time bridge fee data, and code samples. A self-hostable version was published at github.com/across-protocol/mcp-server-across; that repository returned 404 on 2026-09-26, so only the hosted endpoint is listed. An agent builder plugs it in to give an agent live cross-chain bridging context and fee data from Across without maintaining its own docs/fee cache.

Sato Score

74/100· High

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
35/35
Code transparency
9/20
Interface verifiability
10/10
Docs & demo
6/10
Listing transparency & provenance
11/15
Independent verification
3/10

Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety).

Evidence — listed vs checked · what the words mean

Listed from across.to on 2026-07-13. Install: not attempted.

ClaimValueEvidenceSourceChecked
Chains supportedMultichainself-reporteddocs.across.toas of 2026-10-15
Verification statusSelf-Reported — not independently reviewedself-reportedacross.toas of 2026-10-15
Recent activitylast commit 2026-07-20observedacross.to2026-10-15
Install worksdocumented by the project, not run by Sato Hubnot attempted by Sato Hubself-reporteddocs.across.toas of 2026-07-14
MCP endpoint answersanswered — 14 tools listedobservedmcp.across.to2026-10-15
Daily check record90 of 90 daily checks since 2026-07-17 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-14
Deploys asHosted API (Streamable HTTP), npm (npx, stdio), Dockerconfidence 0.90self-reportedgithub.com/across-protocol/mcp-server-acrossas of 2026-07-14
Works withClaude Desktop, Claude Code, Cursor, VS Code Copilot, Codex, Windsurfconfidence 0.90self-reportedgithub.com/across-protocol/mcp-server-acrossas of 2026-07-14
Sato Score74/100 (High)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-15

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — as documented by the project, not run by us

Runtime: remote

claude mcp add --transport http across-docs https://mcp.across.to/mcp
{"mcpServers": {"across-docs": {"url": "https://mcp.across.to/mcp"}}}
Add to CursorAdd to VS Code
claude mcp add --transport http satohub-across-mcp https://mcp.across.to/mcp

A remote server: your client connects to the project's endpoint. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.

Read from the project’s own docs as of 2026-07-14. What a deploy spec is →

Tool inventory — 14 tools, probed live 2026-10-15

  • search_across_docs — Full-text search across the Across Protocol documentation. Use for any conceptual or how-to question about Across.
  • get_page — Get the full content of a specific Across documentation page. Accepts a path like '/reference/api-reference' or a keyword match. Prefer reading the `across://docs/...` resource directly when the path
  • get_code_examples — Get code examples from Across docs. Filter by topic like 'sdk', 'swap', 'deposit', 'viem', 'ethers'.
  • recrawl_docs — Kick off a background re-crawl of all Across documentation pages. Returns immediately; the index updates when the crawl completes.
  • get_supported_chains — List all chains supported by Across with their chain IDs, fetched live from the Across API.
  • get_api_reference — Get the Across REST API endpoint catalog. Pass an `endpoint` to filter; leave empty to list all.
  • get_suggested_fees — Live quote of bridge fees for a single-token transfer between two Across-supported chains.
  • get_swap_quote — Build a crosschain swap on Across. Returns the expected output, fees, and ready-to-sign calldata (`approvalTxns` + deposit `tx`). The client/user signs and broadcasts.
  • track_deposit — Look up the lifecycle status of an Across deposit by origin-chain tx hash or deposit ID.
  • list_deposits — Return recent Across deposits for a given depositor address.
  • get_available_routes — Discover supported (origin, destination, token) routes. All filters are optional; omit to list every route.
  • get_limits — Get the min/max transferrable amount for a given token between two chains.
  • swap_with_wallet — Open an interactive crosschain-swap view in the conversation. Fetches a live Across quote and renders a UI where the user verifies details, connects their wallet, and signs the deposit themselves. Use
  • track_deposit_app — Internal: deposit-status lookup used by the swap UI to poll fill progress.
Answers a handshake
yes · 2026-10-15
Answers a call
yes — get_code_examples returned in 104 ms

Live probe verifies the interface responds — not what the tools do, their safety, or their output quality. The call is one read-only tool named by this server's own list (list_/get_/search_, no mutating verb anywhere in the name, no required arguments and none that look like a key, an address or an amount), asked once a day with no arguments. Not asked is not a failure.

Observed record — 91 daily checks since 2026-07-17

100%of 91 checks since 2026-07-17 succeeded
Currently responding for 91 days
Succeeded
91
Failed
0
Their error
0
Unattributed
0

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 46 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.

Last 30 days — to 2026-10-15, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
14
from the server's own tools/list · 29/30 days
Sato Score
74
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains
Multichain
Agent types
MCP Server, Data Provider
Open source
Yes
Deploys as
Hosted API (Streamable HTTP), npm (npx, stdio), Docker
Works with
Claude Desktop, Claude Code, Cursor, VS Code Copilot, Codex, Windsurf
Last checked
2026-10-15

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#bridge#cross-chain#mcp#docs#across
See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to Across MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Sep 26, 2026
    Edited: github url, description long
  2. Jul 18, 2026
    Sato Hub began tracking this listing
  3. Jul 14, 2026
    Edited: mcp endpoint url
  4. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  5. Jul 13, 2026
    Listed on Sato Hub

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about Across MCP

Is Across MCP open source?
Yes. Across MCP is open source under the MIT license. Checked as of 2026-10-15.
Which chains does Across MCP support?
Across MCP lists support for Multichain as of 2026-10-15.
Is Across MCP still maintained?
The most recent code activity Sato Hub observed was on 2026-07-20 (last commit 2026-07-20), which Sato Hub labels "Recent". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
How do I install or run Across MCP?
remote. Install: claude mcp add --transport http across-docs https://mcp.across.to/mcp. Entry: {"mcpServers": {"across-docs": {"url": "https://mcp.across.to/mcp"}}}. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (https://mcp.across.to/mcp).
Is Across MCP verified on Sato Hub?
Sato Hub holds one earned check for Across MCP: Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety). Its Sato Score is 74 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "Across MCP — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/across-mcp

Data last refreshed 2026-10-15; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.