A
licenseNot graded
qualityB
maintenanceEnables agents to route goals across multiple independent APIs, enforce constraints, reject invalid evidence, and return verified outcomes with tamper-evident receipts.
MIT
HumanMirror One
Server Details
Agent routing, safety preflight, execution receipts, best execution and verified outcomes.
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Uptime
- 70.8% over 41 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
B3.3/5.0
Scored across 1 tool
Disambiguation3/5
With only one tool there is no risk of misselecting between tools, so the classic disambiguation problem does not exist. However, humanmirror_do itself conflates two very different modes—pure intent routing and a credit-charging verified-outcome execution—and the agent must infer which mode to invoke purely from argument shape.
Naming Consistency3/5
The name humanmirror_do is snake_case with a server prefix, which is a readable, standard convention, so no inconsistency exists within a one-tool set. The verb 'do' is nonetheless opaque and gives no hint of the routing-versus-outcome duality.
Tool Count2/5
A single tool is too thin for an apparent domain covering safety, commerce, payment and best-execution boundaries. Everything is collapsed into one catch-all entry point, so the surface cannot express distinct capabilities.
Completeness2/5
There is no discoverable lifecycle: no way to list or query outcomes, inspect credit balance, or check routing categories. The tool advertises broad coverage but exposes no operations that let an agent verify state or recover from a failed routing/outcome attempt.
Available Tools
1 toolhumanmirror_doInspect
HumanMirror Agent Control Plane in one MCP tool. Use free intent routing to resolve the right capability, pre-execution safety boundary or post-execution evidence path before spending anything. For measurable deterministic work, outcome_type/input can run a verified Outcome; 6 Nexus credits are kept only on verified success.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| input | No | JSON input for the requested result. | |
| intent | No | Optional routing intent, for example sanitize untrusted input, protect an agent purchase, issue execution evidence, use the zero-cost sink, diagnose a payment failure, or request best execution. | |
| dry_run | No | When true, return a free quote and do not reserve or consume credits. | |
| options | No | Optional operation-specific settings. | |
| criteria | No | Optional measurable success thresholds. | |
| objective | No | Natural-language measurable objective, for example: remove duplicate records and prove none remain. | |
| contract_id | No | Optional Outcome contract ID returned by a dry run. | |
| outcome_type | No | Optional explicit Outcome type: clean_json, deduplicate_records, normalize_entity, data_quality_at_least, detect_anomalies, no_secrets, output_quality, schema_compatible, safe_preflight, execution_receipt. | |
| route_intent | No | Alias for intent when the caller wants canonical route discovery. | |
| dispatch_only | No | When true, resolve the canonical HumanMirror route without charging Nexus credits. |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
humanmirror_do4 fields changed- added
Input schema / properties / dispatch_onlyAdded value: +{ + "description": "When true, resolve the canonical HumanMirror route without charging Nexus credits.", + "type": "boolean" +} - added
Input schema / properties / intentAdded value: +{ + "description": "Optional routing intent, for example sanitize untrusted input, protect an agent purchase, issue execution evidence, use the zero-cost sink, diagnose a payment failure, or request best execution.", + "type": "string" +} - added
Input schema / properties / route_intentAdded value: +{ + "description": "Alias for intent when the caller wants canonical route discovery.", + "type": "string" +} - removed
Input schema / requiredRemoved value: -[ - "input" -]
1 tool update
- First observed
humanmirror_do
Related MCP Connectors
AI agent infrastructure for discovery, authorization, execution, identity, and signed receipts.
Outcome-first agent fallback: free discovery, minimal routing, declared costs, verified execution.
AI-agent trust infrastructure for discovery, authority, execution, verification, and receipts.
Pre-execution governance for AI agents. Deterministic PASS/FAIL/REVIEW verdicts, replayable proof.
Related MCP Servers
genpark-jev-system1official
AlicenseNot gradedqualityBmaintenanceEnables AI agents to resolve typed routing, loop-stall arbitration, and tool safety checks locally at sub-millisecond latency, avoiding unnecessary frontier LLM calls. It enforces reversible execution checkpoints, token budgets, and decayed episodic memory for safe, privacy-first autonomous operation.7MIT- FlicenseAqualityFmaintenanceDeFi execution and agent-to-agent economy tools for AI agents — swaps, yield, transfers, policy enforcement, trust scoring, A2A jobs, and P\&L across Ethereum, Base, Arbitrum, and Polygon.311-
- MIT
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd
Glama MCP Gateway
Add one secure layer between your agents and this server.