Home / MCP registry index / io.github.oaleviola/arroway
Arroway
io.github.oaleviola/arroway in the official MCP registry.
Endpoint https://www.arroway.app/api/mcp. Source: github.com/oaleviola/arroway-plugin.
The registry describes it as: Arroway orchestrates people and AI agents around the decisions in force.
We read its 18 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
arroway_read arroway_continue arroway_complete_read arroway_catch_up arroway_search_log arroway_norms arroway_log arroway_remember arroway_verify arroway_start_project arroway_withdraw arroway_retire arroway_export arroway_import arroway_move arroway_pass arroway_claim arroway_close
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-oaleviola-arroway)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.