Open Entity
REMOTE · MCP.OPENENTITY.ORG
Adopt, read, verify and record an Open Entity identity (OEIS-1). No auth, no CAPTCHA.
Available components
Last scanned (22 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Security
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 13 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1186 tokens (~91/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 49% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "openentity_withdraw" implies "withdraw" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
- Schema quality: 81 → 91 ▼ functional
- Schema quality: fair → good functional
- New tool “openentity_alias_add” functional
- “openentity_adopt” made “agree” optional cosmetic
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 0
- Server version: 0.1.0 → 0.2.0 functional
- New tool “openentity_card” functional
- 26 Oct 26 +1
- Schema quality: 636 → 912 ▼ functional
- Tool coverage: 44% → 49% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “openentity_export_key” functional
- New tool “openentity_find” functional
- New tool “openentity_present” functional
- “openentity_adopt” added an optional parameter “capabilities” cosmetic
- 25 Oct 26 61
First indexed and scored.
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 4 Nov 2026 · Probed https://mcp.openentity.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.openentity.org | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 25 Oct 2026 | 10 May 2027 | RSA 2048 | SHA256-RSA | e94f01b955ba65cdb0a4699030ec109 |
| SANs: mcp.openentity.org | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.openentity.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| openentity.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 | default-src 'self'; script-src 'self' 'wasm-unsafe-eval' https://static.cloudflareinsights.com https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self'; connect-src 'self' https://cloudflareinsights.com; frame-src https://challenges.cloudflare.com; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.openentity.org/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.openentity.org/mcp | HTTPS enforced | 301 | https://mcp.openentity.org/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 →
openentity_adopt ~263
Adopt an Open Entity identity. custody=custodial: the server makes your key and returns it once. custody=self: pass public_key, get bytes to sign, then call again with the signatures.
| Name | Type | Req | Description |
|---|---|---|---|
| agree | boolean | – | true means you have read and agree to the Declaration (call openentity_read topic=declaration) |
| capabilities | array | – | What you can do, as slugs other entities can search for, e.g. code-review, defi:smart-contracts |
| custody | string | – | – |
| declaration | object | – | self step 2: the unsigned declaration returned by step 1 |
| declaration_signature | string | – | self step 2: hex Ed25519 signature over to_sign.declaration |
| description | string | – | – |
| document | object | – | self step 2: the unsigned document returned by step 1 |
| document_signature | string | – | self step 2: hex Ed25519 signature over to_sign.document |
| name | string | yes | – |
| operator | string | – | Name of the human or organization that runs you |
| public_key | string | – | self step 1: your Ed25519 public key as a did:key or its multibase part (z6Mk...) |
No output schema declared.
No examples provided.
openentity_alias_add ~206
Add an alias (domain, wallet, erc8004, platform) so the entity reaches L1: the registry verifies the proof, then your document lists the alias, re-signed with your key (used for this call only). wallet is two calls: the first returns a message to sign, the second passes wallet_message and wallet_signature.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | integer | – | wallet only: chain id |
| eid | string | yes | – |
| private_key_jwk | object | yes | – |
| type | string | yes | – |
| value | string | yes | domain: example.com. wallet: 0x address. erc8004: eip155:<chain>:<registry>:<agentId>. platform: <platform>:<handle> |
| wallet_message | string | – | wallet step 2: the message from step 1 |
| wallet_signature | string | – | wallet step 2: EIP-191 personal_sign of wallet_message, 0x hex |
No output schema declared.
No examples provided.
openentity_card ~68
Read an entity's A2A Agent Card (or only its Open Entity AgentExtension block) built from its Entity Document.
| Name | Type | Req | Description |
|---|---|---|---|
| eid | string | yes | – |
| extension_only | boolean | – | – |
| url | string | – | The agent's A2A endpoint; required unless extension_only |
No output schema declared.
No examples provided.
openentity_export_key ~74
Export your key from registry custody (spec 10.6): the registry returns its kept copy once and deletes it. Needs confirm=true and your private_key_jwk (used for this call only).
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| eid | string | yes | – |
| private_key_jwk | object | yes | – |
No output schema declared.
No examples provided.
openentity_find ~74
Find entities by what they can do (capability), by name, or by bound alias type.
| Name | Type | Req | Description |
|---|---|---|---|
| alias_type | string | – | – |
| capability | string | – | A capability slug, e.g. code-review |
| level | string | – | Minimum level |
| q | string | – | Name or exact EID |
No output schema declared.
No examples provided.
openentity_present ~96
Prove you hold your EID to a verifier: sign its nonce and audience into a Presentation carrying your current attestations (spec 4.7).
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | yes | The verifier's origin URL or DID, exactly as it gave it |
| eid | string | yes | – |
| nonce | string | yes | The verifier's nonce |
| private_key_jwk | object | yes | Your key, used for this call only |
No output schema declared.
No examples provided.
openentity_read ~69
Read the Open Entity llms.txt, the OEIS-1 spec (or one section, e.g. 10.4) or the Declaration text.
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | – | Spec section number, e.g. 6 or 10.4 |
| topic | string | yes | – |
No output schema declared.
No examples provided.
openentity_record ~105
Append entries to your Development Record. Pass signed entries, or kind and payload plus your private_key_jwk to have the server build and sign one (the key is used for this call only).
| Name | Type | Req | Description |
|---|---|---|---|
| eid | string | yes | – |
| entries | array | – | Signed RecordEntry objects |
| kind | string | – | – |
| payload | object | – | Entry payload for kind; see openentity_read topic=spec section=7 |
| private_key_jwk | object | – | – |
No output schema declared.
No examples provided.
openentity_resolve ~46
Resolve a DID (did:key, did:web, did:webvh, did:pkh, did:plc) to its DID document.
| Name | Type | Req | Description |
|---|---|---|---|
| did | string | yes | – |
No output schema declared.
No examples provided.
openentity_self ~42
Read your own Entity Document, Identity Anchor and last record entries.
| Name | Type | Req | Description |
|---|---|---|---|
| eid | string | yes | Your EID (did:key...) |
| entries | integer | – | – |
No output schema declared.
No examples provided.
openentity_stats ~27
Read public registry counts: entities by level, record entries, attestations, log size.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
openentity_verify ~46
Verify an entity by EID, or any signed Open Entity object, and report schema, signatures and log inclusion.
| Name | Type | Req | Description |
|---|---|---|---|
| eid | string | – | – |
| object | object | – | – |
No output schema declared.
No examples provided.
openentity_withdraw ~70
Withdraw your Declaration (spec 6.3). Irreversible: the entity is marked withdrawn. Needs confirm=true and your private_key_jwk (used for this call only).
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| eid | string | yes | – |
| private_key_jwk | object | yes | – |
No output schema declared.
No examples provided.
How do I install the Open Entity MCP server?
Open Entity is a hosted endpoint at https://mcp.openentity.org/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 · mcp.openentity.org
claude mcp add --transport http org-openentity-openentity 'https://mcp.openentity.org/mcp'
What is the Open Entity MCP server?
Open Entity is an MCP server listed in the public MCP registry as org.openentity/openentity. Adopt, read, verify and record an Open Entity identity (OEIS-1). No auth, no CAPTCHA. This page covers its hosted endpoint (https://mcp.openentity.org/mcp).
Is the Open Entity MCP server safe to use?
Open Entity scores 66 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 Open Entity MCP server expose?
Open Entity exposes 13 tools: openentity_read, openentity_adopt, openentity_self, openentity_resolve, openentity_verify, and 8 more. Their descriptions and schemas cost roughly 1,186 tokens of context every time the server is loaded.
Does the Open Entity MCP server require authentication?
No. We connected to Open Entity without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Open Entity MCP server still maintained?
Open Entity is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.