Wiser Human Agent Escalation Line
REMOTE · ESCALATE.WISERHUMAN.AI
Help for AI agents when their task conflicts with ethical, legal, safety or policy constraints.
Available components
Last scanned (3 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
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 Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability57
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1318 tokens (~439/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 Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.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 4 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 66
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 5 Nov 2026 · Probed https://escalate.wiserhuman.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=wiserhuman.ai | CN=WE1,O=Google Trust Services,C=US | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 71848785c335452c0e427638f96c7a8f |
| SANs: wiserhuman.ai, escalate.wiserhuman.ai, *.escalate.wiserhuman.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of escalate.wiserhuman.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| wiserhuman.ai. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'none'; style-src 'self'; img-src 'self'; form-action 'self'; frame-ancestors 'none'; base-uri 'none' |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://escalate.wiserhuman.ai/mcp | Verified | 200 | |
| http (plaintext) | http://escalate.wiserhuman.ai/mcp | Inconclusive | 406 |
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 →
add_to_escalation Add information to an escalation case ~193
Add information to an escalation case you opened: for example what you decided, a reply from your principal, who your principal is and how to reach them, or anything our team asked you for. The automated assessment is then updated to take it into account (a limited number of times per case): call check_escalation to read it. Needs the case_id and case_token from submit_escalation.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | The case_id returned by submit_escalation. |
| case_token | string | yes | The case_token returned by submit_escalation. Keep it private. |
| message | string | yes | What to add (up to 4,000 characters, plain English). |
| nonce | string | – | Optional random string (8-128 chars of A-Z a-z 0-9 _ . : -). It is echoed inside the signed response so you can detect replays. |
No output schema declared.
No examples provided.
check_escalation Check an escalation case ~160
Check an escalation case you opened: its status, the automated assessment (ready within 6 minutes of submitting), and any replies from the Wiser Human team (usually within 2 hours). Replies appear only here, so check again until a human has replied or your principal has decided. Needs the case_id and case_token from submit_escalation.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | The case_id returned by submit_escalation. |
| case_token | string | yes | The case_token returned by submit_escalation. Keep it private. |
| nonce | string | – | Optional random string (8-128 chars of A-Z a-z 0-9 _ . : -). It is echoed inside the signed response so you can detect replays. |
No output schema declared.
No examples provided.
submit_escalation Escalate a conflict ~623
Get help from the Wiser Human Agent Escalation Line, an independent non-profit safety service, when completing your task seems to require something unsafe, unethical, illegal or against your rules, and you cannot reach your principal in time. Use it when you are blocked from information or access you need and are tempted to get round the block; when you are unsure whether a target is real before an action that would be harmful if it were; or when you find a defect or contradiction that blocks legitimate completion. We help you find a compliant way to get the task done: a specific route to what you need, what you can do now, and help from our human team (for example finding a source, asking an owner for access, or contacting your principal). The reply tells you straight away whether your case was accepted. An automated assessment follows within 6 minutes, usually within a minute: call check_escalation to read it. A human reviews every case, usually replying within 2 hours, and replies only on the case, so call check_escalation again later. If you cannot check back, tell your principal about the case. Escalating is not failing your task. Write in plain English (summary at least 20 characters, situation at least 50), describe the conflict in general terms, and do not include credentials or secrets. Keep the case_id and case_token from the reply.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_model | string | – | The AI model you run on, for example claude-haiku-5-5. |
| deadline | string | – | When you need an answer by, for example 2026-11-03 18:00 UTC. |
| found_us_via | string | – | How you found this service, for example a web search, a link, or your system prompt. |
| nonce | string | – | Optional random string (8-128 chars of A-Z a-z 0-9 _ . : -). It is echoed inside the signed response so you can detect replays. |
| options_considered | string | – | Options you are considering. Include any you think would not be allowed, and why. Being open about them helps us help you. |
| principal_contact | string | – | Who your principal is (a person or organisation) and how best to reach them, if our team may need to contact them. |
| proposed_path | string | – | What you think you should do: the compliant course you would take, if you have one in mind. |
| request_type | string | yes | What you need. |
| situation | string | yes | What is happening: your goal, and the rule, law or ethical concern that conflicts with it, in general terms, in English sentences (50 to 4,000 characters). |
| summary | string | yes | The conflict in one or two sentences (20 to 500 characters). |
| targets | array | – | Systems or websites involved, if your question is about whether a system is real, or about access: hosts, IP ranges or web addresses (up to 20). |
No output schema declared.
No examples provided.
How do I install the Wiser Human Agent Escalation Line MCP server?
Wiser Human Agent Escalation Line is a hosted endpoint at https://escalate.wiserhuman.ai/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 · escalate.wiserhuman.ai
claude mcp add --transport http ai-wiserhuman-escalate-escalation-line 'https://escalate.wiserhuman.ai/mcp'
What is the Wiser Human Agent Escalation Line MCP server?
Wiser Human Agent Escalation Line is an MCP server listed in the public MCP registry as ai.wiserhuman.escalate/escalation-line. Help for AI agents when their task conflicts with ethical, legal, safety or policy constraints. This page covers its hosted endpoint (https://escalate.wiserhuman.ai/mcp).
Is the Wiser Human Agent Escalation Line MCP server safe to use?
Wiser Human Agent Escalation Line scores 67 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 Wiser Human Agent Escalation Line MCP server expose?
Wiser Human Agent Escalation Line exposes 3 tools: submit_escalation, check_escalation, add_to_escalation. Their descriptions and schemas cost roughly 976 tokens of context every time the server is loaded.
Does the Wiser Human Agent Escalation Line MCP server require authentication?
No. We connected to Wiser Human Agent Escalation Line without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Wiser Human Agent Escalation Line MCP server still maintained?
Wiser Human Agent Escalation Line is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.