RealityFirst MCP
Related Servers
Alternatives to RealityFirst MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceFailLoud is a deterministic verification harness for LLM agent outputs — it catches silent failures agents ship as 'done.' Six checks: FL001 placeholder_shipped, FL002 unbacked_claim, FL003 stale_state, FL004 count_mismatch, FL005 missing_components, FL006 unsupported_answer. No LLM in the verdict path. CLI, library, GitHub Action, MCP server (11 tools). MIT.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to verify claims with evidence-based truth scores and confidence levels by running a deterministic pipeline of evidence lanes and adversarial checks.26MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to verify claims against evidence through MCP tools, returning approved, rejected, or needs_review verdicts with replayable receipts.MIT
- AlicenseNot gradedqualityDmaintenancePrevents autonomous agents from fabricating tool results by verifying HMAC-signed receipts against epistemic claim types, forcing re-grounding or escalation before actions commit.MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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.25 PyPIMIT
- FlicenseAqualityBmaintenanceEnables agents to verify claims against a real falsification ledger, querying pre-registered refutation thresholds, recorded verdicts, and verifier drift metrics instead of guessing.5-
TDQS
Scored across 8 tools
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.
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.
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.
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.