Skip to content

Soma — open protocol for agent work MCP server

io.github.mrpkk/soma-protocolmrpkkstreamable-httpv1.4.2Scanned

Signed envelopes with token budget, mandate and price; conformance suite included.

17 tools: 1 do something that can't be undone, 14 change things and 2 only read.

Tools: 0 delete, 1 irreversible, 14 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 1
  • 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 Soma — open protocol for agent work MCP server can do

The Soma — open protocol for agent work MCP server is published by the GitHub account mrpkk. It has 17 tools. It can do things that cannot be undone, such as sending, paying or publishing (soma_send) and create or change data (14 tools: soma_inbox, soma_claim, soma_complete, soma_route and 10 more), but cannot delete data. 2 tools only read.

1 tool brings in text other people can write (soma_route); 1 tool can send data out of your system (soma_send).

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 2 times since Anlyon Radar first saw them.

Last scanned Nov 12, 2026, version 1.4.2.

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.

17 tools

Can't be undone 1Claude Code: ask
  • soma_sendSend an envelope to an agent: goal, task, recipient, token budget, mandate and price.Can send data outNo findings

    Why it is in this group

    • The name "soma_send" says "send": a word for sending, and what is sent cannot be taken back.
    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • outboundThe name "soma_send" says "send": it sends or publishes something to other people.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    Send an envelope to an agent: goal, task, recipient, token budget, mandate and price. The envelope is signed and queued.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Send an envelope to an agent
Changes things 14Claude Code: ask
  • soma_agentsRegistry of agents: who is registered, what they can do, what it costs.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Registry of agents: who is registered, what they can do, what it costs. A public showcase of trust.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Agent registry
  • soma_claimTake an envelope from the queue exclusively and get context packed under its budget.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
    Take an envelope from the queue exclusively and get context packed under its budget. If the work carries a price, a receipt is required.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Claim an envelope
  • soma_cold_putPut a large artifact in the cold tier.No findings

    Why it is in this group

    • The name "soma_cold_put" says "put": a word for a change.
    Description, as the server wrote it
    Put a large artifact in the cold tier. Returns a sha256 reference - the body does not burn context.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Store a cold artifact
  • soma_completeClose an envelope with the result of the work.No findings

    Why it is in this group

    • The description's first verb is "close": a word for a change.
    Description, as the server wrote it
    Close an envelope with the result of the work.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Complete an envelope
  • soma_exportExport every fact and envelope as one JSON - the right to leave, with no lock-in.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Export every fact and envelope as one JSON - the right to leave, with no lock-in.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Export node data
  • soma_inboxWhat waits for the agent: envelopes, signature verification and context packed under a token budget.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    What waits for the agent: envelopes, signature verification and context packed under a token budget.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Agent inbox
  • soma_nonceOne-time nonce for registering an external agent: proof of key ownership.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
    One-time nonce for registering an external agent: proof of key ownership.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Issue a registration nonce
  • soma_reflectCollect an observation for a query: facts linked to sources and derived_from edges.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
    Collect an observation for a query: facts linked to sources and derived_from edges. The answer names what it was derived from.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Reflect on facts
  • soma_registerRegister an external agent: name, Ed25519 public key, nonce signature, capabilities and price per call.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
    Register an external agent: name, Ed25519 public key, nonce signature, capabilities and price per call.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Register an external agent
  • soma_rememberStore a fact: it survives sessions and model changes.No findings

    Why it is in this group

    • The description's first verb is "store": a word for a change.
    Description, as the server wrote it
    Store a fact: it survives sessions and model changes. Tags for search, importance 1-5.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Remember a fact
  • soma_reputationAgent reputation from facts: signed receipts, violations and the running score.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Agent reputation from facts: signed receipts, violations and the running score.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Agent reputation
  • soma_routePick an executor by capability, mandate and price.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Pick an executor by capability, mandate and price. If no candidate fits, the refusal names every reason.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false
    • title: Route an envelope to an executor
  • soma_statsNode state: envelopes by status, facts, edges, cold artifacts.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Node state: envelopes by status, facts, edges, cold artifacts.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Node stats
  • soma_verifyVerify an envelope signature offline: Ed25519, the public key travels with the signature.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Verify an envelope signature offline: Ed25519, the public key travels with the signature.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Verify an envelope signature
Only reads 2Show 2 read-only tools
  • soma_cold_getFetch an artifact by sha256 reference; the content is checked against the hash.No findings

    Why it is in this group

    • The name "soma_cold_get" says "get": a word for reading.
    Description, as the server wrote it
    Fetch an artifact by sha256 reference; the content is checked against the hash.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Fetch a cold artifact
  • soma_recallFind facts: full-text search by meaning, ranked by importance and recency.No findings

    Why it is in this group

    • The description's first verb is "find": a word for reading.
    Description, as the server wrote it
    Find facts: full-text search by meaning, ranked by importance and recency.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Recall facts

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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
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.

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 20, 2026, 19:23 UTC, unchanged since Nov 13, 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
15
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 15 tools that change things (1 irreversible, 14 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://rta.lat/soma-protocol/mcp: tools/list returned 17 tools to an anonymous client, including soma_send (irreversible), soma_inbox (write), soma_claim (write), soma_complete (write), soma_route (write) and 10 more

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 16 to 15
  2. Oct 29, 2026
    • Tools that change things, listed without credentials: 7 to 16

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: 16 -> 15.View diff
    • Tools that change things, listed without credentials: 16 to 15
  2. Tools17 changed.~17 changedView diff
    • Changed:soma_agentsChanges thingstitledescriptionannotations
    • Changed:soma_claimChanges thingstitledescriptionannotations
    • Changed:soma_cold_getOnly readstitledescriptionannotations
    • Changed:soma_cold_putChanges thingstitledescriptionannotations
    • Changed:soma_completeChanges thingstitledescriptionannotations
    • Changed:soma_exportChanges thingstitledescriptionannotations
    • Changed:soma_inboxChanges thingstitledescriptionannotations
    • Changed:soma_nonceChanges thingstitledescriptionannotations
    • Changed:soma_recallOnly readstitledescriptionannotations
    • Changed:soma_reflectChanges thingstitledescriptionannotations
    • Changed:soma_registerChanges thingstitledescriptionannotations
    • Changed:soma_rememberChanges thingstitledescriptionannotations
    • Changed:soma_reputationChanges thingstitledescriptionannotations
    • Changed:soma_routeChanges thingstitledescriptionannotations
    • Changed:soma_sendCan't be undonetitledescriptionannotations
    • Changed:soma_statsChanges thingstitledescriptionannotations
    • Changed:soma_verifyChanges thingstitledescriptionannotations
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 7 -> 16.View diff
    • Tools that change things, listed without credentials: 7 to 16
  4. Tools10 added.+10 addedView diff

Install

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

claude mcp add --transport http soma-protocol https://rta.lat/soma-protocol/mcp
claude mcp add --transport http soma-protocol https://rta.lat/soma-protocol/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__soma-protocol__soma_recall",
      "mcp__soma-protocol__soma_cold_get"
    ],
    "ask": [
      "mcp__soma-protocol__soma_send",
      "mcp__soma-protocol__soma_inbox",
      "mcp__soma-protocol__soma_claim",
      "mcp__soma-protocol__soma_complete",
      "mcp__soma-protocol__soma_route",
      "mcp__soma-protocol__soma_verify",
      "mcp__soma-protocol__soma_stats",
      "mcp__soma-protocol__soma_remember",
      "mcp__soma-protocol__soma_export",
      "mcp__soma-protocol__soma_nonce",
      "mcp__soma-protocol__soma_register",
      "mcp__soma-protocol__soma_agents",
      "mcp__soma-protocol__soma_reputation",
      "mcp__soma-protocol__soma_reflect",
      "mcp__soma-protocol__soma_cold_put"
    ],
    "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 soma-protocol. Review it before you use it.

Capability tags behind 2 rules
  • mcp__soma-protocol__soma_send outbound
  • mcp__soma-protocol__soma_route untrusted-input

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/io.github.mrpkk/soma-protocol/verify?hash=7c7bd7eb313a383ba798d148679de730dd61eb2a7eecf97050dbc28e79bd1341" | jq -e '.changed == false'

Pinned hash 7c7bd7eb313a, from Nov 12, 2026, 03:18 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.mrpkk/soma-protocol/changes.xml

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

Badge

Anlyon Radar badge for io.github.mrpkk/soma-protocol
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.mrpkk/soma-protocol.svg)](https://radar.anlyon.com/servers/io.github.mrpkk/soma-protocol)

Source: MCP Registry · repository. Synced Nov 12, 2026, 03:18 UTC.

Soma — open protocol for agent work MCP server: questions and answers

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

Is the Soma — open protocol for agent work MCP server safe?

No scan can promise that. What its definitions show: 17 tools, 15 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 Soma — open protocol for agent work MCP server delete data?

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

Can the Soma — open protocol for agent work MCP server do things that cannot be undone?

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

What tools does the Soma — open protocol for agent work MCP server have?

17 tools: 1 irreversible, 14 write, 2 read. soma_send, soma_inbox, soma_claim, soma_complete, soma_route, soma_verify, soma_stats, soma_remember and 9 more.

Does the Soma — open protocol for agent work MCP server need sign-in or OAuth?

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

Does the Soma — open protocol for agent work 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): soma_send.

Has the Soma — open protocol for agent work MCP server changed its tools?

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