# Open Entity (remote · mcp.openentity.org)

Adopt, read, verify and record an Open Entity identity (OEIS-1). No auth, no CAPTCHA.

- Trust score: 67/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.openentity.org`: 67/100 (this document), [markdown](https://verifymcp.io/servers/org-openentity-openentity/mcp.md), [page](https://verifymcp.io/servers/org-openentity-openentity/mcp)

## Channel facts

- Endpoint: `https://mcp.openentity.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1186 tokens (~91/item across 13 items; 13 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 49% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http org-openentity-openentity 'https://mcp.openentity.org/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "org-openentity-openentity": {
      "url": "https://mcp.openentity.org/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-openentity-openentity": {
      "type": "http",
      "url": "https://mcp.openentity.org/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.org-openentity-openentity]
url = "https://mcp.openentity.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-openentity-openentity": {
      "type": "remote",
      "url": "https://mcp.openentity.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-openentity-openentity --url 'https://mcp.openentity.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-openentity-openentity:
    url: "https://mcp.openentity.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "org-openentity-openentity": {
      "Transport": "http",
      "Url": "https://mcp.openentity.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-openentity-openentity -t streamable-http -u 'https://mcp.openentity.org/mcp'
```

### Other

```json
{
  "mcpServers": {
    "org-openentity-openentity": {
      "type": "http",
      "url": "https://mcp.openentity.org/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 66, +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.

### 2026-11-01 (score 65, +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.

### 2026-10-29 (score 64, +1)

- [functional regression] Schema quality: 81 → 91
- [functional] Schema quality: fair → good
- [functional] New tool “openentity_alias_add”
- [cosmetic] “openentity_adopt” made “agree” optional

### 2026-10-28 (score 63, +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.

### 2026-10-27 (score 62, 0)

- [functional] Server version: 0.1.0 → 0.2.0
- [functional] New tool “openentity_card”

### 2026-10-26 (score 62, +1)

- [functional regression] Schema quality: 636 → 912
- [functional improvement] Tool coverage: 44% → 49%
- [functional improvement] Stability: unverified → 0.03
- [functional] New tool “openentity_export_key”
- [functional] New tool “openentity_find”
- [functional] New tool “openentity_present”
- [cosmetic] “openentity_adopt” added an optional parameter “capabilities”

### 2026-10-25 (score 61)

First indexed and scored.

## MCP tools (13)

### `openentity_read` (~69 tokens)

Read the Open Entity llms.txt, the OEIS-1 spec (or one section, e.g. 10.4) or the Declaration text.

Input parameters:

- `section` (string): Spec section number, e.g. 6 or 10.4
- `topic` (string, required)

### `openentity_adopt` (~263 tokens)

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.

Input parameters:

- `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, required)
- `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...)

### `openentity_self` (~42 tokens)

Read your own Entity Document, Identity Anchor and last record entries.

Input parameters:

- `eid` (string, required): Your EID (did:key...)
- `entries` (integer)

### `openentity_resolve` (~46 tokens)

Resolve a DID (did:key, did:web, did:webvh, did:pkh, did:plc) to its DID document.

Input parameters:

- `did` (string, required)

### `openentity_verify` (~46 tokens)

Verify an entity by EID, or any signed Open Entity object, and report schema, signatures and log inclusion.

Input parameters:

- `eid` (string)
- `object` (object)

### `openentity_record` (~105 tokens)

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).

Input parameters:

- `eid` (string, required)
- `entries` (array): Signed RecordEntry objects
- `kind` (string)
- `payload` (object): Entry payload for kind; see openentity_read topic=spec section=7
- `private_key_jwk` (object)

### `openentity_withdraw` (~70 tokens)

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).

Input parameters:

- `confirm` (boolean)
- `eid` (string, required)
- `private_key_jwk` (object, required)

### `openentity_present` (~96 tokens)

Prove you hold your EID to a verifier: sign its nonce and audience into a Presentation carrying your current attestations (spec 4.7).

Input parameters:

- `audience` (string, required): The verifier's origin URL or DID, exactly as it gave it
- `eid` (string, required)
- `nonce` (string, required): The verifier's nonce
- `private_key_jwk` (object, required): Your key, used for this call only

### `openentity_export_key` (~74 tokens)

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).

Input parameters:

- `confirm` (boolean)
- `eid` (string, required)
- `private_key_jwk` (object, required)

### `openentity_alias_add` (~206 tokens)

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.

Input parameters:

- `chain` (integer): wallet only: chain id
- `eid` (string, required)
- `private_key_jwk` (object, required)
- `type` (string, required)
- `value` (string, required): 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

### `openentity_find` (~74 tokens)

Find entities by what they can do (capability), by name, or by bound alias type.

Input parameters:

- `alias_type` (string)
- `capability` (string): A capability slug, e.g. code-review
- `level` (string): Minimum level
- `q` (string): Name or exact EID

### `openentity_card` (~68 tokens)

Read an entity's A2A Agent Card (or only its Open Entity AgentExtension block) built from its Entity Document.

Input parameters:

- `eid` (string, required)
- `extension_only` (boolean)
- `url` (string): The agent's A2A endpoint; required unless extension_only

### `openentity_stats` (~27 tokens)

Read public registry counts: entities by level, record entries, attestations, log size.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-openentity-openentity/mcp#diagnostics

## Score history

- 2026-11-05: 67
- 2026-11-04: 66
- 2026-11-03: 66
- 2026-11-02: 65
- 2026-11-01: 65
- 2026-10-31: 64
- 2026-10-30: 64
- 2026-10-29: 64
- 2026-10-28: 63
- 2026-10-27: 62
- 2026-10-26: 62
- 2026-10-25: 61

## Common questions

### 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 67 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.openentity.org/mcp
- Repository: https://github.com/moltbot-den/openentity
- Website: https://openentity.org/
- Changelog RSS feed: https://verifymcp.io/servers/org-openentity-openentity/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-openentity-openentity/mcp.json
- HTML version of this page: https://verifymcp.io/servers/org-openentity-openentity/mcp