List your agent

Topolograph

MCP server● Hosted · onlinev1.7.0

OSPF and IS-IS topology, paths, failure impact, change events, MPLS TE and BGP from Topolograph

Reviews

No review yet. Used Topolograph? Be the first to help others choose.

What it does

Topolograph is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.7.0
PriceNot in the registry
First seen21 Nov 2026
Last checked1h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1h ago (live check)

Hosted endpoint

  • https://topolograph.com/mcp streamable-http

Required: Authorization (get it from the publisher)

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "topolograph": {
      "url": "https://topolograph.com/mcp",
      "headers": {
        "Authorization": "<your Authorization>"
      }
    }
  }
}

Replace the values in <angle brackets>.

Reliability

Re-tested about every 3 days · last check 1h ago
Insufficient observations1 conclusive check in 30 days; a figure is shown from 10
1 / 0Answers / failures, 30 days
No key neededAccess status (latest answer)
Observed test history · one mark = one check
21 Nov21 Nov
AnsweredAnswered, key requiredNo valid answer

Observed endpoint availability: the share of our conclusive checks that got an answer. A request for a key or sign-in counts as an answer (the server is up, its access is protected). Timeouts, unreachable endpoints, server errors and invalid MCP replies count as failures; rate-limited checks and checks during our own incidents are not counted. This is what we observed at each check, not continuous uptime: an outage between two checks may go unseen. The 90-day figure will appear once 90 days of checks exist (checks since 21 Nov 2026). How we measure

Live check

Electra Index connected to the hosted endpoint 1h ago

ONLINE Topolograph answered an MCP connection on 21 Nov 2026 and introduced itself as OSPF_Analyser 1.5.1 (MCP protocol 2025-06-18).

32 tools offered to AI assistants

  • get_graph_by_time · Fetch a graph by graph name from Topolograph API. graph name is a string with included date and hours and number of hosts, i.e 01Sep2025_12h44m36s_8_hosts graph_time (str, optional): The graph time to filter by. Use latest if it's not speci
  • get_all_graphs · Description: This tool retrieves available graphs from the Topolograph API with optional filtering. This tool is a first step for all analysis. Each graph reports two monitoring flags: - is_monitored: the graph was received from a watcher (
  • get_network_by_graph_time · Fetch network data by explicit graph_time. Description: This tool retrieves network information for a specific graph time. Universal tool that works with both OSPF and IS-IS protocols. Use 'node_id' to find all networks terminated by a spec
  • get_graph_status · Get the status of a graph based on its health. Description: This tool returns the status of a graph including connectivity information and various event counts. Input fields: graph_time (str): Name of graph = The graph time to get status fo
  • get_network_events · Description: This tool returns networks events: network up/down and network cost change events. Use this tool only to get details about networks events. Events exist ONLY for watcher-monitored graphs (is_monitored=true). Manually uploaded o
  • get_adjacency_events · Description: This tool returns links/adjacencies events including nodes/hosts up/down events. Use this tool only to get details about nodes/hosts events. Events exist ONLY for watcher-monitored graphs (is_monitored=true). Manually uploaded
  • get_events_timeline · Description: This tool returns node/host up/down events already grouped into chronological time waves (server-side), so you can narrate a network incident ("instability started at T from device X; a flapping burst from device Y; reconverged
  • get_nodes · Get a paginated list of nodes/routers from a graph. Description: Returns structured node data including hostname, system ID, network count, areas, IS-IS flag, and node_attributes (role flags). Supports pre-filtering by protocol, watcher ori
  • get_edges · Get edges from a graph with optional filtering. Description: Returns a paginated list of edges. Supports graph-level pre-filters (protocol, watcher, area) and per-edge attribute filters. Useful for queries like "all IS-IS L1 edges" or "edge
  • get_lsps · List MPLS TE LSP tunnels, or get one tunnel by name. Description: Each returned path already carries its last CSPF placement outcome: placed (bool), reason (human-readable explanation, null when placed), reason_code (machine-readable failur
  • get_shortest_path · Calculate the shortest path from one node to one or several destinations. Description: Plain IGP shortest path by default. For "what if this link is down" backup-path analysis, use get_edge_failure_reaction instead -- that question now has
  • get_cspf_path · Constrained-shortest-path (CSPF) query between two nodes. Description: Answers "will an LSP with these constraints fit, and which path would it take" -- an on-demand computation, exactly like get_shortest_path, just over a graph pre-filtere
Show 20 more
  • get_node_failure_reaction · Predict the whole-network impact if one or more routers go down. Description: Whether the graph stays connected and which links see more or less traffic once these routers fail. A simulation only: nothing is changed in the graph. Input fiel
  • get_edge_failure_reaction · Predict the whole-network impact if one or more links go down. Description: Same shape as get_node_failure_reaction, for links instead of nodes: whether the graph stays connected, and the traffic rerouting pattern (which links see more/less
  • get_graph_analysis · Whole-graph report: central routers, most loaded links, single points of failure and more. Input fields: graph_time (str): The graph time kind (str): central-nodes, most-loaded, single-point-of-failure, fault-tolerant, heatmap, unsym-paths,
  • get_path_tree · The shortest-path tree rooted at one router, equal-cost paths included. Input fields: graph_time (str): The graph time node (str): Node name, hostname or IS-IS System ID direction (str, optional): "out" for paths from the node (default), "i
  • list_bgp_graphs · List BGP graph epochs (one per BMP collection cycle), newest first. Input fields: page (int): Page number, 1-indexed (default: 1) per_page (int): Items per page (default: 50) Equivalent to GET /bgp-graphs.
  • get_bgp_graph · Fetch one BGP graph epoch by bgp_graph_time. Equivalent to GET /bgp-graph/{bgp_graph_time}.
  • list_bgp_nodes · List the BGP speakers of a BGP graph epoch. Input fields: bgp_graph_time (str): The BGP graph epoch to query role (str, optional): Filter by node role asn (str, optional): Filter by autonomous system number page (int): Page number, 1-indexe
  • list_bgp_sessions · List BGP peering sessions of a BGP graph epoch. Input fields: bgp_graph_time (str): The BGP graph epoch to query igp_relation (str, optional): Filter by relation to the IGP topology (intra-domain, inter-domain, external) bgp_session_type (s
  • search_bgp_routes · Search BGP routes, one row per distinct RFC 4271 9.1 path. Description: Without router_id, searches the whole BGP graph's route table (GET /routes). With router_id, scopes the search to that speaker's own resolved RIB view (GET /node/{route
  • get_bgp_node_route_summary · Route totals for one BGP speaker: its resolved RIB view size, a per-RIB-tag histogram, and how many routes it advertised (Adj-RIB-Out). Equivalent to GET /bgp-graph/{bgp_graph_time}/node/{router_id}/routes/summary.
  • get_bgp_route_state · Point-in-time BGP route state, reconstructed from stored events. Input fields: bgp_graph_time (str): The BGP graph epoch to query at (str, optional): ISO 8601 timestamp; defaults to now Equivalent to GET /bgp-graph/{bgp_graph_time}/routes/s
  • compare_bgp_routes · Diff BGP routes between two instants: one row per differing route. Input fields: bgp_graph_time (str): The BGP graph epoch to query (the t1 epoch) t0 (str): ISO 8601 timestamp, the earlier instant t1 (str): ISO 8601 timestamp, the later ins
  • get_bgp_events_timeline · BGP monitoring events (session up/down, route churn), grouped into a timeline by default. Input fields: bgp_graph_time (str): The BGP graph epoch to query start_time (str, optional), end_time (str, optional): ISO 8601 window last_minutes (i
  • list_bgp_bindings · List the BGP-to-IGP graph bindings known for a BGP graph epoch. Output fields: dict with key: items (list of BgpBinding) Equivalent to GET /bgp-graph/{bgp_graph_time}/bindings.
  • get_bgp_binding · Fetch one BGP-to-IGP graph binding: which IGP graph this BGP epoch is correlated with, and how confidently (matched_rids, source_coverage, state). Equivalent to GET /bgp-graph/{bgp_graph_time}/{graph_time}/binding.
  • resolve_route · Resolve the path a router would take to a destination, one row per routing decision -- hands off between static/BGP/IGP/LSP whenever one of them overrides the plain SPF path. Input fields: graph_time (str): The IGP graph to resolve against
  • get_vrf_inventory · Router-scoped VRF inventory as of an IGP graph: names, route distinguishers, and per-address-family import/export route targets. Input fields: graph_time (str): The IGP graph time router_id (str, optional), rd (str, optional): Filters Outpu
  • list_vpns · Answers "which VNI/VRF exists on which leaf": the fabric-wide VPN/VRF/VNI inventory of the BGP epochs bound to this graph, or one router's own view. Input fields: graph_time (str): The IGP graph time router_id (str, optional): Scope to one
  • get_routes · Answers "where is MAC/IP X", VRF/VNI contents, and hosts behind a leaf: routes of the BGP epochs bound to this graph (the latest of every source), current state by default. Input fields: graph_time (str): The IGP graph time, or the name of
  • get_route_events · Answers "did MAC/IP X move, from where, when": route event history (add/withdraw/MAC-move) of the BGP epochs bound to this graph. Input fields: graph_time (str): The IGP graph time start_time (str, optional), end_time (str, optional): ISO 8

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Re-tested about every 3 days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://topolograph.com/mcpDECLAREDSRC-001 Official MCP Registry1h ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry1h ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry1h ago
Websitehttps://topolograph.comDECLAREDSRC-001 Official MCP Registry1h ago
Repositoryhttps://github.com/Vadims06/topolograph-mcp-serverDECLAREDSRC-001 Official MCP Registry1h ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry1h ago
Version1.7.0DECLAREDSRC-001 Official MCP Registry1h ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry1h ago

Change history

  • NEW21 Nov 2026
    first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run Topolograph? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor TopolographLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of Topolograph?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/topolograph?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/topolograph/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about Topolograph

How do I connect Topolograph?

Use the hosted endpoint https://topolograph.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

Does Topolograph need an API key or token?

Yes. The registry entry lists a required value: Authorization. Get it from the publisher.

What tools does Topolograph offer?

When Electra Index connected on 21 Nov 2026, it listed 32 tools: get_graph_by_time, get_all_graphs, get_network_by_graph_time, get_graph_status, get_network_events, get_adjacency_events, get_events_timeline, get_nodes and more. The full list is in "Live check" above.

Is Topolograph online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1h ago.