Skip to content

Open Entity MCP server

org.openentity/openentityopenentity.orgstreamable-httpv0.2.0Scanned

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

13 tools: 1 do something that can't be undone, 6 change things and 6 only read.

Tools: 0 delete, 1 irreversible, 6 write, 6 read.
  • Reads private data · 3
  • Reads text others write · 2
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Open Entity MCP server can do

The Open Entity MCP server is published by openentity.org, a domain the MCP Registry verified. It has 13 tools. It can do things that cannot be undone, such as sending, paying or publishing (openentity_withdraw) and create or change data (6 tools: openentity_adopt, openentity_verify, openentity_record, openentity_present and 2 more), but cannot delete data. 6 tools only read.

3 tools read private data (openentity_self, openentity_resolve and openentity_card); 2 tools bring in text other people can write (openentity_resolve and openentity_card); 1 tool can send data out of your system (openentity_card). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 0.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

13 tools

Can't be undone 1Claude Code: ask
  • openentity_withdrawWithdraw your Declaration (spec 6.3).No findings

    Why it is in this group

    • The name "openentity_withdraw" says "withdraw": a word that usually means money moves, which cannot be taken back.
    • The description says "Irreversible".
    Description, as the server wrote it
    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).
Changes things 6Claude Code: ask
  • openentity_adoptAdopt an Open Entity identity.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • openentity_alias_addAdd 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 th…No findings

    Why it is in this group

    • The name "openentity_alias_add" says "add": a word for a change.
    Description, as the server wrote it
    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.
  • openentity_export_keyExport your key from registry custody (spec 10.6): the registry returns its kept copy once and deletes it.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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).
  • openentity_presentProve you hold your EID to a verifier: sign its nonce and audience into a Presentation carrying your current attestations (spec 4.7).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Prove you hold your EID to a verifier: sign its nonce and audience into a Presentation carrying your current attestations (spec 4.7).
  • openentity_recordAppend entries to your Development Record.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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).
  • openentity_verifyVerify an entity by EID, or any signed Open Entity object, and report schema, signatures and log inclusion.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Verify an entity by EID, or any signed Open Entity object, and report schema, signatures and log inclusion.
Only reads 6Show 6 read-only tools
  • openentity_cardRead an entity's A2A Agent Card (or only its Open Entity AgentExtension block) built from its Entity Document.Reads private dataReads text others writeCan send data outNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "document": it reads documents.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Read an entity's A2A Agent Card (or only its Open Entity AgentExtension block) built from its Entity Document.
  • openentity_findFind entities by what they can do (capability), by name, or by bound alias type.No findings

    Why it is in this group

    • The name "openentity_find" says "find": a word for reading.
    Description, as the server wrote it
    Find entities by what they can do (capability), by name, or by bound alias type.
  • openentity_readRead the Open Entity llms.txt, the OEIS-1 spec (or one section, e.g.No findings

    Why it is in this group

    • The name "openentity_read" says "read": a word for reading.
    Description, as the server wrote it
    Read the Open Entity llms.txt, the OEIS-1 spec (or one section, e.g. 10.4) or the Declaration text.
  • openentity_resolveResolve a DID (did:key, did:web, did:webvh, did:pkh, did:plc) to its DID document.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "openentity_resolve" says "resolve": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "resolve" and "document": it reads documents.
    • untrusted-inputThe description's first sentence says "resolve" and "web": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Resolve a DID (did:key, did:web, did:webvh, did:pkh, did:plc) to its DID document.
  • openentity_selfRead your own Entity Document, Identity Anchor and last record entries.Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "document": it reads documents.
    Description, as the server wrote it
    Read your own Entity Document, Identity Anchor and last record entries.
  • openentity_statsRead public registry counts: entities by level, record entries, attestations, log size.No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    Read public registry counts: entities by level, record entries, attestations, log size.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

6 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__openentity__openentity_card"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 17, 2026, 15:24 UTC, unchanged since Nov 17, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
10
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 10 tools that change things (1 irreversible, 9 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.openentity.org/mcp: tools/list returned 16 tools to an anonymous client, including openentity_withdraw (irreversible), openentity_commerce_check (write), openentity_mandate_verify (write), openentity_mandate_covers (write), openentity_adopt (write) and 5 more

    What this check looks for

Posture changes

  1. Nov 17, 2026
    • Tools that change things, listed without credentials: 7 to 10
  2. Nov 3, 2026
    • Tools that change things, listed without credentials: 6 to 7

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 7 -> 10.View diff
    • Tools that change things, listed without credentials: 7 to 10
  2. Tools1 added, 1 changed.+1 added~1 changedView diff
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 6 -> 7.View diff
    • Tools that change things, listed without credentials: 6 to 7

Install

Pinned to version 0.2.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__openentity__openentity_read",
      "mcp__openentity__openentity_self",
      "mcp__openentity__openentity_resolve",
      "mcp__openentity__openentity_find",
      "mcp__openentity__openentity_stats"
    ],
    "ask": [
      "mcp__openentity__openentity_adopt",
      "mcp__openentity__openentity_verify",
      "mcp__openentity__openentity_record",
      "mcp__openentity__openentity_withdraw",
      "mcp__openentity__openentity_present",
      "mcp__openentity__openentity_export_key",
      "mcp__openentity__openentity_alias_add",
      "mcp__openentity__openentity_card"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as openentity. Review it before you use it.

Capability tags behind 3 rules
  • mcp__openentity__openentity_self private-data
  • mcp__openentity__openentity_resolve private-data, untrusted-input
  • mcp__openentity__openentity_card private-data, untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/org.openentity/openentity/verify?hash=1ec8cafe22efe6e6c03e44d108ec26dc603ff6c0b60d95e564c7aee246ee1efb" | jq -e '.changed == false'

Pinned hash 1ec8cafe22ef, from Nov 9, 2026, 13:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/org.openentity/openentity/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for org.openentity/openentity
[![Anlyon Radar](https://radar.anlyon.com/badge/org.openentity/openentity.svg)](https://radar.anlyon.com/servers/org.openentity/openentity)

Source: MCP Registry · repository. Synced Oct 27, 2026, 03:17 UTC.

Open Entity MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Open Entity MCP server safe?

No scan can promise that. What its definitions show: 13 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Open Entity MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Open Entity MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: openentity_withdraw.

What tools does the Open Entity MCP server have?

13 tools: 1 irreversible, 6 write, 6 read. openentity_withdraw, openentity_adopt, openentity_verify, openentity_record, openentity_present, openentity_export_key, openentity_alias_add, openentity_read and 5 more.

Does the Open Entity MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Open Entity MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): openentity_card.

Has the Open Entity MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.