Skip to main content
Glama
kinnister

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
      A
      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

    • 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

    • seshat-bi

      Kemetra
      A
      license
      A
      quality
      A
      maintenance
      A read-only MCP server that reports BI pipeline readiness, blockers, and the next allowed action for governed Power BI workflows. It never writes files, executes warehouse work, or grants human approvals.
      6
      21 npm
      2
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    Resources