AL
38 total tools · 1 server with elevated error rate6 servers observed
MCP Server-Centered Topology
An MCP server map should expose caller demand, tool surface, transport, and operational health.
Useful per server: which agents connect to it, how many tools it exposes, what sessions depend on it, where transport or latency adds risk, and what failures cluster around it.
Identity, adjacency, activity, and posture around one representative item.
Callers
Who depends on this server.
Claude Codeprimary agent
Cursorsecondary agent
alice@company.comfrequent user
Tool Surface
Which exposed tools matter most.
read_file318 calls
write_file204 calls
list_directory191 calls
MCP Server
filesystem v1.0.0
Broadly shared server whose tools shape the majority of code-oriented sessions.
18 sessions · 420 calls
Execution Context
Operational details that explain behavior.
http transportnetworked
local filesystemasset reach
todaylast seen
Watch For
Where health and risk can degrade.
web-search 3.4%compare error outlier
latency drifttool slowdown
unexpected callernew client
Transport
http
Tool surface
8 tools
Avg posture
0.2% error rate
Blast radius
shared by multiple agents
| Server | Version | Transport | Tools | Sessions | Total calls | Error rate | Last seen |
|---|---|---|---|---|---|---|---|
| filesystem | 1.0.0 | http | 8 | 18 | 420 | 0.2% | today |
| github | 0.6.2 | http | 12 | 9 | 84 | 1.1% | today |
| figma | 0.3.0 | http | 6 | 4 | 31 | 0% | today |
| postgres | 1.1.0 | stdio | 4 | 2 | 18 | 0% | yesterday |
| web-search | 2.0.1 | http | 3 | 6 | 44 | 3.4% | today |
| puppeteer | 0.4.0 | stdio | 5 | 1 | 8 | 0% | Mar 30 |