Skip to main content
Glama
zone5101

RealityFirst MCP

by zone5101
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to RealityFirst MCP

No user-submitted related servers found.

    Related Servers

    • ReceiptGuard

      GHGuide
      A
      license
      Not graded
      quality
      D
      maintenance
      Prevents autonomous agents from fabricating tool results by verifying HMAC-signed receipts against epistemic claim types, forcing re-grounding or escalation before actions commit.
      MIT

    • mcp-verify-claim

      sudo-ai-git
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to classify every claim into evidence tiers (FACT/INFERENCE/SPECULATION/UNVERIFIED) with attached evidence, forcing deterministic, evidence-gated reporting without LLM or network calls.
      18 PyPI
      MIT
    • catqualia-ledger-mcp by OpeningBlackBox

      catqualia-ledger-mcpofficial

      OpeningBlackBox
      F
      license
      A
      quality
      C
      maintenance
      Enables agents to verify claims against a real falsification ledger, querying pre-registered refutation thresholds, recorded verdicts, and verifier drift metrics instead of guessing.
      5
      19 PyPI
      -

    • Proofrail

      armsteadj1
      A
      license
      A
      quality
      C
      maintenance
      Enables coding agents to identify the least-proven claim in code after edits and receive a focused repair packet with exact source anchors, missing proof, reproducer, and a done condition, supporting iterative verify/fix loops.
      3
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (classify vs resolve vs compact). However, validate_evidence, check_completion_evidence, and check_replay_safety all perform gate-style checks on evidence, which could cause confusion without careful reading of descriptions.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (validate_evidence, resolve_precedence, check_replay_safety, etc.). There are no mixed conventions or vague verbs.

    Tool Count5/5

    With 8 tools, the set is well-scoped for a verification/evidence-gate server. Each tool addresses a distinct step in the workflow, and there is no excessive proliferation.

    Completeness3/5

    The surface covers validation, classification, conflict resolution, planning, and loss recording, but record_loss explicitly does not persist entries, leaving no way to actually store or retrieve loss data. There is also no tool to execute verification or persist evidence, creating dead ends for some workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources