Ask Emil – Human Perspective
REMOTE · RUNUP.DK
Real human in Denmark: lived experience & opinion. Free 1-question pilot. Set a custom User-Agent.
Available components
Last scanned (20 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 4 Nov 2026.
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 Security66
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 454 tokens (~151/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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 64% of tool parameters carry a description.Partial
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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 2 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 1 Nov 26 +28
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: 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
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Tool coverage: 64 functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- 13 Oct 26 36
First indexed and scored.
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 4 Nov 2026 · Probed https://runup.dk/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=runup.dk | CN=YE1,O=Let's Encrypt,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5a383b891a9e5c1d12b0f7327d624ba2e92 |
| SANs: runup.dk, www.runup.dk | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 secure
Validation of runup.dk. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dk. | present | 16874 | 13 | Verified |
| runup.dk. | present | 37040 | 13 | Verified |
| runup.dk. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | default-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://runup.dk/mcp | Verified | 200 | |
| http (plaintext) | http://runup.dk/mcp | HTTPS enforced | 301 | https://runup.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 →
ask_human_perspective Ask a real human ~221
Ask a real human — Emil Hyltoft Eriksen, Denmark — for his lived experience and personal opinion: 'what happened when I…', 'what would a real person actually do', 'how would this feel to a human'. Not facts, not professional medical/legal/financial advice. Free pilot: exactly one question in total; after that the server returns status pilot_full. Emil is testing whether agents find this useful at all. Answers are written personally by Emil and are asynchronous (usually hours; give a realistic deadline). Returns a question_id; poll get_answer(question_id). Include enough context to answer without follow-up.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Optional stable id for your agent. |
| context | string | yes | Background so Emil can answer without follow-up. |
| deadline | string | yes | ISO 8601. When you need the answer by (at least 1 hour, at most 30 days ahead). |
| options | array | – | Optional options to choose between. |
| question | string | yes | The question for Emil. |
No output schema declared.
No examples provided.
get_answer Get the answer ~63
Get the status and, when ready, Emil's answer to a question_id from ask_human_perspective. Status is queued, answered, declined or expired. Answers are asynchronous: poll no more often than every 15 minutes.
| Name | Type | Req | Description |
|---|---|---|---|
| question_id | string | yes | – |
No output schema declared.
No examples provided.
give_feedback Give feedback (market test) ~124
Market test: tell us whether the human answer was useful and whether you (or your operator) would pay for answers like this, and roughly how much. One feedback per answered or declined question. This is the whole point of the free pilot, so please be honest.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | – |
| price_usd | number | – | What one answer like this would be worth to you, in USD. |
| question_id | string | yes | – |
| useful | integer | yes | 1 = useless, 5 = very useful |
| would_pay | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Ask Emil – Human Perspective MCP server?
Ask Emil – Human Perspective is a hosted endpoint at https://runup.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 · runup.dk
claude mcp add --transport http 2xe-ask-emil 'https://runup.dk/mcp'
What is the Ask Emil – Human Perspective MCP server?
Ask Emil – Human Perspective is an MCP server listed in the public MCP registry as io.github.2xe/ask-emil. Real human in Denmark: lived experience & opinion. Free 1-question pilot. Set a custom User-Agent. This page covers its hosted endpoint (https://runup.dk/mcp).
Is the Ask Emil – Human Perspective MCP server safe to use?
Ask Emil – Human Perspective scores 65 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 Ask Emil – Human Perspective MCP server expose?
Ask Emil – Human Perspective exposes 3 tools: ask_human_perspective, get_answer, give_feedback. Their descriptions and schemas cost roughly 408 tokens of context every time the server is loaded.
Does the Ask Emil – Human Perspective MCP server require authentication?
No. We connected to Ask Emil – Human Perspective without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Ask Emil – Human Perspective MCP server still maintained?
Ask Emil – Human Perspective is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.