dk.humanified/consistency-gate
REMOTE · MCP.HUMANIFIED.DK · SCANNED SEP 27
Check claims against a fact-store: consistent, contradicts, or unverifiable — with a receipt.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 600 tokens (~200/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the dk.humanified/consistency-gate MCP server?
dk.humanified/consistency-gate is a hosted endpoint at https://mcp.humanified.dk/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.humanified.dk
claude mcp add --transport http dk-humanified-consistency-gate 'https://mcp.humanified.dk/mcp'
{
"mcpServers": {
"dk-humanified-consistency-gate": {
"url": "https://mcp.humanified.dk/mcp"
}
}
} {
"servers": {
"dk-humanified-consistency-gate": {
"type": "http",
"url": "https://mcp.humanified.dk/mcp"
}
}
} [mcp_servers.dk-humanified-consistency-gate] url = "https://mcp.humanified.dk/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dk-humanified-consistency-gate": {
"type": "remote",
"url": "https://mcp.humanified.dk/mcp",
"enabled": true
}
}
} openclaw mcp add dk-humanified-consistency-gate --url 'https://mcp.humanified.dk/mcp' --transport streamable-http
mcp_servers:
dk-humanified-consistency-gate:
url: "https://mcp.humanified.dk/mcp" {
"McpServers": {
"dk-humanified-consistency-gate": {
"Transport": "http",
"Url": "https://mcp.humanified.dk/mcp"
}
}
} assistant mcp add dk-humanified-consistency-gate -t streamable-http -u 'https://mcp.humanified.dk/mcp'
{
"mcpServers": {
"dk-humanified-consistency-gate": {
"type": "http",
"url": "https://mcp.humanified.dk/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Stability: 0.97 → pass security
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +49
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.93 ▲ functional
- 21 Sept 26 −48
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.87 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 20 Sept 26 −2
- Stability: pass → 0.87 functional
- 3 Sept 26 0
- Stability: 0.97 → pass security
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://mcp.humanified.dk/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.humanified.dk | CN=YE2,O=Let's Encrypt,C=US | 4 Aug 2026 | 2 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 6c4146a7da35375bfa9ffdd919117feb598 |
| SANs: mcp.humanified.dk | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.humanified.dk. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dk. | present | 16874 | 13 | Verified |
| humanified.dk. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.humanified.dk/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.humanified.dk/mcp | HTTPS enforced | 308 | https://mcp.humanified.dk/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_claim ~311
NL-gate (kernen): udtræk SPO-triple(r) fra en naturlig-sprogs-PÅSTAND (Sonnet via LiteLLM, R1) og tjek hver mod det grundede SPO-fakta-lager (i PUBLIC_DEMO-mode: det OFFENTLIGE demo-fakta-lager, IKKE dine data — se scope_note). Returnerer en auditerbar consistency-receipt: {claim, extracted_triples[], conflicts[], verdict, checked_against_n_facts, scope_note}. `verdict` ∈ {consistent, contradicts, unverifiable} — ALDRIG true/false. ADVISORY: flager konsistens, blokerer/beslutter ALDRIG for dig (never-write-for-you). Persisterer ALDRIG selve påstanden (check ≠ gem — kun add_fact skriver til lageret, og add_fact er FRAVÆRENDE i PUBLIC_DEMO-mode). PUBLIC_DEMO-mode: rate-limitet (default 5/min + 30/time, ÉN global demo-bucket, §2/§8 BLOCKER 3). Over grænsen returneres `{error:"rate_limited", retry_after_s, scope_note}` — ALDRIG et consistent-formet svar. Bogholderi-fejl i rate-limiteren -> deny (fail-safe).
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | – |
| focus | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
check_triple ~145
Rå SPO-gate, deterministisk (ingen LLM — billig, testbar kerne, ÅBEN+GRATIS i PUBLIC_DEMO-mode, ingen rate-grænse §2). Konflikt = samme normaliseret subjekt+prædikat, andet normaliseret objekt. Returnerer ALLE konflikter (ikke kun første). `verdict` ∈ {consistent, contradicts} — ALDRIG true/false. Read-only mod lageret (i PUBLIC_DEMO-mode: det offentlige demo-fakta-lager).
| Name | Type | Req | Description |
|---|---|---|---|
| object | string | yes | – |
| predicate | string | yes | – |
| subject | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_facts ~144
Alle fakta hvor `entity` er subjekt ELLER objekt (transparens/audit). `entity` normaliseres FØR match — case/whitespace-varianter matcher samme række. Returtypen er ALTID en liste (§8-adjudikering: ingen dict-wrap/scope_note-injektion her, det ville være en regression mod default-modens kontrakt). PUBLIC_DEMO-mode: listen viser udelukkende rækker fra det OFFENTLIGE demo-fakta-lager (demo-facts.json) — ikke fleet/TIER-1/cortex-data (§3 PUBLIC-SAFE).
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
What is the dk.humanified/consistency-gate MCP server?
dk.humanified/consistency-gate is an MCP server listed in the public MCP registry as dk.humanified/consistency-gate. Check claims against a fact-store: consistent, contradicts, or unverifiable, with a receipt. This page covers its hosted endpoint (https://mcp.humanified.dk/mcp).
Is the dk.humanified/consistency-gate MCP server safe to use?
dk.humanified/consistency-gate scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the dk.humanified/consistency-gate MCP server expose?
dk.humanified/consistency-gate exposes 3 tools: check_claim, check_triple, list_facts. Their descriptions and schemas cost roughly 600 tokens of context every time the server is loaded.
Does the dk.humanified/consistency-gate MCP server require authentication?
No. We connected to dk.humanified/consistency-gate without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the dk.humanified/consistency-gate MCP server still maintained?
dk.humanified/consistency-gate is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.