Developer Tools
realitygraph.dev
Provides tools to estimate verification debt, lint AI coding task specs, and manage task contracts for verifiable software development.
ENDPOINT 1
https://realitygraph.dev/api/mcp
MCP server metadata
- Name
- reality-graph-verification-tools
- Version
- 2.0.0
Known tools 10
check_verification_debtEstimate a software team's verification debt from team parameters.
Inferred read-onlylint_task_specCheck whether a free-text work order for an AI coding agent is verifiable BEFORE handing it over.
Inferred read-onlyget_task_contract_templateReturns Reality Graph's free fill-in template (v0) for a verifiable task contract: goal, non-goals, boundaries (may change / must not change / forbidden), 3-7 yes/no acceptance criteria, validation plan, expected evidence, assumptions, open questions — with a filled example and fill-in guidance.
Inferred read-onlyvalidate_task_contractDeterministically validates a FILLED task contract (the JSON structure from get_task_contract_template): completeness of goal/non-goals/boundaries, decidability of each acceptance criterion (vague words, missing measurable markers), automated checks in the validation plan, expected evidence, and leftover placeholders.
Inferred read-onlyget_verification_report_templateReturns the free fill-in template (v0) for a verification report — the artifact you write right after an AI-assisted run: task recap, files changed AND files confirmed untouched, validation results per acceptance criterion (not authored by the generating model), what was skipped, limitations, and the explicit decision.
Potential side effectssearchFull-text search over the Reality Graph knowledge base on AI coding verification: 40+ glossary definitions, 700+ FAQ answers, sourced statistics, and article summaries on verification debt, AI code review, spec-vs-implementation checking, EU compliance (EU AI Act, GDPR, NIS2), and AI coding governance — in English and German.
Inferred read-onlyfetchFetch a document from the Reality Graph knowledge base by id (as returned by search, e.
Inferred read-onlyplan_change_verificationTurn explicit change characteristics into a risk tier, required automated checks, manual scenarios, evidence, release blockers, role handoff, and canonical Reality Graph guidance.
Inferred read-onlycheck_release_readinessReturn GO, CONDITIONAL, or NO_GO from supplied acceptance-criterion results, check evidence, rollback, monitoring, limitations, and independent review.
Inferred read-onlycalculate_verification_capacityCalculate weekly review demand, utilization, capacity gap, supported change throughput, and changes lacking evidence from measured team inputs.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.reality-graph-verification-tools]
url = "https://realitygraph.dev/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"reality-graph-verification-tools": {
"type": "http",
"url": "https://realitygraph.dev/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: reality-graph-verification-tools
Remote MCP URL: https://realitygraph.dev/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"reality-graph-verification-tools": {
"url": "https://realitygraph.dev/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"reality-graph-verification-tools": {
"type": "http",
"url": "https://realitygraph.dev/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "reality-graph-verification-tools",
"transport": "streamable-http",
"url": "https://realitygraph.dev/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for realitygraph.dev was fetched 2026-09-06T21:52:40.907Z.
realitygraph.dev is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.