Skip to main content
Glama
Sign In
agentic-os-mcp

agentic-os-mcp

by kinnister
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to agentic-os-mcp

No user-submitted related servers found.

    Related Servers

    • turva-mcp

      erekola
      A
      license
      Not graded
      quality
      B
      maintenance
      Read-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
    • vercy

      vercyofficial

      ver-cy
      A
      license
      Not graded
      quality
      B
      maintenance
      A 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.
      Apache 2.0

    • McpApp

      krok1029
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides 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
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4.6/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool has a distinct role: three catalog/list tools target different content domains (role presets, QE blueprints, SDLC phases), while search_methodology is full-text search and get_document is exact-URI fetch. The descriptions explicitly state the boundary (presets are JSON and never appear in search; get_document resolves only exact URIs), so misselection is unlikely, though the three similarly-shaped list_* tools require reading descriptions to tell apart.

    Naming Consistency5/5

    All seven names are snake_case verb_noun (or verb_resource) constructions: list_presets, get_document, list_qe_blueprints, list_sdlc_phases, plan_install, run_doctor, search_methodology. No casing or stylistic drift, and the verb accurately signals the operation in every case.

    Tool Count5/5

    Seven tools is well within the ideal 3-15 range and every one earns its place in a documented discover→read→plan→audit flow. Nothing is redundant or filler.

    Completeness4/5

    The surface covers discovery (search, three catalog listers), retrieval (get_document), planning (plan_install), and verification (run_doctor), which fits a deliberately read-only advisory server. The one real gap is that there is no browse/index tool for methodology documents themselves — discovery depends on already knowing a search term — and run_doctor can never yield a 'passed' verdict server-side, which is a documented but structural dead end.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources