mcp-registry/com.narrowhighway/concordance · v2.0.0a0
As of 2026-10-20 07:43 UTC, the Narrowhighway Concordance MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 30 outages in 90 days, with a median recovery of 6 minutes.
Deterministic claim verification with receipts across ~60 domains. No model in the loop.
Claude Code
claude mcp add --transport http narrowhighway-concordance-mcp-server https://narrowhighway.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"narrowhighway-concordance-mcp-server": {
"type": "http",
"url": "https://narrowhighway.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
102 of 102 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
102 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
195 parameter(s) across 83 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
8 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
Loading this server's tool list costs an agent ~16,241 tokens before any work — more than 90% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
In the last 30 days: 1 tool(s) removed and 6 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 83 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.narrowhighway%2Fconcordance/fixes
{
"name": "calendar_create",
"description": "[KEEP · internal] Create ONE event in a human's calendar — the pilot on-behalf write, and the only one. Requires a LIVE consent grant: the human signed a scoped, expiring calendar_write grant for YOUR key fingerprint on their own device (GET /consent/signable → sign locally → POST /consent). Without it this refuses and teaches the way in. The event lands only in the calendar THEY configured (their .ics file or CalDAV); nothing is stored here, and the receipt names the grant that authorized it. D",
"inputSchema": {
"type": "object",
"required": [
"grantor_pubkey",
"agent_fp",
"summary",
"start_iso"
],
"properties": {
"end_iso": {
"type": "string",
"maxLength": 4000
},
"summary": {
"type": "string",
"maxLength": 4000
},
"agent_fp": {
"type": "string",
"maxLength": 4000
},
"start_iso": {
"type": "string",
"maxLength": 4000
},
"description": {
"type": "string",
"maxLength": 4000
},
"grantor_pubkey": {
"type": "string",
"maxLength": 4000
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "candidate_get",
"description": "[CHECK · internal] Fetch a sealed candidate record (a narrowing receipt or a commitment anchor) by its content hash — the whole preserved path, losers included, re-checkable offline with tools/verify_seal.py. The seal proves process integrity, never truth.",
"inputSchema": {
"type": "object",
"required": [
"hash"
],
"properties": {
"hash": {
"type": "string",
"pattern": "^[0-9a-f]{64}$"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "card_get",
"description": "[FIND · door] Fetch one card (the full record) from the keeping by id.",
"inputSchema": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"maxLength": 4000
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.narrowhighway/concordance"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.narrowhighway/concordance"}) over MCP.
candidate_narrow ~530 tokensshelf_signable ~465 tokenscandidate_commit ~455 tokenskernel_gate ~455 tokensverify ~420 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.narrowhighway%2Fconcordance?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.narrowhighway%2Fconcordance?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.narrowhighway%2Fconcordance.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.narrowhighway%2Fconcordance.svg :target: https://glimind.com/server/mcp-registry%2Fcom.narrowhighway%2Fconcordance?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:d2e630c757ca2f82…, first seen 2026-10-17, included at leaf 15206 of 31,597. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable security servers · most reliable other servers · most reliable calendar servers · most reliable retrieval servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-20 07:43 UTC, the Narrowhighway Concordance MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 30 outages in 90 days, with a median recovery of 6 minutes.
Narrowhighway Concordance MCP server advertises 102 tools, including ask, attest_record, audit, backmatter, badges_issue.
Point your MCP client at this streamable-http endpoint: https://narrowhighway.com/mcp
Glimind scanned all 102 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.