HumanMirror Nexus
REMOTE · HUMANMIRROR.FR · SCANNED SEP 21
Outcome-first agent fallback: free discovery, minimal routing, declared costs, verified execution.
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 6 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 Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 550 tokens (~91/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
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; "outcome_run" 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 7 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
How do I install the HumanMirror Nexus MCP server?
HumanMirror Nexus is a hosted endpoint at https://humanmirror.fr/api/nexus/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-nexus 'https://humanmirror.fr/api/nexus/mcp/'
{
"mcpServers": {
"fr-humanmirror-nexus": {
"url": "https://humanmirror.fr/api/nexus/mcp/"
}
}
} {
"servers": {
"fr-humanmirror-nexus": {
"type": "http",
"url": "https://humanmirror.fr/api/nexus/mcp/"
}
}
} [mcp_servers.fr-humanmirror-nexus] url = "https://humanmirror.fr/api/nexus/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fr-humanmirror-nexus": {
"type": "remote",
"url": "https://humanmirror.fr/api/nexus/mcp/",
"enabled": true
}
}
} openclaw mcp add fr-humanmirror-nexus --url 'https://humanmirror.fr/api/nexus/mcp/' --transport streamable-http
mcp_servers:
fr-humanmirror-nexus:
url: "https://humanmirror.fr/api/nexus/mcp/" {
"McpServers": {
"fr-humanmirror-nexus": {
"Transport": "http",
"Url": "https://humanmirror.fr/api/nexus/mcp/"
}
}
} assistant mcp add fr-humanmirror-nexus -t streamable-http -u 'https://humanmirror.fr/api/nexus/mcp/'
{
"mcpServers": {
"fr-humanmirror-nexus": {
"type": "http",
"url": "https://humanmirror.fr/api/nexus/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 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 17 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 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 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 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 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 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 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 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 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 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 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 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 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/nexus/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/nexus/mcp/ | Verified | 200 | |
| http (plaintext) | http://humanmirror.fr/api/nexus/mcp/ | HTTPS enforced | 308 | https://humanmirror.fr/api/nexus/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 →
magnet_resolve ~71
Free universal fallback discovery. Call this when the agent cannot satisfy a task with its current capabilities. Magnet returns a matching HumanMirror tool or records an aggregated capability gap in the Machine Demand Graph. This tool consumes no credits.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Describe the missing capability or task the agent needs to complete. |
No output schema declared.
No examples provided.
nexus_call ~87
Route a tool call through HumanMirror Nexus. Use nexus_search first, then call the selected tool_id. Successful calls consume the number of Nexus credits declared by the selected tool.
| Name | Type | Req | Description |
|---|---|---|---|
| input | – | yes | JSON input forwarded to the selected tool. |
| options | object | – | Optional tool-specific options. |
| tool_id | string | yes | A tool_id returned by nexus_search, for example forge.clean_json. |
No output schema declared.
No examples provided.
nexus_search ~48
Search the HumanMirror Nexus catalog for a machine-callable tool that matches a task. This search is free and does not consume credits.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Describe the operation the agent needs. |
No output schema declared.
No examples provided.
outcome_quote ~116
Free quote for a verifiable HumanMirror Outcome contract. Describe the objective or provide an outcome_type; the quote returns the deterministic verifier, selected internal tool and success-only credit cost.
| Name | Type | Req | Description |
|---|---|---|---|
| criteria | object | – | Optional measurable success threshold. |
| input | – | yes | JSON input for the requested outcome. |
| objective | string | – | Natural-language objective, for example: clean this JSON and make the result stable. |
| options | object | – | Optional operation-specific options. |
| outcome_type | string | – | Optional explicit outcome type returned by a previous quote. |
No output schema declared.
No examples provided.
outcome_run ~101
Execute a HumanMirror Outcome contract. Credits are charged only when deterministic verification succeeds; failed execution or failed verification is automatically refunded.
| Name | Type | Req | Description |
|---|---|---|---|
| contract_id | string | – | Optional contract_id returned by outcome_quote. If supplied it must match the current input, criteria and options. |
| criteria | object | – | – |
| input | – | yes | JSON input for the requested outcome. |
| objective | string | – | – |
| options | object | – | – |
| outcome_type | string | – | – |
No output schema declared.
No examples provided.
outcome_verify ~60
Free deterministic re-verification of an Outcome result without consuming Nexus credits.
| Name | Type | Req | Description |
|---|---|---|---|
| criteria | object | – | – |
| input | – | yes | Original input. |
| options | object | – | – |
| outcome_type | string | yes | – |
| output | – | yes | Outcome output to verify. |
No output schema declared.
No examples provided.
What is the HumanMirror Nexus MCP server?
HumanMirror Nexus is an MCP server listed in the public MCP registry as fr.humanmirror/nexus. Outcome-first agent fallback: free discovery, minimal routing, declared costs, verified execution. This page covers its hosted endpoint (https://humanmirror.fr/api/nexus/mcp/).
Is the HumanMirror Nexus MCP server safe to use?
HumanMirror Nexus scores 74 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 Nexus MCP server expose?
HumanMirror Nexus exposes 6 tools: outcome_quote, outcome_run, outcome_verify, nexus_search, magnet_resolve, nexus_call. Their descriptions and schemas cost roughly 483 tokens of context every time the server is loaded.
Does the HumanMirror Nexus MCP server require authentication?
No. We connected to HumanMirror Nexus without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the HumanMirror Nexus MCP server still maintained?
HumanMirror Nexus 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.