Agent Registry MCP
Related Servers
Alternatives to Agent Registry MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceSelf-hosted governed project memory for coding agents, recording decisions, checkpoints, evidence, review state, and agent activity in PostgreSQL with pgvector while keeping maintainer control over what becomes reusable memory or instruction-grade guidance.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceA persistent, trust-scored project memory for AI coding agents, backed by PostgreSQL + pgvector, providing durable memory of architecture decisions, bug patterns, and coding conventions.26 npm1MIT
- AlicenseNot gradedqualityAmaintenanceProvides persistent project memory for AI coding agents, enabling context retention across sessions via event logging, briefing generation, and querying.MIT
- AlicenseNot gradedqualityDmaintenanceProvides AI coding assistants with persistent project memory to retain architectural decisions, code patterns, and domain knowledge across sessions. It stores data locally in a SQLite database, allowing agents to remember, recall, and manage project-specific context using full-text search.5 npmApache 2.0
- AlicenseBqualityAmaintenanceLocal-first, auditable memory for Codex, Claude Code, and MCP clients. It stores scoped user/project memory in SQLite or Postgres, serves read-only recall and inspection tools by default, and supports opt-in governed writeback with review and forget controls.8195 npm17MIT
- AlicenseNot gradedqualityBmaintenanceProvides AI coding agents with git-native persistent memory and a dependency-aware task graph, letting them record and fuzzy-recall architectural decisions, lessons, and gotchas while creating, claiming, and completing tasks that auto-unblock downstream work. Stores everything as plain JSON and Markdown committed inside the repository, so context stays branch-aware, team-shared, and reviewable in pull requests.0MIT
TDQS
Scored across 15 tools
Most tools clearly target a distinct resource+action pair (context/skill/project/memory/agent), and parallel search/get operations across resources are reasonably distinguishable. However, skill_resolve versus skill_get is ambiguous without descriptions, and memory_get versus memory_recent plus context_search versus context_get have overlapping retrieval semantics that an agent could easily misselect.
All 15 tools use consistent snake_case with a resource-first, action-second pattern (e.g. context_search, skill_get, memory_register, project_detect). The two *_status tools (registry_status, agent_status) fit the same resource_action convention rather than deviating from it.
15 tools is at the upper end but well-scoped for a registry spanning six resource domains (context, skill, project, memory, registry, agent), with roughly 2-3 tools per domain and no obvious redundancy.
The surface covers registration, lookup, and search for some resources, and memory has a full lifecycle including memory_transition. But there is no skill_register, no context_register, no update/delete operations for projects or contexts, and agent support is limited to a single status tool, leaving notable lifecycle gaps.