Topolograph BGP Topology Analysis

pyats-routing, pyats-junos-routing and multivendor-device-query each read one live device's BGP table. This one reasons over BGP topology Topolograph has already collected via BMP — speakers, sessions, the route table across every reporting peer, VRF/VPN placement, and whether that BGP epoch actually corresponds to a stored IGP graph.

It answers "what does BGP believe the topology and route state are" — not "what is in this router's BGP table right now."

Remote, read-only

Same server as topolograph-igp-analysis (spec 119): topolograph-mcp is a remote HTTP MCP registered in config/openclaw.json, no local server, fronting your own Topolograph instance (TOPOLOGRAPH_MCP_URL, default https://topolograph.com/mcp), bearer TOPOLOGRAPH_API_TOKEN. No second credential — if the IGP skill already works, this one does too.