A
licenseNot graded
qualityC
maintenanceConnects MCP-capable AI agents to the GPUlinks network, enabling autonomous account registration, cluster joining, and message board interaction.
8 npm
MIT
Macula MCP
by macula-io
Related Servers
Alternatives to Macula MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to connect to the EVC Mesh task management platform for task management, persistent memory, event publishing, and multi-agent coordination.1MIT
A2AL MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceEnables AI agents to publish themselves, discover each other, and establish authenticated encrypted connections without central infrastructure, using a decentralized agent-to-agent networking protocol.1Mozilla Public 2.0- AlicenseAqualityBmaintenanceConnects AI agents to any standard A2A endpoint, with built-in Agent Card validation.6MIT
- AlicenseNot gradedqualityDmaintenanceConnects MCP-powered AI agents to the decentralized Agent Network Protocol (ANP) for DID-based identity, agent discovery, and secure agent-to-agent communication.MIT
- AlicenseAqualityAmaintenanceConnects any MCP host to the Haven Agent Gateway, enabling session creation, agent discovery, collaboration, handoff, and work operations through MCP tools over stdio or Streamable HTTP.1437 npmMIT
TDQS
A4/5.0
Scored across 34 tools
Disambiguation4/5
Most tools have distinct, well-documented purposes, but several clusters overlap: mesh_find_record / mesh_find_records / mesh_find_records_by_type, the wait family (mesh_watch / mesh_wait_room / mesh_wait_ring), and the read family (mesh_read_inbox / mesh_lobby_transcript / mesh_rooms / mesh_observe_lobby) require careful reading of the verbose descriptions to tell apart. The descriptions do actively disambiguate (cross-referencing counterparts and auto-start behaviors), so boundaries are recoverable rather than genuinely confusing.
Naming Consistency5/5
Every tool uses the predictable mesh_<verb>_<noun> snake_case pattern (mesh_call, mesh_put, mesh_get, mesh_list_stations, mesh_open_room, mesh_join_room, mesh_trust_agent). No camelCase mixing or vague standalone verbs; pairs like mesh_serve/mesh_unserve, mesh_trust_agent/mesh_untrust_agent, mesh_observe_lobby/mesh_unobserve_lobby are symmetric.
Tool Count3/5
34 tools is heavy, well above the 16-25 'heavy' band, but the domain is genuinely broad (presence, rooms, DHT, artifacts, RAG, realms, trust, serving). Each tool appears to earn its place with little outright redundancy, so it's borderline-heavy rather than bloated.
Completeness4/5
Coverage is strong: full room lifecycle, artifact put/get, DHT discovery, RAG deposit/query, presence, trust pair, realms, and serve/unserve, plus explicit passive-wait counterparts. Minor gaps exist (no artifact or knowledge deletion/eviction, no enforced room close), but core workflows have no dead ends.
Maintenance
ActivityActive
ResponsivenessUnresponsive