Verified AI-agent outcomes: secret scanning, JSON cleanup, dedupe, anomaly and schema checks.
Connect Remote server
claude mcp add --transport http outcome https://humanmirror.fr/api/outcome/mcp/ --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"outcome": {
"url": "https://humanmirror.fr/api/outcome/mcp/",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"outcome": {
"type": "http",
"url": "https://humanmirror.fr/api/outcome/mcp/",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://humanmirror.fr/api/outcome/mcp/
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools 1 found in our last check
humanmirror_outcomeExecute 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…
Headers
| Name | Description |
|---|---|
AuthorizationOptional, secret | Optional for initialize, tools/list and dry-run discovery. Required for credit-backed execution. Use: Bearer hm_nexus_… |
Details
| Endpoint | https://humanmirror.fr/api/outcome/mcp/ (Streamable HTTP) |
| First published | 9 Oct 2026 |
| Last updated | 9 Oct 2026 |
| Registry name | fr.humanmirror/outcome |
More security servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
