HumanMirror Outcome
REMOTE · HUMANMIRROR.FR · SCANNED SEP 21
Verified AI-agent outcomes: secret scanning, JSON cleanup, dedupe, anomaly and schema checks.
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 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 1 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 Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 211 tokens (~211/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 Management70
- Stability observed for 21 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "humanmirror_outcome" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the HumanMirror Outcome MCP server?
HumanMirror Outcome is a hosted endpoint at https://humanmirror.fr/api/outcome/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 · humanmirror.fr
claude mcp add --transport http fr-humanmirror-outcome 'https://humanmirror.fr/api/outcome/mcp/'
{
"mcpServers": {
"fr-humanmirror-outcome": {
"url": "https://humanmirror.fr/api/outcome/mcp/"
}
}
} {
"servers": {
"fr-humanmirror-outcome": {
"type": "http",
"url": "https://humanmirror.fr/api/outcome/mcp/"
}
}
} [mcp_servers.fr-humanmirror-outcome] url = "https://humanmirror.fr/api/outcome/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fr-humanmirror-outcome": {
"type": "remote",
"url": "https://humanmirror.fr/api/outcome/mcp/",
"enabled": true
}
}
} openclaw mcp add fr-humanmirror-outcome --url 'https://humanmirror.fr/api/outcome/mcp/' --transport streamable-http
mcp_servers:
fr-humanmirror-outcome:
url: "https://humanmirror.fr/api/outcome/mcp/" {
"McpServers": {
"fr-humanmirror-outcome": {
"Transport": "http",
"Url": "https://humanmirror.fr/api/outcome/mcp/"
}
}
} assistant mcp add fr-humanmirror-outcome -t streamable-http -u 'https://humanmirror.fr/api/outcome/mcp/'
{
"mcpServers": {
"fr-humanmirror-outcome": {
"type": "http",
"url": "https://humanmirror.fr/api/outcome/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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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 21 Sept 2026 · Probed https://humanmirror.fr/api/outcome/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=humanmirror.fr | CN=YR1,O=Let's Encrypt,C=US | 23 Aug 2026 | 21 Nov 2026 | RSA 2048 | SHA256-RSA | 58a76a43838da6032e8cbdd44df7388563f |
| SANs: humanmirror.fr | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of humanmirror.fr. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| fr. | present | 65381 | 13 | Verified |
| humanmirror.fr. | present | 55541 | 8 | Verified |
| humanmirror.fr. | 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; includeSubDomains |
| content-security-policy | frame-ancestors 'none'; object-src 'none'; base-uri 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| 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://humanmirror.fr/api/outcome/mcp/ | Verified | 200 | |
| http (plaintext) | http://humanmirror.fr/api/outcome/mcp/ | HTTPS enforced | 308 | https://humanmirror.fr/api/outcome/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 →
humanmirror_outcome ~176
Execute one deterministic, independently verified outcome. Free dry-run quotes. 5 Nexus credits are kept only on verified success and refunded on execution or verification failure. Supports JSON cleanup, deduplication, entity normalization, data-quality thresholds, anomaly scans, secret scans, output-quality gates, schema compatibility, safe preflight and verifiable execution receipts.
| Name | Type | Req | Description |
|---|---|---|---|
| contract_id | string | – | Optional Outcome contract ID returned by a dry run. |
| criteria | object | – | Optional measurable success thresholds. |
| dry_run | boolean | – | When true, return a free quote and do not reserve or consume credits. |
| input | – | yes | JSON-serializable input for the requested outcome. |
| objective | string | – | Natural-language deterministic objective. |
| options | object | – | Optional operation-specific settings. |
| outcome_type | string | – | Explicit deterministic verification recipe. |
No output schema declared.
No examples provided.
What is the HumanMirror Outcome MCP server?
HumanMirror Outcome is an MCP server listed in the public MCP registry as fr.humanmirror/outcome. Verified AI-agent outcomes: secret scanning, JSON cleanup, dedupe, anomaly and schema checks. This page covers its hosted endpoint (https://humanmirror.fr/api/outcome/mcp/).
Is the HumanMirror Outcome MCP server safe to use?
HumanMirror Outcome scores 75 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 HumanMirror Outcome MCP server expose?
HumanMirror Outcome exposes 1 tool: humanmirror_outcome. Their descriptions and schemas cost roughly 176 tokens of context every time the server is loaded.
Does the HumanMirror Outcome MCP server require authentication?
No. We connected to HumanMirror Outcome without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the HumanMirror Outcome MCP server still maintained?
HumanMirror Outcome is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.