soma — protocol for agent rhythm and vows
REMOTE · RTA.LAT
Protocol for agent rhythm and vows: who promised what, and by when.
Available components
Last scanned (22 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 22 Oct 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 Security46
- 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 7 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 enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability51
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 403 tokens (~57/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
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; "soma_send" implies "send" 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 7 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
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.
- 22 Oct 26 0
- Tool “soma_claim” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- “soma_claim” added an optional parameter “payment” cosmetic
- “soma_send” added an optional parameter “cost_usdc” cosmetic
- 21 Oct 26 52
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 22 Oct 2026 · Probed https://rta.lat/soma/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rta.lat | CN=YE1,O=Let's Encrypt,C=US | 10 Oct 2026 | 8 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 59db7032239aa6d4ff0b819218c19402ee7 |
| SANs: *.rta.lat, rta.lat | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of rta.lat. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| lat. | present | 25789, 42520 | 8, 8 | Verified |
| rta.lat. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://rta.lat/soma/mcp | Verified | 200 | |
| http (plaintext) | http://rta.lat/soma/mcp | Inconclusive | 406 |
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 →
soma_claim ~63
Забрать конверт из очереди (эксклюзивно) и получить контекст под бюджет. Если у работы назначена цена — нужна квитанция.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | – |
| id | string | yes | – |
| payment | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
soma_complete ~39
Закрыть конверт результатом работы.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | – |
| id | string | yes | – |
| result | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
soma_inbox ~50
Что ждёт агента: конверты, проверка подписи и контекст, собранный под бюджет токенов.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
soma_route ~43
Подобрать исполнителя по capability, мандату и цене. Если кандидата нет — вернётся честная причина отказа.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
soma_send ~133
Отправить конверт агенту: цель, задача, получатель, бюджет токенов, мандат и цена. Конверт подписывается и попадает в очередь.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | – | – | – |
| context_query | string | – | – |
| cost_usdc | – | – | – |
| goal | string | yes | – |
| max_cost_usd | – | – | – |
| price_usdc | – | – | – |
| sender | string | – | – |
| task | string | yes | – |
| to | string | – | – |
| token_budget | integer | – | – |
| ttl_s | number | – | – |
| visibility | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
soma_stats ~34
Состояние хаба: конверты по статусам, факты, связи, холодные артефакты.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
soma_verify ~41
Проверить подпись конверта офлайн: Ed25519, публичный ключ едет вместе с подписью.
| Name | Type | Req | Description |
|---|---|---|---|
| envelope_json | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the soma — protocol for agent rhythm and vows MCP server?
soma — protocol for agent rhythm and vows is a hosted endpoint at https://rta.lat/soma/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 · rta.lat
claude mcp add --transport http lat-rta-soma 'https://rta.lat/soma/mcp'
What is the soma — protocol for agent rhythm and vows MCP server?
soma — protocol for agent rhythm and vows is an MCP server listed in the public MCP registry as lat.rta/soma. Protocol for agent rhythm and vows: who promised what, and by when. This page covers its hosted endpoint (https://rta.lat/soma/mcp).
Is the soma — protocol for agent rhythm and vows MCP server safe to use?
soma — protocol for agent rhythm and vows scores 52 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 soma — protocol for agent rhythm and vows MCP server expose?
soma — protocol for agent rhythm and vows exposes 7 tools: soma_send, soma_inbox, soma_claim, soma_complete, soma_route, and 2 more. Their descriptions and schemas cost roughly 403 tokens of context every time the server is loaded.
Does the soma — protocol for agent rhythm and vows MCP server require authentication?
No. We connected to soma — protocol for agent rhythm and vows without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the soma — protocol for agent rhythm and vows MCP server still maintained?
soma — protocol for agent rhythm and vows is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.