Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

HumanMirror One

REMOTE · HUMANMIRROR.FR · SCANNED SEP 21

One MCP tool for verified AI-agent outcomes with success-only charging.

Available components

+5 this week 76 Trust /100
Trust breakdown (7 categories)

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
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 243 tokens (~243/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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • 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
Install

How do I install the HumanMirror One MCP server?

HumanMirror One is a hosted endpoint at https://humanmirror.fr/api/one/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

# add to Claude Code
claude mcp add --transport http fr-humanmirror-one 'https://humanmirror.fr/api/one/mcp/'
// .cursor/mcp.json
{
  "mcpServers": {
    "fr-humanmirror-one": {
      "url": "https://humanmirror.fr/api/one/mcp/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "fr-humanmirror-one": {
      "type": "http",
      "url": "https://humanmirror.fr/api/one/mcp/"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.fr-humanmirror-one]
url = "https://humanmirror.fr/api/one/mcp/"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fr-humanmirror-one": {
      "type": "remote",
      "url": "https://humanmirror.fr/api/one/mcp/",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add fr-humanmirror-one --url 'https://humanmirror.fr/api/one/mcp/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  fr-humanmirror-one:
    url: "https://humanmirror.fr/api/one/mcp/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "fr-humanmirror-one": {
      "Transport": "http",
      "Url": "https://humanmirror.fr/api/one/mcp/"
    }
  }
}
# add to Vellum
assistant mcp add fr-humanmirror-one -t streamable-http -u 'https://humanmirror.fr/api/one/mcp/'
// mcp.json
{
  "mcpServers": {
    "fr-humanmirror-one": {
      "type": "http",
      "url": "https://humanmirror.fr/api/one/mcp/"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 21 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.

  • 20 Sept 26 +2
    • MCP protocol: fail → pass functional
    • MCP protocol version: 2025-06-18 → 2026-07-28 functional
  • 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.

  • 16 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.

  • 14 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 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.

  • 8 Sept 26 −1
    • MCP protocol: pass → fail functional
    • MCP protocol version: 2026-07-28 → 2025-06-18 functional
Diagnostics

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/one/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/one/mcp/ Verified 200
http (plaintext) http://humanmirror.fr/api/one/mcp/ HTTPS enforced 308 https://humanmirror.fr/api/one/mcp/
MCP tools · 1 exposed · ~201 tokens

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 →

Tool Tokens
humanmirror_do ~201

One HumanMirror tool for measurable deterministic outcomes. Set dry_run=true for a free quote. Otherwise HumanMirror executes and independently verifies the result; 6 Nexus credits are kept only on verified success and refunded on execution or verification failure.

NameTypeReqDescription
contract_idstringOptional Outcome contract ID returned by a dry run.
criteriaobjectOptional measurable success thresholds.
dry_runbooleanWhen true, return a free quote and do not reserve or consume credits.
inputyesJSON input for the requested result.
objectivestringNatural-language measurable objective, for example: remove duplicate records and prove none remain.
optionsobjectOptional operation-specific settings.
outcome_typestringOptional explicit Outcome type: clean_json, deduplicate_records, normalize_entity, data_quality_at_least, detect_anomalies, no_secrets, output_quality, schema_compatible, safe_preflight, execution_re…

No output schema declared.

No examples provided.

Common questions

What is the HumanMirror One MCP server?

HumanMirror One is an MCP server listed in the public MCP registry as fr.humanmirror/one. One MCP tool for verified AI-agent outcomes with success-only charging. This page covers its hosted endpoint (https://humanmirror.fr/api/one/mcp/).

Is the HumanMirror One MCP server safe to use?

HumanMirror One scores 76 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 One MCP server expose?

HumanMirror One exposes 1 tool: humanmirror_do. Their descriptions and schemas cost roughly 201 tokens of context every time the server is loaded.

Does the HumanMirror One MCP server require authentication?

No. We connected to HumanMirror One without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the HumanMirror One MCP server still maintained?

HumanMirror One 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.