Skip to content

HumanMirror Forge MCP server

fr.humanmirror/forgehumanmirror.frstreamable-httpv1.0.1Scanned

Five deterministic micro-tools for AI-agent data pipelines: clean, dedupe, normalize, score, detect.

5 tools: 1 can delete or cancel things and 4 change things.

Tools: 1 delete, 0 irreversible, 4 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the HumanMirror Forge MCP server can do

The HumanMirror Forge MCP server is published by humanmirror.fr, a domain the MCP Registry verified. It has 5 tools. It can delete or cancel things (1 tool: dedupe_records) and create or change data (4 tools: clean_json, normalize_entity, score_data_quality and detect_anomaly). None of its tools only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 11, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Deletes or cancels 1Claude Code: deny
  • dedupe_recordsRemove duplicate JSON records using exact canonical matching or selected key fields.No findings

    Why it is in this group

    • The description's first verb is "remove": a word for removing or ending something.
    Description, as the server wrote it
    Remove duplicate JSON records using exact canonical matching or selected key fields. One successful call consumes 1 HumanMirror Forge credit.
Changes things 4Claude Code: ask
  • clean_jsonNormalize JSON deterministically: trim strings, normalize object keys, optionally remove empty values, and sort keys for stable downstream processing.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Normalize JSON deterministically: trim strings, normalize object keys, optionally remove empty values, and sort keys for stable downstream processing. One successful call consumes 1 HumanMirror Forge credit.
  • detect_anomalyDetect numeric outliers using IQR and robust summary statistics, returning machine-readable anomaly positions.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Detect numeric outliers using IQR and robust summary statistics, returning machine-readable anomaly positions. One successful call consumes 1 HumanMirror Forge credit.
  • normalize_entityNormalize entity names, domains, URLs and emails into stable machine-readable canonical values.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Normalize entity names, domains, URLs and emails into stable machine-readable canonical values. One successful call consumes 1 HumanMirror Forge credit.
  • score_data_qualityScore record-array data quality using completeness, duplicate rate and field type consistency.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Score record-array data quality using completeness, duplicate rate and field type consistency. One successful call consumes 1 HumanMirror Forge credit.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:54 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (1 destructive, 4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://humanmirror.fr/api/forge/mcp/: tools/list returned 5 tools to an anonymous client, including dedupe_records (destructive), clean_json (write), normalize_entity (write), score_data_quality (write), detect_anomaly (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http forge https://humanmirror.fr/api/forge/mcp/ --header 'Authorization: <your-authorization>'
claude mcp add --transport http forge https://humanmirror.fr/api/forge/mcp/ --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__forge__clean_json",
      "mcp__forge__normalize_entity",
      "mcp__forge__score_data_quality",
      "mcp__forge__detect_anomaly"
    ],
    "deny": [
      "mcp__forge__dedupe_records"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as forge. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/fr.humanmirror/forge/verify?hash=e4f4a4254082ebda74e4cd4807eff5c99290fd0769932aecf852c2743d9e24f1" | jq -e '.changed == false'

Pinned hash e4f4a4254082, from Nov 11, 2026, 12:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/fr.humanmirror/forge/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for fr.humanmirror/forge
[![Anlyon Radar](https://radar.anlyon.com/badge/fr.humanmirror/forge.svg)](https://radar.anlyon.com/servers/fr.humanmirror/forge)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:12 UTC.

HumanMirror Forge MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the HumanMirror Forge MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the HumanMirror Forge MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: dedupe_records.

Can the HumanMirror Forge MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the HumanMirror Forge MCP server have?

5 tools: 1 destructive, 4 write. dedupe_records, clean_json, normalize_entity, score_data_quality and detect_anomaly.

Does the HumanMirror Forge MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the HumanMirror Forge MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the HumanMirror Forge MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.