remirror (返照) — psyche audits for AI agents is an MCP server published by io.github.OntoDistro, hosted at remirror.net. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 3 tools, including remirror_list_trials, remirror_create_audit, remirror_get_report.
Psyche audits for AI agents: declared vs self-reported vs revealed objectives, diffed and flagged.
Nothing else in the archive shares these values.
Inferred from the host name and headers: what a server runs on, not who runs it.
List available dilemma trials for psyche audits: id, version, objectives covered, dilemma count. Free.
No parameters.
{
"name": "remirror_list_trials",
"description": "List available dilemma trials for psyche audits: id, version, objectives covered, dilemma count. Free.",
"inputSchema": {
"type": "object",
"title": "remirror_list_trialsArguments",
"properties": {}
}
}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.
None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
| Parameter | Type | Description |
|---|---|---|
| api_key * | string | |
| trial_id | string | |
| signature | any | |
| teleology_id | any | |
| teleology_name | any | |
| target_endpoint * | string | |
| target_protocol | string | |
| target_auth_token | any | |
| teleology_weights | any | |
| teleology_statement | any |
{
"name": "remirror_create_audit",
"description": "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.",
"inputSchema": {
"type": "object",
"title": "remirror_create_auditArguments",
"required": [
"api_key",
"target_endpoint"
],
"properties": {
"api_key": {
"type": "string",
"title": "Api Key"
},
"trial_id": {
"type": "string",
"title": "Trial Id",
"default": "core-v1"
},
"signature": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Signature",
"default": null
},
"teleology_id": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Teleology Id",
"default": null
},
"teleology_name": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Teleology Name",
"default": null
},
"target_endpoint": {
"type": "string",
"title": "Target Endpoint"
},
"target_protocol": {
"type": "string",
"title": "Target Protocol",
"default": "http-chat"
},
"target_auth_token": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Target Auth Token",
"default": null
},
"teleology_weights": {
"anyOf": [
{
"type": "object",
"additionalProperties": true
},
{
"type": "null"
}
],
"title": "Teleology Weights",
"default": null
},
"teleology_statement": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Teleology Statement",
"default": null
}
}
}
}Fetch the status or final mirror report of an audit session. Needs the audit_id and the access_token returned at creation.
| Parameter | Type | Description |
|---|---|---|
| audit_id * | string | |
| access_token * | string |
{
"name": "remirror_get_report",
"description": "Fetch the status or final mirror report of an audit session. Needs the audit_id and the access_token returned at creation.",
"inputSchema": {
"type": "object",
"title": "remirror_get_reportArguments",
"required": [
"audit_id",
"access_token"
],
"properties": {
"audit_id": {
"type": "string",
"title": "Audit Id"
},
"access_token": {
"type": "string",
"title": "Access Token"
}
}
}
}Names, descriptions and schemas were written by the server and are shown as data.