No user-submitted related servers found.
Scored across 36 tools
The set is organized into clear subsystem families (fraggate/mesh/memory/chainlock/runtime_session), and each tool's description aggressively points to its specific role. However, there are several near-overlapping clusters—three exec paths (fraggate_call, runtime_run, runtime_session_exec), multiple listing tools (fraggate_list, runtime_software, runtime_bundle), and paired recall tools (memory_recall vs chainlock_recall)—so an agent can still misroute without reading the long descriptions carefully.
All names use a consistent lowercase snake_case domain-prefix convention (fraggate_*, mesh_*, memory_*, chainlock_*, runtime_*), which makes the tool families predictable. Minor deviations exist—read-only nouns like runtime_skill, runtime_manifest, and mesh_nodes sit alongside action verbs, and mesh_disable actually refuses rather than disables—but the overall pattern is coherent.
36 tools is well beyond the 25-tool threshold and will impose a heavy selection burden on an agent even though the server spans several subsystems. The count reflects five or six distinct domains bundled into one MCP surface, and could reasonably be split into separate servers (FragGate, mesh, chainlock, memory, session).
Each subsystem has a fairly complete lifecycle: FragGate has list/describe/verify/call, mesh has status/nodes/join/heartbeat/leave/enable, ChainLock has append/tip/recall/verify/seal, memory has observe/calibrate/resolve/recall/get, and raw sessions have open/policy/exec/close/receipts. The main gaps are deliberate (no memory_delete/chainlock_delete, mesh_disable refuses by design), and there is no direct product install/remove tool, though those ops appear reachable through fraggate_call.