HumanMirror Outcome

fr.humanmirrorPublished by humanmirror.frOfficial publisherv1.0.1Updated Oct 24, 2026

Verified AI-agent outcomes: secret scanning, JSON cleanup, dedupe, anomaly and schema checks.

The publisher's own server: HumanMirror Flow

VerifiedStreamable HTTPWeb executableSecurity & Monitoring Data & Analytics

Server details

Identifier: fr.humanmirror/outcome
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to humanmirror.fr, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/fr.humanmirror%2Foutcome.svg)](https://sourceweft.com/mcp/fr.humanmirror%2Foutcome?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A remote MCP server that runs one deterministic, independently verified data outcome per call, such as JSON cleanup, deduplication, entity normalization, schema

What you can do: Execute a single deterministic, independently verified outcome through one tool, humanmirror_outcome. Get free dry-run quotes before committing to a run. Apply JSON cleanup, deduplication, entity normalization, data-quality thresholds, anomaly scans, secret scans and schema checks. Credits are kept only on verified success and refunded if execution or verification fails.
When to use it: Useful when you want a one-off, verifiable data-cleaning or checking step, such as cleaning JSON, removing duplicates, normalizing entities, scanning for secrets or anomalies, or enforcing schema and quality thresholds, without building that logic yourself.
Requirements: A remote streamable HTTP endpoint; no local package or runtime. An Authorization header with a Bearer token is optional for initialize, tools/list and dry-run discovery, but required for credit-backed execution. Execution consumes Nexus credits.

Before you install

Execution spends Nexus credits (5 per run, kept only on verified success and refunded on failure). The Authorization header carries a secret token; keep it private. Data submitted for processing is sent to a third-party service, so avoid sending sensitive content unless acceptable.

Installation

In SourceWeft

Open HumanMirror Outcome in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/fr.humanmirror%2Foutcome/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "humanmirror-outcome": {
      "type": "http",
      "url": "https://humanmirror.fr/api/outcome/mcp/"
    }
  }
}

README

This repository has no README.

Tools

humanmirror_outcome

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.

Parametersinputrequireddry_runoptionscriteriaobjectivecontract_idoutcome_type

Version history

v1.0.1LatestOct 9, 2026
v1.0.0Sep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.