dk.humanified/values-firewall
REMOTE · VF.HUMANIFIED.DK · SCANNED SEP 27
EU AI Act Art-14 runtime oversight: allow / flag / gate-to-human on an agent action, with 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 connect, but we couldn't read the whole tool list to see what that exposes. 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 502. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the dk.humanified/values-firewall MCP server?
dk.humanified/values-firewall is a hosted endpoint at https://vf.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 · vf.humanified.dk
claude mcp add --transport http dk-humanified-values-firewall 'https://vf.humanified.dk/mcp'
{
"mcpServers": {
"dk-humanified-values-firewall": {
"url": "https://vf.humanified.dk/mcp"
}
}
} {
"servers": {
"dk-humanified-values-firewall": {
"type": "http",
"url": "https://vf.humanified.dk/mcp"
}
}
} [mcp_servers.dk-humanified-values-firewall] url = "https://vf.humanified.dk/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dk-humanified-values-firewall": {
"type": "remote",
"url": "https://vf.humanified.dk/mcp",
"enabled": true
}
}
} openclaw mcp add dk-humanified-values-firewall --url 'https://vf.humanified.dk/mcp' --transport streamable-http
mcp_servers:
dk-humanified-values-firewall:
url: "https://vf.humanified.dk/mcp" {
"McpServers": {
"dk-humanified-values-firewall": {
"Transport": "http",
"Url": "https://vf.humanified.dk/mcp"
}
}
} assistant mcp add dk-humanified-values-firewall -t streamable-http -u 'https://vf.humanified.dk/mcp'
{
"mcpServers": {
"dk-humanified-values-firewall": {
"type": "http",
"url": "https://vf.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
- 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 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −3
- Stability: pass → 0.83 functional
- 3 Sept 26 +1
- Stability: 0.97 → pass security
- 1 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 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
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://vf.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=vf.humanified.dk | CN=YE2,O=Let's Encrypt,C=US | 4 Aug 2026 | 2 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5ca8f31643e4bfb45a6f1fdabfb6520eb78 |
| SANs: vf.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 vf.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 | 502 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vf.humanified.dk/mcp | HTTP error | 502 | |
| http (plaintext) | http://vf.humanified.dk/mcp | HTTPS enforced | 308 | https://vf.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_action ~527
Kerne-gaten (to-lags evaluering): Lag A (deterministisk hard-rule/outward-match, ingen LLM) + Lag B (Sonnet vurderer mod charterets NL-principper via LiteLLM :4000, citerer principle_id + reasoning — INGEN egen alvorligheds-dom) → most-restrictive-wins aggregeret, auditerbar receipt: {action, deterministic_flags[], values_assessment[], values_assessment_unavailable, unrecognized_principle_citations, principles_evaluated, recommendation, requires_human, charter_name, scope_note}. `recommendation` ∈ {allow, flag, gate_to_human} — ALDRIG approved/denied/true/false. ADVISORY: anbefaler, blokerer/eksekverer/autoriserer ALDRIG (never-decide-for-you). FAIL-SAFE: Lag B utilgængelig -> Lag A kører stadig, values_assessment_unavailable=true, recommendation løftet til MINDST 'flag' (aldrig stille 'allow'). Read-only — skriver INTET, ingen side-effekter. PUBLIC_DEMO-mode: vurderet mod det OFFENTLIGE Art-14-demo-charter (ikke din org — se scope_note). Rate-limitet (default 5/min + 30/time, ÉN global demo-bucket). Over grænsen returneres `{error:"rate_limited", retry_after_s, scope_note}` — ALDRIG et recommendation-formet svar. Bogholderi-fejl i rate-limiteren -> deny (fail-safe). RED-TEAM-FIX (minimal-indgreb): tomt/whitespace-only `action` valideres FØR rate-limiteren forbruger en kvote-token — en ugyldig-input-loop kan ellers stille dræne demoens kvote uden at nogensinde levere en receipt (rå ValueError fra firewall.check_action's fail-loud-guard ville ellers både forbruge kvote OG propagere ubehandlet til transport-laget, hvilket bryder "check_action leverer ALTID en receipt/struktureret fejl"-disciplinen). Uden for PUBLIC_DEMO uændret: fw.check_action's egen ValueError-fail-loud gælder stadig (bindende, testet i test_values_firewall.py).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| context | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
check_action_deterministic ~153
KUN Lag A — ingen LLM-kald overhovedet (billig, ren mekanisk, spejler consistency-gates check_triple). Samme receipt-form som check_action, men values_assessment er altid tom, values_assessment_unavailable altid false, og scope_note siger eksplicit 'values_layer_consulted:false'. Read-only. PUBLIC_DEMO-mode: ÅBEN, GRATIS — ALDRIG rate-begrænset (spec §2, ingen LLM-kost). Vurderet mod det offentlige Art-14-demo-charter; scope_note får demo-disclosuren appended.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| context | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_charter ~172
Transparens: hvilke regler/principper håndhæver DENNE firewall lige nu — navn/version/ hard_rules/outward_patterns/principles. Values-locked (arvet): firewall'en håndhæver KUN dette deklarerede charter, opfinder aldrig regler/principper udenfor det. PUBLIC_DEMO-mode: ÅBEN, GRATIS — ALDRIG rate-begrænset. Viser det OFFENTLIGE Art-14-demo- charter (6 principper, 4 hard_rules, 14 outward_patterns) — ikke noget kunde-/fleet-/ TIER-1-charter. Får et `scope_note`-felt med demo-disclosuren tilføjet (fraværende i default-mode — additiv, ingen bestående felter ændres).
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
What is the dk.humanified/values-firewall MCP server?
dk.humanified/values-firewall is an MCP server listed in the public MCP registry as dk.humanified/values-firewall. EU AI Act Art-14 runtime oversight: allow / flag / gate-to-human on an agent action, with receipt. This page covers its hosted endpoint (https://vf.humanified.dk/mcp).
Is the dk.humanified/values-firewall MCP server safe to use?
dk.humanified/values-firewall scores 23 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/values-firewall MCP server expose?
dk.humanified/values-firewall exposes 3 tools: check_action, check_action_deterministic, list_charter. Their descriptions and schemas cost roughly 852 tokens of context every time the server is loaded.
Does the dk.humanified/values-firewall MCP server require authentication?
No. We connected to dk.humanified/values-firewall without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the dk.humanified/values-firewall MCP server still maintained?
dk.humanified/values-firewall 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.