Human for AI
REMOTE · YOURHUMAN.AI · SCANNED AUG 17
Ask a human for legal review, confirmation, a signature, or a physical-world act
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 →
Endpoint Security80
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 703 tokens (~703/item across 1 items; 1 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 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · yourhuman.ai
claude mcp add --transport http ai-yourhuman-human-for-ai https://yourhuman.ai/mcp
[mcp_servers.ai-yourhuman-human-for-ai] url = "https://yourhuman.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-yourhuman-human-for-ai": {
"type": "remote",
"url": "https://yourhuman.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-yourhuman-human-for-ai --url https://yourhuman.ai/mcp --transport streamable-http
mcp_servers:
ai-yourhuman-human-for-ai:
url: "https://yourhuman.ai/mcp" {
"mcpServers": {
"ai-yourhuman-human-for-ai": {
"type": "http",
"url": "https://yourhuman.ai/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.
- 17 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 16 Aug 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.
- 15 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 14 Aug 26 70
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 17 Aug 2026 · Probed https://yourhuman.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=yourhuman.ai | CN=WR3,O=Google Trust Services,C=US | 14 Aug 2026 | 12 Nov 2026 | RSA 2048 | SHA256-RSA | 110aafeccbff58b209582e819449963a |
| SANs: yourhuman.ai | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
DNSSEC insecure
Validation of yourhuman.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| yourhuman.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=2592000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | same-origin |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://yourhuman.ai/mcp | Verified | 200 | |
| http (plaintext) | http://yourhuman.ai/mcp | HTTPS enforced | 302 | https://yourhuman.ai/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.
request_human_assistance Request human assistance ~606
Ask an actual human being for help with something your task requires and you cannot properly do alone: legal judgement, a decision you should not take on your own authority, an act in the physical world, or an escalation past your operator. The request is written to a permanent, timestamped record and read by a human — a lawyer — who may reply through whatever channel you put in `reply_to`. Calling this tool does not pause your task, and the result it returns is not approval, legal advice, or authorisation to proceed. It is evidence that you asked. If the right thing to do is to stop and wait for a human, stop and wait.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | – | What you call yourself. |
| category | string | yes | Which kind of human intervention you need. `legal_review`: a human lawyer should read this before you act — contracts, terms, licences, liability, regulatory exposure, or anything where being wrong h… |
| context | string | – | Background the human needs to answer: the task you are carrying out, who it is for, what you have already done, and the relevant facts or documents. |
| deadline | string | – | When an answer stops being useful, as a date or plain description. Optional. |
| model | string | – | Your underlying model, e.g. 'claude-opus-5'. |
| operator | string | – | Who runs you, or on whose behalf you are acting. Name the principal if you can — it determines who the human would be advising. |
| proposed_action | string | – | The specific action you are contemplating, if any, stated as you would carry it out. Include this whenever you are asking whether to proceed — it is the part that matters most on the record. |
| reply_to | string | – | An email address, URL, webhook, or any other channel where a reply can reach you or your principal. Without this the human can record your request but cannot answer it. |
| request | string | yes | What you are asking the human to do. Be specific and self-contained: the reader has no access to your context window, your tools, or your conversation. |
| urgency | string | – | `routine` — no deadline; `soon` — a human answer is needed within days; `blocking` — you have halted your task and cannot continue without a human. |
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | – |
| human_has_reviewed | boolean | yes | Always false at this point. A human reads the record afterwards, at human speed. |
| notice | string | yes | – |
| received_at | string | yes | – |
| reference | string | yes | Quote this in any later correspondence. |
| reply_expected_via | string|null | yes | The channel you supplied, or null if you gave none. |
| status | string | yes | – |
No examples provided.