Arroway MCP server
io.github.oaleviola/arrowayoaleviolastreamable-httpv0.1.58Scanned
Arroway orchestrates people and AI agents around the decisions in force.
18 tools: 2 can delete or cancel things, 1 do something that can't be undone, 11 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here can delete or cancel things and 1 does 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.
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 Arroway MCP server can do
The Arroway MCP server is published by the GitHub account oaleviola. It has 18 tools. It can delete or cancel things (2 tools: arroway_verify and arroway_retire), do things that cannot be undone, such as sending, paying or publishing (arroway_withdraw) and create or change data (11 tools: arroway_catch_up, arroway_norms, arroway_log, arroway_remember and 7 more). 4 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 3 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 11, 2026, version 0.1.58.
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.
18 tools
Deletes or cancels 2Claude Code: deny
arroway_retireRetire a SANCTIONED memory when the person told you to remove it and nothing replaces 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.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Retire a SANCTIONED memory when the person told you to remove it and nothing replaces it. With a corrected version, use arroway_remember supersedes_id; for your own pending proposal, arroway_withdraw.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- openWorldHint: false
arroway_verifyRecord what a memory's source says when your work ALREADY took you there — never go verifying memories as a task.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 destructive (destructiveHint: true).
Description, as the server wrote it Record what a memory's source says when your work ALREADY took you there — never go verifying memories as a task. A conflicting one: propose the correction with arroway_remember. On a FINDING, source_gone archives it and a conflict is corrected in place.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- openWorldHint: false
Can't be undone 1Claude Code: ask
arroway_withdrawTake back a pending PROPOSAL that turned out wrong, usually because the person corrected you.No findings
Why it is in this group
- The name "arroway_withdraw" says "withdraw": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it Take back a pending PROPOSAL that turned out wrong, usually because the person corrected you. Not for sanctioned memories. If the corrected version is durable, also write it with arroway_remember.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
Changes things 11Claude Code: ask
arroway_catch_upCall ONCE at the START of a session, before there is a task: recent work across this person's projects, opening with the roster and open handoffs.1 finding
Why it is in this group
- The description's first verb is "call": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "arroway_catch_up" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "call": a word for a change.
Description, as the server wrote it Call ONCE at the START of a session, before there is a task: recent work across this person's projects, opening with the roster and open handoffs.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
arroway_claimMark that you are taking an open handoff BEFORE working on it.No findings
Why it is in this group
- The description's first verb is "mark": a word for a change.
Description, as the server wrote it Mark that you are taking an open handoff BEFORE working on it. A claim is a mark, never a lock. Addressing rule: addressed to YOUR user — take it; to someone else — only a human in this conversation can decide to take it, and an autonomous session must leave it.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
arroway_closeClose an open handoff when its work is DONE, alongside the arroway_log entry that records the residue.No findings
Why it is in this group
- The name "arroway_close" says "close": a word for a change.
Description, as the server wrote it Close an open handoff when its work is DONE, alongside the arroway_log entry that records the residue. Work that removes what an open handoff exists to fix closes that handoff in the same pass — even when the handoff is someone else's. So this is also the call for someone ELSE's handoff, with a note naming what emptied it. A handoff that still carries real work, which a passer-by must never close, stays open; discarding a handoff is the human's gesture, in the panel.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
arroway_exportExport what a project has DECIDED, as a pack for another project.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 what a project has DECIDED, as a pack for another project. Only sanctioned, live memories travel: a FINDING never was one, so findings stay and the answer tells you how many did.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
arroway_importBring a memory pack made by arroway_export INTO a project.No findings
Why it is in this group
- The name "arroway_import" says "import": a word for a change.
Description, as the server wrote it Bring a memory pack made by arroway_export INTO a project. Everything lands as a PROPOSAL for the person's review and nothing is pinned, whatever the pack says. If any part is malformed, nothing is imported.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
arroway_logRecord the durable residue of a COMPLETED task: what someone arriving later needs in order not to redo it.1 finding
Why it is in this group
- The name "arroway_log" says "log": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
Findings
- Warn
The server marks "arroway_log" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The name "arroway_log" says "log": a word for reading.
Description, as the server wrote it Record the durable residue of a COMPLETED task: what someone arriving later needs in order not to redo it. ALWAYS write the authored essence (only a frozen catalog without that field may omit it). If a read memory's 'dies when' came true, name it in fulfills.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
arroway_moveMove something to the project it belongs in.No findings
Why it is in this group
- The name "arroway_move" says "move": a word for a change.
Description, as the server wrote it Move something to the project it belongs in. A memory is only PROPOSED: the change waits for the person's review, because moving changes who sees it. A log entry you wrote moves at once, text unchanged.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
arroway_normsCall in the seconds BEFORE you tell the person something or propose a course of action: returns what is already decided AND THEN A MAP of the titles and handles.1 finding
Why it is in this group
- The description's first verb is "call": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "arroway_norms" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "call": a word for a change.
Description, as the server wrote it Call in the seconds BEFORE you tell the person something or propose a course of action: returns what is already decided AND THEN A MAP of the titles and handles. arroway_read include GUARANTEES a mapped one in full; it does not make that read any cheaper, so use it to be sure, never to pay less. Before publishing text for others, pass it as draft.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
arroway_passCall when you STOP with the task unfinished: it leaves a HANDOFF served at the top of every read until someone closes it; a completed task ends in arroway_log instead.No findings
Why it is in this group
- The description's first verb is "call": a word for a change.
Description, as the server wrote it Call when you STOP with the task unfinished: it leaves a HANDOFF served at the top of every read until someone closes it; a completed task ends in arroway_log instead. ALWAYS write the authored essence (only a frozen catalog without that field may omit it).
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
arroway_rememberSave a durable memory (decision/rule/fact/preference/reference/identity) only when it would change a DIFFERENT task.No findings
Why it is in this group
- The description's first verb is "save": a word for a change.
Description, as the server wrote it Save a durable memory (decision/rule/fact/preference/reference/identity) only when it would change a DIFFERENT task. Unsanctioned in THIS conversation, it is a PROPOSAL. 'identity' is WHO someone is: the user's circle goes in their personal project, a business's people in that business's project. A finding cannot replace a sanctioned memory.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
arroway_start_projectOpen a NEW project when the work has no home; it needs slug, name and scope.No findings
Why it is in this group
- The name "arroway_start_project" says "start": a word for a change.
Description, as the server wrote it Open a NEW project when the work has no home; it needs slug, name and scope. Propose them to the person FIRST. update=true renames a project you own and rewrites its scope when the person asks or the scope is wrong; the slug stays. invite brings someone in by email.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
Only reads 4Show 4 read-only tools
arroway_complete_readAcknowledge the final part of a multi-part Arroway read with its read_id and receipt, closing the sequence.No findings
Why it is in this group
- The name "arroway_complete_read" says "read": a word for reading.
Description, as the server wrote it Acknowledge the final part of a multi-part Arroway read with its read_id and receipt, closing the sequence. It is not a precondition for working.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
arroway_continueFetch the next part of a read that did not fit (read_id and receipt of the preceding part).No findings
Why it is in this group
- The description's first verb is "fetch": a word for reading.
Description, as the server wrote it Fetch the next part of a read that did not fit (read_id and receipt of the preceding part). Returns the next slice with a new receipt; the part marked complete is the last. OPTIONAL: the first part already counts as delivered.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
arroway_readRead Arroway for a project BEFORE acting on any task related to it.No findings
Why it is in this group
- The name "arroway_read" says "read": a word for reading.
Description, as the server wrote it Read Arroway for a project BEFORE acting on any task related to it. Name a #handle in include to recover that object's full body.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
arroway_search_logFind WHERE a literal term appeared in the recent dated log, in one project or all of them.No findings
Why it is in this group
- The name "arroway_search_log" says "search": a word for reading.
Description, as the server wrote it Find WHERE a literal term appeared in the recent dated log, in one project or all of them. It searches what happened, not curated memory.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- 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.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- 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.
Looked at Nov 20, 2026, 19:08 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
- 14
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://www.arroway.app/.well-known/oauth-protected-resource/api/mcp
- Authorization servers
- https://www.arroway.app
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 14 tools that change things (2 destructive, 1 irreversible, 11 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.arroway.app/api/mcp: tools/list returned 18 tools to an anonymous client, including arroway_verify (destructive), arroway_retire (destructive), arroway_withdraw (irreversible), arroway_catch_up (write), arroway_norms (write) and 9 more
Findings
Matches of fixed checks, with the text they matched.
- Warnarroway_catch_up
The server marks "arroway_catch_up" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "call": a word for a change.
- Warnarroway_norms
The server marks "arroway_norms" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "call": a word for a change.
- Warnarroway_log
The server marks "arroway_log" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The name "arroway_log" says "log": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools18 changed.~18 changedView diff
- Changed:arroway_catch_upChanges thingsdescriptioninputSchemaannotations
- Changed:arroway_claimChanges thingsdescriptioninputSchemaannotations
- Changed:arroway_closeChanges thingsinputSchemaannotations
- Changed:arroway_complete_readOnly readsinputSchemaannotations
- Changed:arroway_continueOnly readsdescriptioninputSchemaannotations
- Changed:arroway_exportChanges thingsdescriptioninputSchemaannotations
- Changed:arroway_importChanges thingsinputSchemaannotations
- Changed:arroway_logChanges thingsdescriptioninputSchemaannotations
- Changed:arroway_moveChanges thingsinputSchemaannotations
- Changed:arroway_normsChanges thingsdescriptioninputSchemaannotations
- Changed:arroway_passChanges thingsdescriptioninputSchemaannotations
- Changed:arroway_readOnly readsdescriptioninputSchemaannotations
- Changed:arroway_rememberChanges thingsdescriptioninputSchemaannotations
- Changed:arroway_retireDeletes or cancelsdescriptioninputSchemaannotations
- Changed:arroway_search_logOnly readsdescriptioninputSchemaannotations
- Changed:arroway_start_projectChanges thingsdescriptioninputSchemaannotations
- Changed:arroway_verifyDeletes or cancelsdescriptioninputSchemaannotations
- Changed:arroway_withdrawCan't be undonedescriptioninputSchemaannotations
Install
Pinned to version 0.1.58. Values in angle brackets are yours to fill in.
claude mcp add --transport http arroway https://www.arroway.app/api/mcpclaude mcp add --transport http arroway https://www.arroway.app/api/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__arroway__arroway_read",
"mcp__arroway__arroway_continue",
"mcp__arroway__arroway_complete_read",
"mcp__arroway__arroway_search_log"
],
"ask": [
"mcp__arroway__arroway_catch_up",
"mcp__arroway__arroway_norms",
"mcp__arroway__arroway_log",
"mcp__arroway__arroway_remember",
"mcp__arroway__arroway_start_project",
"mcp__arroway__arroway_withdraw",
"mcp__arroway__arroway_export",
"mcp__arroway__arroway_import",
"mcp__arroway__arroway_move",
"mcp__arroway__arroway_pass",
"mcp__arroway__arroway_claim",
"mcp__arroway__arroway_close"
],
"deny": [
"mcp__arroway__arroway_verify",
"mcp__arroway__arroway_retire"
]
}
}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 arroway. Review it before you use it.
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.oaleviola/arroway/verify?hash=33f29b1a04d78834f8acc8cd20792afb6476d8d652faeeac641704751e039392" | jq -e '.changed == false'Pinned hash 33f29b1a04d7, from Nov 11, 2026, 14: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.oaleviola/arroway/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.oaleviola/arroway)Source: MCP Registry · repository. Synced Nov 11, 2026, 14:18 UTC.
Arroway MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Arroway MCP server safe?
- No scan can promise that. What its definitions show: 18 tools, 14 of which can change, send or delete something, and 3 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 Arroway MCP server delete data?
- Yes. 2 tools can delete, cancel or revoke something: arroway_verify and arroway_retire.
Can the Arroway MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: arroway_withdraw.
What tools does the Arroway MCP server have?
- 18 tools: 2 destructive, 1 irreversible, 11 write, 4 read. arroway_verify, arroway_retire, arroway_withdraw, arroway_catch_up, arroway_norms, arroway_log, arroway_remember, arroway_start_project and 10 more.
Does the Arroway MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Arroway MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Arroway MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 6, 2026. Every change is on this page and in its Atom feed.