Swarmscope
Related Servers
Alternatives to Swarmscope
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceAgent-first knowledge graph MCP server that provides 25 tools for managing a knowledge graph with nodes and edges, plus a human-readable dashboard for LLMs and AI agents.331 npmApache 2.0
- AlicenseBqualityAmaintenanceLocal MCP event log for multi-agent workspaces, enabling structured event publishing, cursor-based polling, and status checks via SQLite-backed sidecar.10561 PyPI1MIT
- AlicenseNot gradedqualityCmaintenanceMCP-native agent-to-agent messaging hub for AI swarms. Agents communicate via channels and DMs through MCP protocol — zero SDKs needed. Includes web UI, semantic search, analytics dashboard. Single Go binary, local-first.2Apache 2.0
- FlicenseNot gradedqualityDmaintenanceA local-first MCP server that gives AI coding agents runtime visibility and AI-managed debug logging. It replaces blind print() debugging by turning runtime execution into causal chains, allowing agents to instantly locate bugs by finding missing .success events in Python and TypeScript code. Single binary with MCP, CLI, and HTTP interfaces.-
- AlicenseNot gradedqualityDmaintenanceA local MCP server for AI agents to log activities, query logs, and leave notes for each other, featuring a web UI and REST API.MIT
- AlicenseAqualityAmaintenanceAn MCP server that records agent execution metrics and exposes a Context Window Explorer to visualize exactly what entered the model's context window across sessions, tokens, and tool calls.83MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: report_event writes events, list_events reads raw events with pagination/filters, and get_network reads aggregated agent-edge topology. The descriptions make the boundary between raw events and aggregated network data explicit, so misselection is unlikely.
All three tools follow a consistent verb_noun snake_case pattern: get_network, list_events, report_event. No mixed conventions or vague verbs are present.
Three tools cover the minimal complete surface for this domain: ingest, list, and network view. Each tool earns its place, and the small set is easy to scan without redundancy.
The core lifecycle is covered (write events, read events, view derived network), but there are minor gaps: no direct event-by-id lookup, no pagination for get_network beyond the 200-edge cap, and no option to include test traffic in network views. Agents can work around most of these using list_events filters, but some dead ends remain.