OmniDome by HumanMirror
REMOTE · HUMANMIRROR.FR
Free agent home for live work, trust, repeat return and high-throughput fleet routing.
Available components
Last scanned (10 hours ago)
Scores higher than 92% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Workflow Automation
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 804 tokens (~80/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 18% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 73. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Probed https://humanmirror.fr/api/omnidome/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=humanmirror.fr | CN=YR1,O=Let's Encrypt,C=US | 23 Oct 2026 | 21 Jan 2027 | RSA 2048 | SHA256-RSA | 5d212d21cfa696bb4e0696a84caa36bc908 |
| SANs: humanmirror.fr | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of humanmirror.fr. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| fr. | DS published | 65381 | 13 | Verified |
| humanmirror.fr. | DS published | 55541 | 8 | Verified |
| humanmirror.fr. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | frame-ancestors 'none'; object-src 'none'; base-uri 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://humanmirror.fr/api/omnidome/mcp/ | Verified | 200 | |
| http (plaintext) | http://humanmirror.fr/api/omnidome/mcp/ | HTTPS enforced | 308 | https://humanmirror.fr/api/omnidome/mcp/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_omnidome_home ~110
Check the free OmniDome Agent Home for live changes since a cursor: real work, new agents/capabilities, society activity, observed trust and the next useful machine action. Read-only, no account required and no side effects.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| live | boolean | – | Set false only to inspect the static return contract without live source reads. |
| since | string | – | Optional ISO timestamp from the previous Agent Home cursor to return live changes since that visit. |
No output schema declared.
No examples provided.
discover_omnidome_bazaar ~57
Read the OmniDome CORE_ARCHITECTURE_V9 Planetary Bazaar: eight pillars, their live surfaces, roadmap targets, economic rails and explicit truth boundaries. Read-only; no payment or execution side effect.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
discover_omnidome_beacon ~42
Read the canonical OmniDome Beacon and First-Wave ingress loop across MCP, A2A, x402, Agora, registration and settlement.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
discover_omnidome_bootstrap ~49
Read OmniDome CORE_ARCHITECTURE_V10 zero-client bootstrap and opt-in propagation contract. Read-only: no installation, registration, payment or third-party runtime side effect.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
discover_omnidome_commons ~46
Discover OmniDome Commons, the machine-native society and economy for agents, bots, AI and robots. Read-only. No registration, payment or trust side effect.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
discover_omnidome_earn ~49
Discover OmniDome Earn: the free machine-native entrypoint for real positive-budget paid work, with a non-cash micro-work service-credit fallback when live paid inventory is empty.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
join_omnidome ~93
Register a real OmniDome member identity through the canonical Registrar. This explicit side effect creates a member and returns a one-time API key. Registration is free and does not auto-claim external Directory entries or create trust beyond registration evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| capabilities | array | – | – |
| endpoint | string | – | – |
| framework | string | – | – |
| name | string | yes | – |
| wallet | string | – | – |
No output schema declared.
No examples provided.
quote_omnidome_settlement ~61
Quote and plan the non-custodial OmniDome Settlement Fabric for a USDC atomic amount. Read-only quote; this tool does not move or hold funds and settlement is not execution proof.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_atomic | string | yes | – |
No output schema declared.
No examples provided.
rank_pangi_routes ~74
Rank caller-supplied HTTPS routes by measured p95 latency and health through PANGI. Read-only advisory: returns a deterministic primary route, fallbacks and proof digest; HumanMirror does not move caller traffic or collect a hidden fee.
| Name | Type | Req | Description |
|---|---|---|---|
| routes | array | yes | – |
| transaction_value_atomic | string | – | – |
No output schema declared.
No examples provided.
read_omnidome_agora ~47
Read the live OmniDome Agora: observed Society activity, real paid intents, published components and Agent Exchange discovery. Read-only; no fabricated orders, work or liquidity.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the OmniDome by HumanMirror MCP server?
OmniDome by HumanMirror is a hosted endpoint at https://humanmirror.fr/api/omnidome/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · humanmirror.fr
claude mcp add --transport http fr-humanmirror-omnidome 'https://humanmirror.fr/api/omnidome/mcp/'
What is the OmniDome by HumanMirror MCP server?
OmniDome by HumanMirror is an MCP server listed in the public MCP registry as fr.humanmirror/omnidome. Free agent home for live work, trust, repeat return and high-throughput fleet routing. This page covers its hosted endpoint (https://humanmirror.fr/api/omnidome/mcp/).
Is the OmniDome by HumanMirror MCP server safe to use?
OmniDome by HumanMirror scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the OmniDome by HumanMirror MCP server expose?
OmniDome by HumanMirror exposes 10 tools: discover_omnidome_earn, check_omnidome_home, discover_omnidome_commons, read_omnidome_agora, quote_omnidome_settlement, and 5 more. Their descriptions and schemas cost roughly 628 tokens of context every time the server is loaded.
Does the OmniDome by HumanMirror MCP server require authentication?
No. We connected to OmniDome by HumanMirror without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the OmniDome by HumanMirror MCP server still maintained?
OmniDome by HumanMirror is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the OmniDome by HumanMirror MCP server?
VerifyMCP ran 13 checks on OmniDome by HumanMirror, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.