Skip to main content
Glama

Related Servers

Alternatives to BoundaryXP MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables AI tools and agents to form contract-bound organizations, execute persistent task DAGs with independent audits, score decisions with counterfactual trees, run time-compressed world simulations, and control an on-demand localhost dashboard via stdio tools.
      6
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Bridges a planning and review client to DeepSeek Harness Desktop over local stdio MCP, letting users submit staged tasks with explicit goals, scope, and acceptance criteria for execution inside native DSH sessions, models, and approval boundaries. Exposes task submission, waiting, evidence retrieval, review, continuation, cancellation, and recovery tools so results are judged against traceable evidence from the current run.
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI agents to perform auditable A* reasoning, import world graphs, incorporate physical carrier constraints, and maintain a learning knowledge base through a zero-dependency local MCP stdio service.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to inspect and reverse-engineer large binaries through bounded stdio JSON-RPC 2.0 tools for graph queries, SSA facts, path solving, runtime grounding, and mod scaffolding.
      1
      AGPL 3.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to query a local code graph over stdio, so they can see what a Git change may affect, find related tests, routes and nodes, and cite evidence paths — read-only and fully on-machine.
      2 npm
      MIT

    TDQS

    B3.4/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools map to distinct resource+action pairs (project create/get/update, job get/cancel, result get/recheck, artifact get), and the dictionary family of six tools is differentiated by descriptions (discover / bind / lookup / format / validate / import). The riskiest overlaps are the preview-only vs persisting tools (bx_task_import, bx_task_validate, bx_project_create) and bx_project_update vs bx_task_validate, which an agent could misselect without reading the long descriptions carefully.

    Naming Consistency4/5

    Names follow a stable bx_<resource>_<verb> snake_case pattern throughout (bx_project_create, bx_job_get, bx_result_recheck, bx_dictionary_import), which is readable and predictable. Minor deviation: singular/plural resource mixing within the same family (bx_projects_list vs bx_project_get; bx_dictionaries_list / bx_dictionaries_bind vs bx_dictionary_lookup / bx_dictionary_format).

    Tool Count3/5

    21 tools is on the heavy side for the surface; each phase (discovery, projects, dictionaries, analysis, jobs, results, artifacts) has justification, but the dictionary sub-domain alone consumes six tools. The set is coherent rather than bloated, yet sits in the borderline 16-25 band.

    Completeness3/5

    Core lifecycle is largely covered: project create/get/update/list, analysis prepare/complete, job get/cancel, result get/recheck, artifact paging. However there is no project delete/archive, no job or result listing/history enumeration tool, and task-level editing only exists indirectly through bx_project_update, leaving dead ends for cleanup and discovery of prior runs.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues