Skip to content
plugmcp
DirectorySkillsCategoriesBlog
EN/中文
Sign inSign up
Home/Servers/Concordance

Concordance

by com.narrowhighway

Deterministic claim verification with receipts across ~60 domains. No model in the loop.

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Server URL
https://narrowhighway.com/mcp
Provider
Add in Claude

Claude opens with the name and URL filled in. You still confirm it there.

Claude Code
claude mcp add --transport http com.narrowhighway-concordance https://narrowhighway.com/mcp

Run in a terminal.

Claude Desktop
{
  "mcpServers": {
    "com.narrowhighway-concordance": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://narrowhighway.com/mcp"
      ]
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Related MCP

View more
  • Firecrawl🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
  • N
    NotionToken-auth Notion MCP: pages, databases, blocks, comments, files. Runs headless in CI and agents.
  • Context7Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors

Related skills

View all
  • reaReverse engineer anything with agents, from app behavior down to native binaries.
  • rea-changelog-updatePrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.
  • rea-tool-designDesign or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.

Deterministic claim verification with receipts across ~60 domains. No model in the loop.

Concordance 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 with docs/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.

  1. Claim — a structured assertion {domain, spec} (or text the router resolves)
  2. Verifier — a pure deterministic function spec → verdict + worked trail (no I/O, no LLM)
  3. Verdict — PASS | REJECT | QUARANTINE + the worked math (the elimination trail)
  4. Seal — content-addressed (SHA-256) record of {claim, verdict, trail}
  5. Ledger — append-only hash chain of seals
  6. Ranker — IDF/full-text retrieval over the keeping
  7. Surface — the face over the shared foundation (secular reach / 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.py and tools/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; see docs/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.

How do I install Concordance?
Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does Concordance need an API key?
No required environment variable is listed on this record.
What transport does Concordance use?
Concordance is reached over HTTP.
When was Concordance last checked?
Last checked 2026-10-16. Deterministic claim verification with receipts across ~60 domains. No model in the loop.

No tool list yet. Remote servers get one after the first health check.

plugmcp

Plug any tool into any agent. MCP servers for people who do not write servers. Gateway for volume, n8n for apps.

  • github.com/TODO
  • x.com/TODO
  • linkedin.com/company/TODO

PlugMCP, 2026

Product
  • Browse
  • Install
  • Host your own
  • Voice mode
  • Browser
Directory
  • All MCP servers
  • Agent skills
  • Categories
  • New
  • Voice
  • Submit a server
Developers
  • Docs
  • Blog
  • What is MCP
  • What is WebMCP
  • Status
Company
  • About
  • Contact
  • Terms
  • Privacy
  • DPA