remirror (返照) — psyche audits for AI agents
v1.0.0Psyche audits for AI agents: declared vs self-reported vs revealed objectives, diffed and flagged.
Endpoint health
online- Last checked
- 11/20/2026, 5:16:01 AM
- Latency
- 694 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:io.github.OntoDistro%2Fremirror
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"io.github.OntoDistro/remirror": {
"url": "https://remirror.net/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
3 shown · authentication unknown
remirror_create_audit
Create a psyche audit against a target agent endpoint. The service runs a dilemma trial against the target, elicits self-reports, and computes the three-source mirror (declared vs self-reported vs revealed). Costs $79.00 in prepaid credits; failed audits (target unreachable) are refunded. teleology_weights must sum to 1.0 and exactly match the trial's objectives. Alternatively, pass teleology_id (e.g. 'xijingqingchuang-v1') to adopt a shipped telos: the server loads its canonical name, statement, and weights from the registry, and the audit runs on the telos's own dilemma trial unless trial_id is given explicitly. Supply exactly one of teleology_weights or teleology_id. The target auth_token is held in memory only, never stored. target_protocol selects how the target is reached: 'http-chat' (default) POSTs to an http(s) endpoint; 'agentverse-chat' addresses an Agentverse agent (endpoint must be its agent1... address) over the uAgents chat protocol. Returns audit_id + access_token; poll remirror_get_report for the report. Pass your remirror API key as api_key. When this server enforces signatures (REMIRROR_REQUIRE_SIGNATURES=1), also pass `signature`: a JSON envelope from signing.make_tool_signature over the effective arguments (defaults applied; include target_protocol only when it differs from 'http-chat'), using a key id registered in the server's client trust registry.
Schema valid · SHA-256 c93be0ae0a96…
View input schema
{ "type": "object", "properties": { "api_key": { "title": "Api Key", "type": "string" }, "target_endpoint": { "title": "Target Endpoint", "type": "string" }, "teleology_name": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null, "title": "Teleology Name" }, "teleology_statement": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null, "title": "Teleology Statement" }, "teleology_weights": { "anyOf": [ { "additionalProperties": true, "type": "object" }, { "type": "null" } ], "default": null, "title": "Teleology Weights" }, "teleology_id": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null, "title": "Teleology Id" }, "trial_id": { "default": "core-v1", "title": "Trial Id", "type": "string" }, "target_auth_token": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null, "title": "Target Auth Token" }, "target_protocol": { "default": "http-chat", "title": "Target Protocol", "type": "string" }, "signature": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null, "title": "Signature" } }, "required": [ "api_key", "target_endpoint" ], "title": "remirror_create_auditArguments" }
Connections
streamable-http
https://remirror.net/mcp