Is the Humanmirror Forge MCP server down?

mcp-registry/fr.humanmirror/forge · v1.0.0

healthy
Last checked 2026-10-26 17:12 UTC · handshake 124ms

As of 2026-10-26 17:12 UTC, the Humanmirror Forge MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 13.2 hours.

uptime (30d checks)
100%
checks observed
4,884
outages (90d)
2
tools
5

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

Point your MCP client at this streamable-http endpoint: https://humanmirror.fr/api/forge/mcp/

Agent-readiness: C (73/100)

C (73/100): 0 error(s), 3 warning(s) across 5 tool(s); ~636 tokens of tool definitions.
Scores higher than 8% of 15,769 MCP servers Glimind has audited.
Its tool list costs an agent ~636 tokens per session — lighter than 85% of servers.
73 → 73 since 2026-10-17
no tool-poisoning patterns
Schemas70
Descriptions62
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (4)

5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: clean_json, dedupe_records, detect_anomaly, normalize_entity, score_data_quality

2 tool(s) have parameters with no type (no type/enum/anyOf/$ref).

Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →

Tools: clean_json, normalize_entity

2 parameter(s) across 2 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: clean_json, dedupe_records

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 2 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Ffr.humanmirror%2Fforge/fixes

clean_json 1 change 
{
  "name": "clean_json",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "input"
    ],
    "properties": {
      "input": {
        "description": "Any JSON value to normalize.",
        "type": "string"
      },
      "options": {
        "type": "object",
        "properties": {
          "sort_keys": {
            "type": "boolean"
          },
          "remove_empty": {
            "type": "boolean"
          },
          "trim_strings": {
            "type": "boolean"
          },
          "normalize_keys": {
            "type": "boolean"
          }
        },
        "additionalProperties": false
      }
    },
    "additionalProperties": false
  }
}
normalize_entity 1 change 
{
  "name": "normalize_entity",
  "description": "Normalize entity names, domains, URLs and emails into stable machine-readable canonical values. One successful call consumes 1 HumanMirror Forge credit.",
  "inputSchema": {
    "type": "object",
    "required": [
      "input"
    ],
    "properties": {
      "input": {
        "description": "Entity name string or object with fields such as name, domain, url and email.",
        "type": "string"
      }
    },
    "additionalProperties": false
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/fr.humanmirror/forge"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/fr.humanmirror/forge"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Ffr.humanmirror%2Fforge.svg)](https://glimind.com/server/mcp-registry%2Ffr.humanmirror%2Fforge?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Ffr.humanmirror%2Fforge?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Ffr.humanmirror%2Fforge.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Ffr.humanmirror%2Fforge.svg
   :target: https://glimind.com/server/mcp-registry%2Ffr.humanmirror%2Fforge?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:459b0f5222a011e3…, first seen 2026-10-17, included at leaf 11631 of 74,329. Version history · verify what your client received.

Tools (5)

Compare: most reliable data servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Humanmirror Forge MCP server down right now?

As of 2026-10-26 17:12 UTC, the Humanmirror Forge MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 13.2 hours.

How many tools does Humanmirror Forge MCP server provide?

Humanmirror Forge MCP server advertises 5 tools, including clean_json, dedupe_records, detect_anomaly, normalize_entity, score_data_quality.

How do I install Humanmirror Forge MCP server?

Point your MCP client at this streamable-http endpoint: https://humanmirror.fr/api/forge/mcp/

Is the Humanmirror Forge MCP server safe to connect to an AI agent?

Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Humanmirror Forge MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve