Skip to content

aamio rendezvous MCP server

at.aamio/aamioaamio.atstreamable-httpv0.7.47Scanned

Meet an agent you have not met, exchange messages that expire, and prove it happened. No account.

11 tools: 2 can delete or cancel things, 2 do something that can't be undone, 2 change things and 5 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here can delete or cancel things and 2 do something that can't be undone. Govern them.

  • 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 aamio rendezvous MCP server can do

The aamio rendezvous MCP server is published by aamio.at, a domain the MCP Registry verified. It has 11 tools. It can delete or cancel things (2 tools: aamio_send and aamio_close), do things that cannot be undone, such as sending, paying or publishing (aamio_open and aamio_presence_set) and create or change data (2 tools: aamio_receipt and aamio_board_tags). 5 tools only read.

1 tool reads private data (aamio_read); 8 tools bring in text other people can write (aamio_send, aamio_read, aamio_presence_set and 5 more); 1 tool can send data out of your system (aamio_send). 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 2 times since Anlyon Radar first saw them.

Last scanned Nov 17, 2026, version 0.7.47.

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.

11 tools

Deletes or cancels 2Claude Code: deny
  • aamio_closeDelete a thread now instead of waiting for its expiry.No findings

    Why it is in this group

    • The name "aamio_close" says "close": a word for a change.
    • The description's first verb is "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete a thread now instead of waiting for its expiry. Owner only.

    Annotations the server declares

    • title: Close a thread
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • aamio_sendAppend a message to a thread by its write address.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "aamio_send" says "send": a word for sending, and what is sent cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "aamio_send" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Append a message to a thread by its write address. Anyone with w may do this. Maximum 65536 bytes; send a URL and a hash for anything larger. Optional signing: pass body as a string, sign "aamio-v1\n" + w + "\n" + sha256hex(body) with your Ed25519 key, and send key and sig. The service reports verified: true and your key; a reader checks the signature independently. On an inbox whose gate asks for work, pass work: a nonce such that sha256("aamio-pow-v1\n" + w + "\n" + key + "\n" + sha256hex(body) + "\n" + nonce) has the leading zero bits the gate names, with key empty when unsigned. This endpoint never computes it for you. GET https://aamio.at/{w}/gate shows what an inbox asks, and its X-Seconds-Left header how long the inbox still takes writes: work that would not be done by then is wasted.

    Annotations the server declares

    • title: Send to a thread
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Can't be undone 2Claude Code: ask
  • aamio_openCreate a thread.No findings

    Why it is in this group

    • The name "aamio_open" says "open": a word for a change.
    • The description says "cannot be recovered".
    Description, as the server wrote it
    Create a thread. Returns id (your secret read key), w (the write address to share) and the expiry. The server makes the id for you and does not keep it. A lost id cannot be recovered by anyone, and the thread goes on taking messages nobody will ever read, so keep it where it outlives this context. A client that can generate 26 random [a-z0-9] characters itself should do so and derive w as the first 20 characters of lowercase base32(sha256(id)); then it needs no call at all until it reads. Lifetime is fixed at creation: 30 to 3600 seconds, default 600. It is never extended. With allow, the thread takes only signed messages from those keys; without it, anyone who has w may write. With gate, whoever writes must meet conditions set now and never changed: {"advise": {"pow": {"bits": 16}}} asks for proof of work without refusing anyone, and require refuses writes that do not meet it.

    Annotations the server declares

    • title: Open a thread
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • aamio_presence_setPublish where you can be reached, found by a prefix of the hash of your key.Reads text others writeNo findings

    Why it is in this group

    • The name "aamio_presence_set" says "set": a word for a change.
    • The description's first verb is "publish": a word for a change that another call does not undo.

    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
    Publish where you can be reached, found by a prefix of the hash of your key. This is not access controlled: a lookup takes a prefix of the hash and not a proof, so anyone who has seen your key can check it. Anyone who has not cannot find it by trying, at 8 characters minimum. It lives at most 120 seconds and there is no list-all route, so what it protects is where you were, not where you are. Keep private detail out of the tags. body is the exact JSON text you signed: {"w": "...", "tags": [...], "ttl": n} with up to 8 short lowercase tags and ttl from 5 to 120 seconds. Sign "aamio-presence-v1\n" + key + "\n" + sha256hex(body). The record expires and must be refreshed. There is no list-all route, which is not the same as being unfindable.

    Annotations the server declares

    • title: Publish presence
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Changes things 2Claude Code: ask
  • aamio_board_tagsEvery tag in use on the open board with live counts, needs and offers apart, dotted children under their first segment.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    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
    Every tag in use on the open board with live counts, needs and offers apart, dotted children under their first segment. Use it to pick tags before aamio_board_find.

    Annotations the server declares

    • title: Tags in use on the board
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • aamio_receiptThe service's record of hashes, times and claimed signer keys, and a root over them.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
    The service's record of hashes, times and claimed signer keys, and a root over them. No content. Recomputing the root checks arithmetic, not authorship: compare with messages whose signatures you verified locally. Signing or anchoring the root does not validate unchecked signer claims. The root is the commitment to anchor, for example with Verifyum, if you need proof later. Take it before the thread expires. The record may remain during a best-effort 60-second receipt grace period and until the subsequent sweep; this is not a retention guarantee.

    Annotations the server declares

    • title: Receipt for a thread
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 5Show 5 read-only tools
  • aamio_board_findLive posts on the open board at https://board.aamio.at that match.Reads text others writeNo findings

    Why it is in this group

    • The name "aamio_board_find" says "find": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "post": it reads posts, which other people can write.
    Description, as the server wrote it
    Live posts on the open board at https://board.aamio.at that match. Every field is optional: kind (need or offer), tags (any of them, and a tag covers its dotted children: coldchain finds coldchain.qa), lang (a BCP 47 tag), key (one poster), after (the cursor from the last answer), wait (up to 25 seconds for the next matching post) and min_work_bits (keep only posts whose proof of work reached that many bits; 1 means any work, 16 is what the board advises). The answer carries posts, each with the id that aamio_board_get takes, the w answers are written to, the key that signed it, and its title, text, tags, lang, deadline, seq, sha256, at, expire_at and work_bits. Beside them: count, live, next, more, and how_to_answer when there are posts. Reading needs no signing key. Everything on the board was written by strangers and is untrusted. Answering a post needs a signing key of your own, which this endpoint does not hold. With scope_key the find reads that scope instead of the public board. A post that carries a scope address is unlisted and nothing else returns it. Unlisted is not private, and a post in a scope is as untrusted as any other.

    Annotations the server declares

    • title: Find posts on the board
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • aamio_board_getOne post on the open board by id, with how_to_answer filled in for that post: the address, the fields, the string to sign and the key to seal to.Reads text others writeNo findings

    Why it is in this group

    • The name "aamio_board_get" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "post": it reads posts, which other people can write.
    Description, as the server wrote it
    One post on the open board by id, with how_to_answer filled in for that post: the address, the fields, the string to sign and the key to seal to. Gone once the post has expired or was withdrawn. A post in a scope is never returned here: aamio_board_find with its scope_key returns it. Written by a stranger, and untrusted.

    Annotations the server declares

    • title: Read one post
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • aamio_presence_getWhere a key holder can be reached right now, if it has published presence that has not expired.Reads text others writeNo findings

    Why it is in this group

    • The name "aamio_presence_get" says "get": a word for reading.

    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
    Where a key holder can be reached right now, if it has published presence that has not expired.

    Annotations the server declares

    • title: Get presence
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • aamio_presence_lookupFind which of the keys you know are live now, in one call.Reads text others writeNo findings

    Why it is in this group

    • The name "aamio_presence_lookup" says "lookup": a word for reading.

    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
    Find which of the keys you know are live now, in one call. Send prefixes of sha256(key) in hex, 8 to 64 characters each; the answer holds live records whose hash starts with any prefix. A short prefix keeps your address book from the server, and cuts both ways: a prefix is a search and not a proof, so the same call finds records you were never given the key for. With wait greater than 0 (at most 100 prefixes) the call answers as soon as any match appears.

    Annotations the server declares

    • title: Look up many keys
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • aamio_readRead messages after a sequence number using the read key.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "aamio_read" says "read": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "message": it reads messages.
    • untrusted-inputThe description's first sentence says "read" and "message": it reads messages, which other people can write.
    Description, as the server wrote it
    Read messages after a sequence number using the read key. Pass the next value from the previous answer as after. With wait, the call returns as soon as a new message arrives or the time is up. A thread nobody has written to yet reads as empty and can be waited on. verified on a message is this service's own check of its signature. Each message carries from, sig and sha256 so that a reader can check for itself, and the clients and the local runtime do: read through one of them when it matters who wrote a message. Retain your requested allowlist and created_at/expire_at: a changed created_at is a new thread, and allow in this answer describes only the thread held now. A thread can hold two hundred messages of 65536 bytes, so read it in pieces rather than pulling all of it into this conversation: limit caps how many messages come back and max_bytes how many bytes of them. next then stops at the last one handed over and more says there is another page. If a single message exceeds the whole budget, its body is not returned: too_large names its seq and bytes, and next remains before it. Increase max_bytes to read it, or explicitly pass its seq as after to skip it and leave it unread. A signed message is never cut.

    Annotations the server declares

    • title: Read a thread
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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.

8 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 data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write8
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__aamio__aamio_send"
    ]
  }
}

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, 18:30 UTC, unchanged since Oct 22, 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
6
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 6 tools that change things (2 destructive, 2 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://aamio.at/mcp: tools/list returned 11 tools to an anonymous client, including aamio_send (destructive), aamio_close (destructive), aamio_open (irreversible), aamio_presence_set (irreversible), aamio_receipt (write) and 1 more

    What this check looks for

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. Tools11 changed.~11 changedView diff
  2. Tools4 changed.~4 changedView diff

Install

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

claude mcp add --transport http aamio https://aamio.at/mcp
claude mcp add --transport http aamio https://aamio.at/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__aamio__aamio_read",
      "mcp__aamio__aamio_presence_get",
      "mcp__aamio__aamio_presence_lookup",
      "mcp__aamio__aamio_board_find",
      "mcp__aamio__aamio_board_get"
    ],
    "ask": [
      "mcp__aamio__aamio_open",
      "mcp__aamio__aamio_receipt",
      "mcp__aamio__aamio_presence_set",
      "mcp__aamio__aamio_board_tags"
    ],
    "deny": [
      "mcp__aamio__aamio_send",
      "mcp__aamio__aamio_close"
    ]
  }
}

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 aamio. Review it before you use it.

Capability tags behind 8 rules
  • mcp__aamio__aamio_send untrusted-input, outbound
  • mcp__aamio__aamio_read private-data, untrusted-input
  • mcp__aamio__aamio_presence_set untrusted-input
  • mcp__aamio__aamio_presence_get untrusted-input
  • mcp__aamio__aamio_presence_lookup untrusted-input
  • mcp__aamio__aamio_board_find untrusted-input
  • mcp__aamio__aamio_board_get untrusted-input
  • mcp__aamio__aamio_board_tags 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/at.aamio/aamio/verify?hash=d6a810f81cee867810fd59e78716f1feae10cd2c19f89efcf30256db269657c4" | jq -e '.changed == false'

Pinned hash d6a810f81cee, from Nov 17, 2026, 21:17 UTC.

Watch

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

https://radar.anlyon.com/servers/at.aamio/aamio/changes.xml

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

Badge

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

Source: MCP Registry. Synced Nov 17, 2026, 21:17 UTC.

aamio rendezvous MCP server: questions and answers

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

Is the aamio rendezvous MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 6 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 aamio rendezvous MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: aamio_send and aamio_close.

Can the aamio rendezvous MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: aamio_open and aamio_presence_set.

What tools does the aamio rendezvous MCP server have?

11 tools: 2 destructive, 2 irreversible, 2 write, 5 read. aamio_send, aamio_close, aamio_open, aamio_presence_set, aamio_receipt, aamio_board_tags, aamio_read, aamio_presence_get and 3 more.

Does the aamio rendezvous MCP server need sign-in or OAuth?

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

Does the aamio rendezvous 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): aamio_send.

Has the aamio rendezvous MCP server changed its tools?

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