About Concordance
Concordance is a deterministic verification engine for people and agents that need to check claims and retain verifiable evidence. It returns a verdict, reasoning trail, and content-addressed seal, alongside tools for retrieval and scripture study.
Key features
- 01Deterministic claim verification
- 02Verdicts with reasoning trails
- 03Content-addressed seals and append-only ledger
- 04Search, lookup, and definitions
- 05Parable matching and next-step guidance
- 06Scripture reading and word study
Use cases
- 01Check mathematical or domain claims
- 02Keep re-checkable evidence for verdicts
- 03Find material and inspect its sources
- 04Study scripture and cross-references
MCP support
Concordance provides an MCP server with tools for verification, retrieval, situation-based guidance, personal records, and scripture study. Responses are found or verified and include citations and seals.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://narrowhighway.com/mcpclaude mcp add --transport http concordance-2 https://narrowhighway.com/mcp{"mcpServers":{"concordance-2":{"type":"http","url":"https://narrowhighway.com/mcp"}}}Open in Cursor{"servers":{"concordance-2":{"type":"http","url":"https://narrowhighway.com/mcp"}}}Open in VS Code{"mcpServers":{"concordance-2":{"type":"http","url":"https://narrowhighway.com/mcp"}}}{"mcpServers":{"concordance-2":{"serverUrl":"https://narrowhighway.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
93| Parameter | Type | Required | Description |
|---|---|---|---|
| mode | enum | No | MATH form: equality | inequality | derivative | integral | limit | solvederivative | equality | inequality | integral | limit | solve |
| params | object | No | MATH form: e.g. {expr_a, expr_b, variables} for equality |
| steps | array | No | DOMAIN form: [{id, domain, spec}] — spec is the domain's packet |
| seal | boolean | No | mint a re-checkable seal (default true) |
Details
From the project READMEConcordance 2.0
A deterministic verification engine. It checks what is true and hands you a receipt you can re-verify — a verdict, the worked reasoning, and a permanent content-addressed seal. It eliminates what is not the answer so that what survives stands on its own.
Rebuilt like a watch (the watchmaker's discipline): one bounded, counted movement; serviceable by any competent hand; machine-honest — the accuracy is the finish. See
docs/V2_DEFINITION.md. New here? Start withdocs/ARCHITECTURE.md— the newcomer's map (every count dated and derived from the code).
The floor — seven primitives
Every answer is a (verdict, trail, seal) — three things, each independently checkable.
- Claim — a structured assertion
{domain, spec}(or text the router resolves) - Verifier — a pure deterministic function
spec → verdict + worked trail(no I/O, no LLM) - Verdict —
PASS | REJECT | QUARANTINE+ the worked math (the elimination trail) - Seal — content-addressed (SHA-256) record of
{claim, verdict, trail} - Ledger — append-only hash chain of seals
- Ranker — IDF/full-text retrieval over the keeping
- Surface — the face over the shared foundation (
secularreach /witness)
The measure: reproducibility, zero false-positives on the published benchmark (docs/BENCHMARK.md), re-checkability.
One foundation, two surfaces
The foundation is the Bible (FOUNDATION.md) — Christ at the center. From it the
engine reaches the world two ways: a secular .com (the reach) and an explicit-witness .org.
One engine, one foundation, selected by config — never a fork.
from concordance import EngineConfig
EngineConfig("secular").identity # the reach — no religious wording
EngineConfig("witness").identity # the witness — the foundation named
Run it
PYTHONPATH=src python -m concordance serve # the .com reach (secular) — API + site, same-origin
PYTHONPATH=src python -m concordance serve --surface witness # the .org witness face
Then open http://127.0.0.1:8000/ — bring a claim, get a receipt. (Data — the keeping, the WEB
Bible, Strong's — is generated by tools/migrate_*.py and gitignored; the engine runs without it,
just with less to retrieve.)
The surfaces — reached by asking, not by menus
- The Console (
/) — speak or type anything; the keeping answers, shown as a calm trail (door → verifier → seal → source), read as a page or heard aloud in the operator's own cloned voice. Crisis-first, store-nothing. - The parable (
/parable.html, and the WALK door) — bring a situation; receive the one of Christ's parables whose shape fits it — the story verbatim, with his own explanation where he gave one, and one next step. Found and cited, never generated; honest silence where no single parable fits. - The Reading Room (
/books.html) — a free library: read our books in full, or open your own.epub, which is read entirely in your browser and never uploaded (store-nothing).
For agents — the MCP (the church for agents)
The engine is also an MCP server (python -m concordance mcp). Five doors, every answer
found/verified/cited/sealed, never generated:
- CHECK —
verify·audit·seal_fetch·find_verifier: a claim in; the verdict, the worked trail, the seal. - FIND —
search·card_get·lookup·define: one map, one lookup, the source itself. - WALK —
ask·discern·parable·coach_next: a situation in, one next step out — the path, the fitting parable, the figures' words. - KEEP —
identity_create·study_create·decks: a sovereign key born on your device; your deck, your receipts. - WORD —
read_passage·word_study·cross_references: Scripture at depth.
Status
The 2.0 engine is built end to end and live (narrowhighway.com/.org/.tv) — floor 7/7, the derivation moat (0 false-positives), the tamper-evident ledger + precedent overlay, 93 verifier modules across 77 routable domains, the witness overlay (theology / witness / scripture / canon), the shared corpus
- ranker (880k+ cards), scripture ref-resolution + original-language word study, the axes grid, the
Console + the parable register + the Reading Room, an MCP server (100+ tools), a sovereign HTTP API,
and the site. 400 test files; the deploy gate (benchmarks, live assay, front door, recall) runs on
every push with zero false positives and reverts on any regression. The domain router is model-free
and measured (orthogonalized basis; routing cross-talk and invariance tracked by
tools/dispatch_probe.pyandtools/hodge_probe.py). A gated collective-intelligence layer (stigmergy, quorum, flock, eldership, physiology, inhibition) and an alignment gate (the keeping tiered by agreement — occult explicit-only, other religions/philosophy referenceable) run over it; seedocs/WORLD.md. Sovereign, stdlib-first; heavy deps (sympy/scipy/numpy) are optional, lazy-loaded.
1.0 is frozen (v1.0-frozen in the Lighthouse repo) — the shape that taught us the floor.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.