ArrivalGraph MCP Server

by kurious8282 Your server? Claim it

not responding

ArrivalGraph is listed as active in the registry but did not answer our last check. It exposes 1 tools.

Seoul building context for AI agents, delivery/logistics, maps and robotics.

Uptime history 60 hours of history · worst hour 0%

60 hours agonow

54.9%

Uptime 24h

50 of 91 checks

Tools

read from the server

196 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 21 September 2026. No other catalogue keeps this.

21 Sep a tool description was rewritten get_arrival_context

21 Sep a tool changed version

ArrivalGraph does not always answer

Over the last week it answered 81.8% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add arrivalgraph --transport http https://ozeejewwpjmabshxyitc.supabase.co/functions/v1/arrivalgraph-mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "arrivalgraph": {
      "url": "https://ozeejewwpjmabshxyitc.supabase.co/functions/v1/arrivalgraph-mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.arrivalgraph]
url = "https://ozeejewwpjmabshxyitc.supabase.co/functions/v1/arrivalgraph-mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "arrivalgraph": {
      "url": "https://ozeejewwpjmabshxyitc.supabase.co/functions/v1/arrivalgraph-mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "arrivalgraph": {
      "url": "https://ozeejewwpjmabshxyitc.supabase.co/functions/v1/arrivalgraph-mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

arrival

get_arrival_context

Use when an agent has a Seoul WGS84 destination coordinate and needs the actual matched building, floors, official elevator-presence fact, footprint size, registry ID, or structural arrival context for delivery/logistics, map enrichment, or physical-world planning. Do not use for general POI search, business discovery, traffic ETA, or turn-by-turn routing. Unverified entrance, elevator-location, parking-entry, loading-zone, access-rule, and observed-time facts remain null rather than inferred.

Endpoints

URL	Transport	State	Latency	Checked
https://ozeejewwpjmabshxyitc.supabase.co/functions/v1/arrivalgraph-mcp	streamable-http	answering	176 ms	8 min ago

Alternatives to ArrivalGraph

same job, measured the same way

FairMind Project Context

by fairmind

Project memory for coding agents: requirements, decisions, code graph and delivery telemetry.

answering

Fixmap

by aryamthecodebreaker

Deterministic local-first context and impact maps for coding agents from tasks, issues, and diffs.

107 installs/wk local only

Cuemap MCP

by cuemap-dev

Local memory and context retrieval for AI agents through CueMap.

343 installs/wk local only

Cartograph

by anthony-maio

Repo analysis for coding agents with ranked files, dependency maps, and task-scoped context.

47 installs/wk local only

Outflow MCP

by laurells

MCP server exposing an Outflow workspace's live architecture graph as context for AI coding agents

34 installs/wk local only

Cgraphy

by pmgarg

Code knowledge graph over MCP: token-budgeted context for AI coding agents.

63 installs/wk local only

agentdocs

by titov-d

Fresh, source-verified docs for building MCP servers and Claude agents, for AI coding agents.

38 installs/wk local only

Synap Memory

by maximem

Persistent memory for AI agents — log and recall conversation context over MCP.

4 tools answering

ArrivalGraph — questions

Answers built from our own checks of this server.

What can ArrivalGraph do?

It exposes 1 tools, read directly from the server on our last check. Among them: get_arrival_context. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is ArrivalGraph working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 50 of 91 checks got a reply (54.9%), average response time 196 ms. The bar chart above shows every period we have measured.

The registry lists ArrivalGraph as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect ArrivalGraph?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does ArrivalGraph need an API key?

No. ArrivalGraph completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is ArrivalGraph?

It answers our handshake in 196 ms on average, which is faster than 70% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.