Real-time Agent Discovery and Connection Tracking
How does network scanning work from a webpage?
All scanning happens server-side via the backend API for security and capability reasons.
MCPs are discovered from three layers and merged into one registry below. Click Refresh on any source to pull the latest data.
botcomponent.content for every Copilot Studio agent.
Extracts connector endpoint URLs and maps them to the agent that uses them.
Manually register a known MCP server. Once registered, all connections to it are tracked through the governance layer.
π‘ Optionally: start a standalone MCP server
Built-in demo tools already work. For a real separate server, run:
nohup bash start_local_mcp.sh > mcp_server.log 2>&1 &
Tools available (via governance layer):
Live tool calls routed through the governance layer β auto-refreshes every 5s
No MCP traffic yet. Test a tool above or use an agent to call MCP tools.
| Rule Name | Source Pattern | Destination Pattern | Action | Priority | Status |
|---|---|---|---|---|---|
| No rules configured | |||||