A
licenseNot graded
qualityC
maintenanceA read-only MCP server for AI coding agents to inspect repositories, audit code quality, route engineering skills, and plan safe issue/PR workflows.
1
MIT
agentic-os-mcp
by kinnister
Related Servers
Alternatives to agentic-os-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceA deterministic, read-only MCP server that lets coding agents search Git-backed architecture decision records and retrieve decisions governing specific files. It includes rejected and superseded decisions, with no model, network, or write access.20Apache 2.0
- AlicenseNot gradedqualityAmaintenanceRead-only MCP server that answers questions about turva.dev from its published data. Five tools return JSON: the service catalog with prices, contact and operator details, engagement principles and dated agent-readiness and security evidence with verification links. Connect over Streamable HTTP. You need no API key. The server does not scan other websites or run audits.MIT
- AlicenseNot gradedqualityBmaintenanceA read-only MCP server over a published model catalogue that lets agents search and resolve models, fetch overlay profiles, definitions and citations, and check memory records against a governance overlay through the same code path as the CLI.100 PyPIApache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides a local-first MCP server for AI-native software delivery, enabling structured specifications, human approval gates, controlled repository operations, verification evidence, review, and traceability.Apache 2.0
- AlicenseAqualityDmaintenanceRead-only MCP server providing AI access to verifiable web, GitHub, and local sources, plus a managed fantasy entity catalog, with strong security and provenance tracking.101MIT
TDQS
A4.7/5.0
Scored across 7 tools
Disambiguation5/5
Each tool targets a distinct operation: searching/fetching methodology documents, listing different catalogs (presets, blueprints, phases), planning an install, and auditing. No two tools have overlapping purposes.
Naming Consistency5/5
All tool names follow a consistent verb_noun snake_case pattern with verbs like search, get, list, plan, run. The naming is uniform and predictable.
Tool Count5/5
Seven tools cover the essential operations for the methodology/pipeline domain: documentation access, catalog browsing, install planning, and auditing. The count is well-scoped without unnecessary tools.
Completeness4/5
The tool surface comprehensively covers read operations and planning. Writing is intentionally left to the host, which is a design choice. No obvious gaps for the server's stated purpose.
Maintenance
ActivityMaintained
ResponsivenessNo issues