Skip to main content
Glama
HLIntel

TheaOS mcp

by HLIntel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to TheaOS mcp

No user-submitted related servers found.

    Related Servers

    • corbat by corbat-tech

      corbatofficial

      corbat-tech
      A
      license
      A
      quality
      D
      maintenance
      Policy and quality engine for AI coding agents that enforces team coding standards and provides validation gates for agent-assisted software delivery.
      7
      54 npm
      5
      MIT

    • agentseed

      Morningstar202604
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to enforce spec-driven development and verify code before it is marked done, using six tools that catch invented APIs, scan for hallucinated content, check plugin conformance, sandbox-run tests, validate schemas, and record audit evidence.
      771 npm
      8
      PolyForm Noncommercial 1.0.0

    • Magga

      8NobleTruths
      A
      license
      Not graded
      quality
      C
      maintenance
      Magga lets coding agents prove their changes before claiming they’re done by building the code and verifying that newly added tests fail before the fix and pass after it. It returns evidence-backed verdicts through the verify_change tool and supports 16 languages, including Rust, Go, Python, Solidity, and C/C++.
      8 npm
      Apache 2.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.1/5.0

    Scored across 15 tools

    Disambiguation2/5

    The generic headron tool can invoke the same verbs as port, route, gate, steps, failures, successes, and proof, so agents have no clear rule for choosing between the generic and specific tools. mind_direct also overlaps heavily with mind_classify, mind_plan, mind_route, and mind_search.

    Naming Consistency3/5

    The mind_* tools form a consistent prefixed family, and all names are lowercase snake_case, but the rest of the set mixes bare nouns (port, gate, proof, failures, successes) with a product name and no predictable verb_noun pattern.

    Tool Count4/5

    Fifteen tools is within a reasonable range for a workflow/orchestration server, but the generic headron command plus many thin wrappers means the count is slightly higher than needed.

    Completeness4/5

    The surface covers discovery, routing, gating, proof, failure/success lessons, agent selection, search, health, and receipts. It is missing explicit execution/verification tools, but the server is intentionally read-only, so the remaining gaps are minor.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources