Concordance MCP server
{
"mcpServers": {
"narrowhighway-concordance": {
"type": "http",
"url": "https://narrowhighway.com/mcp"
}
}
}{
"mcpServers": {
"narrowhighway-concordance": {
"type": "http",
"url": "https://narrowhighway.com/mcp"
}
}
}{
"mcpServers": {
"narrowhighway-concordance": {
"type": "http",
"url": "https://narrowhighway.com/mcp"
}
}
}{
"servers": {
"narrowhighway-concordance": {
"type": "http",
"url": "https://narrowhighway.com/mcp"
}
}
}{
"mcpServers": {
"narrowhighway-concordance": {
"type": "http",
"url": "https://narrowhighway.com/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 2.0.0
What it does
Concordance is a deterministic verification engine that checks claims against ~60 domains and returns a verdict with a re-verifiable receipt (verdict, reasoning trail, and content-addressed seal). It requires no model in the loop and is designed for reproducible, auditable claim verification.
- Submit a structured claim and receive a deterministic PASS/REJECT/QUARANTINE verdict with the worked reasoning trail and a tamper-evident seal.
- Re-verify any past claim by checking its seal and reasoning against the content-addressed ledger without re-running the engine.
- Retrieve and rank previous verdicts using full-text search over the keeping (stored results) to find applicable precedents.
Tools this server exposes
| Tool | Does |
|---|---|
| claim_submission | Accept a structured claim with domain and spec fields, or resolve unstructured text to a claim. |
| deterministic_verifier | Run a pure function verifier that produces a verdict (PASS/REJECT/QUARANTINE) plus the worked elimination trail. |
| seal_generation | Generate a SHA-256 content-addressed record of the claim, verdict, and trail for later re-verification. |
| ledger_append | Maintain an append-only hash chain of all seals for audit and precedent tracking. |
| verdict_ranker | Retrieve and rank stored verdicts by IDF and full-text search over the keeping. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.