Skip to main content
Glama

Related Servers

Alternatives to corexense-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables deterministic verification of AI agent decisions and actions, providing PASS/FAIL/ABSTAIN verdicts with replayable proofs and an optional signed receipt ledger.
      5 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to run disciplined hunts over public data, enforcing evidence ledgers, calibration controls, novelty checks against catalogues and literature, and fresh-eyes review before any claim is trusted. Human-only decisions such as waivers and expert attestations stay out of reach of the agent.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Lets an assistant read recorded production AI agent runs — steps, model and tool calls with arguments, and outcomes — along with the findings of comparison runs that checked a prompt or model change against those recordings, and verify a signed evidence bundle offline with no account or network. It is strictly read-only: no tool starts a replay or comparison, so nothing can spend money or act without a person deciding.
      5
      Apache 2.0
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to verify technical claims against supplied evidence, identify unsupported assumptions and contradictions, and recommend the smallest next check before acting.
      5
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Gives any agent eyes and ears by indexing video, audio, and screen activity into searchable, timestamped frames, transcripts, and OCR text that answers can cite. It also evaluates frozen verification contracts over file digests, JSON values, SQL results, HTTP responses, and DOM state to return a deterministic verdict from a separate process.
      MIT

    TDQS

    C2.9/5.0

    Scored across 5 tools

    Disambiguation3/5

    Three of the five tools (review_scenario, review_episode, review_simulation_episode) share the same 'review_*' verb and closely related semantics; descriptions differentiate them (local qualification vs. synthetic episode vs. FIRA replay audit), but the scenario-vs-episode boundary remains fuzzy and invites misselection. list_scenarios and explain_belief are clearly distinct.

    Naming Consistency5/5

    All five names follow a consistent snake_case verb_noun pattern (list_scenarios, review_scenario, explain_belief, review_episode, review_simulation_episode). No mixed conventions or casing deviations.

    Tool Count5/5

    Five tools is well within the sweet spot for a narrowly scoped decision-review server. Each tool maps to a distinct capability (enumeration, review, explanation, episode audit, simulation audit) and none appear redundant padding.

    Completeness3/5

    The surface covers enumeration, review, explanation, and replay auditing, but there is no tool to fetch or inspect a specific scenario/episode by identifier, nor to list available episodes or query belief state directly. These are notable gaps that could force agents into dead ends after listing.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues