ARUON Research MCP server
io.github.Aruon-AI/reirAruon-AIstreamable-httpv1.0.3Scanned
Sourced, analyst-released CRE site and land screens. Pay by card or USDC on Base or Ethereum.
7 tools: 1 do something that can't be undone, 4 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 2
- 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.
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 ARUON Research MCP server can do
The ARUON Research MCP server is published by the GitHub account Aruon-AI. It has 7 tools. It can do things that cannot be undone, such as sending, paying or publishing (confirm_crypto_payment) and create or change data (4 tools: check_coverage, create_order, start_crypto_payment and request_new_quote), but cannot delete data. 2 tools only read.
1 tool brings in text other people can write (get_order_status); 2 tools can send data out of your system (create_order and start_crypto_payment).
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 18, 2026, version 1.0.3.
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.
7 tools
Can't be undone 1Claude Code: ask
confirm_crypto_paymentThe six-digit code mailed to the human buyer's inbox: ask the person for it; it is never sent to you.No findings
Why it is in this group
- The name "confirm_crypto_payment" says "payment": a word that usually means money moves, which cannot be taken back.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
Description, as the server wrote it The six-digit code mailed to the human buyer's inbox: ask the person for it; it is never sent to you. Answers with the quote (coin, network, exact amount, address, 20 minutes to send) or the hold and who must act. If the quote expires before a payment arrives, call request_new_quote.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Changes things 4Claude Code: ask
check_coverageHow well ARUON holds a place for one report: band full_data (24-hour clock where sla_hours is set), area_scan, zip_only or unknown, with the reason.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 How well ARUON holds a place for one report: band full_data (24-hour clock where sla_hours is set), area_scan, zip_only or unknown, with the reason. The answer the order page reads. Whether an order can be paid at once depends on the report: market_scan, scout_shortlist_founding and screen_parcel go to checkout only where the band is full_data; tower_sheet and site_search only where area_scan is true (the ordered ring is loaded), whatever the band; market_report on any US ZIP, whatever the band; tower_targets never: an analyst always confirms scope first. Anywhere else an analyst confirms scope before anything is charged; ok=false means the place could not be read. Even on held ground an order can still go to scope review, so create_order's status is the final word.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
create_orderFiles an order through the same door as the web order form and returns {order_token, status, checkout_url}.Can send data outNo findings
Why it is in this group
- The name "create_order" says "create": a word for a change.
What it can reach
- outboundThe input takes a destination (input.phone): what the tool writes goes there.
Description, as the server wrote it Files an order through the same door as the web order form and returns {order_token, status, checkout_url}. status is one of: awaiting_payment: Instant pay: finish checkout at checkout_url. Nothing runs before payment. Work begins at our analyst's go-ahead.; awaiting_scope_review: An analyst confirms scope with the buyer first, then sends the payment link or an invoice. Nothing is charged until then.; awaiting_human_approval: An order filed before 2026-11-04 from an agent operator we had not approved yet: a person approves it before any checkout link. Nothing is charged until then. checkout_url is set only for awaiting_payment. This tool never charges, never starts a report and never releases one. Requires the buyer's consent and paid-engagement acknowledgment, ai_agent_name and agent_operator. Send an idempotency_key and reuse it on any retry: a repeat with the same key and agent_operator returns the first order's token and status (replayed: true) and never files a second order. If create_order answers with a gateway error (502, 503, 504 or 524) or no answer at all, the order may or may not have been filed: retry with the same idempotency_key. Without a key, do not retry at once: wait about a minute and retry once; if the buyer then receives two order mails, they should pay only the link in the newest one and tell ARUON (reply to either mail), and the duplicate is cancelled. Nothing is charged until a checkout link is paid.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
request_new_quoteFor an order whose crypto quote expired before a payment arrived (get_order_status says so): asks for a new quote, at a new exact amount with 20 minutes to send.No findings
Why it is in this group
- The name "request_new_quote" says "request": a word for a change.
Description, as the server wrote it For an order whose crypto quote expired before a payment arrived (get_order_status says so): asks for a new quote, at a new exact amount with 20 minutes to send. It is the order page's GET A NEW QUOTE button. Refused while the current quote is still inside its 20 minutes (send against that one), once a payment to the order has been seen, and for an order no longer awaiting payment. No new code is emailed. Nothing is charged here: the buyer sends the payment from their own wallet. For an order crypto is not offered on, this tool answers that crypto is not offered for the order, and nothing changes.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
start_crypto_paymentFor an order awaiting payment: files the payment intake (billing address, role, the wallet the buyer will send from, and acceptance of the terms, refund and privacy documents, and …Can send data outNo findings
Why it is in this group
- The name "start_crypto_payment" says "start": a word for a change.
What it can reach
- outboundThe input takes a destination (input.phone): what the tool writes goes there.
Description, as the server wrote it For an order awaiting payment: files the payment intake (billing address, role, the wallet the buyer will send from, and acceptance of the terms, refund and privacy documents, and of Schedule C (Crypto Payments) of the Terms of Service with accept_terms, before any code is emailed). For a Ukrainian billing address, billing.region is required: the region's ISO 3166-2 code, e.g. UA-30. Texas sales tax applies. Unless the payment service has already verified the buyer's email, it mails a six-digit code to the HUMAN buyer's own inbox (the order's email), never to you: the person must give you the code for confirm_crypto_payment, and you cannot complete a crypto payment without it. Once a crypto payment starts, the card checkout link is withdrawn: one payment per order. A first crypto order is paid as usual and checked by a person before the report is released. Rails are the ones the payment service has on (get_order_status lists them; network fees are paid by the sender, and a rail whose fees are higher says so there). Nothing is charged here: the buyer sends the payment from their own wallet. Crypto is offered only on some orders (get_order_status carries a crypto block where it is); for any other order this tool answers that crypto is not offered for the order, and nothing changes.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 2Show 2 read-only tools
get_order_statusThe order's status by its order_token: awaiting_payment: Instant pay: finish checkout at checkout_url.Reads text others writeNo findings
Why it is in this group
- The name "get_order_status" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
Description, as the server wrote it The order's status by its order_token: awaiting_payment: Instant pay: finish checkout at checkout_url. Nothing runs before payment. Work begins at our analyst's go-ahead.; awaiting_scope_review: An analyst confirms scope with the buyer first, then sends the payment link or an invoice. Nothing is charged until then.; awaiting_human_approval: An order filed before 2026-11-04 from an agent operator we had not approved yet: a person approves it before any checkout link. Nothing is charged until then.; paid: Paid. The clock starts at our analyst's go-ahead, not at the card charge.; in_production: The report is being built.; in_review: The report is built and an analyst is reading it before release.; delivered: Released by an analyst and sent to the buyer's email.; held: A person at ARUON is looking at the order. Nothing is charged or sent until they act.; received: Received.; closed: Closed. No report will be sent on this order. checkout_url is set only while the order awaits payment.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
list_productsThe ARUON catalog: every report with its price (or null where it is quoted), whether it can be ordered now, whether it is instant pay, the turnaround, a sample and the terms.No findings
Why it is in this group
- The name "list_products" says "list": a word for reading.
Description, as the server wrote it The ARUON catalog: every report with its price (or null where it is quoted), whether it can be ordered now, whether it is instant pay, the turnaround, a sample and the terms. The same records as https://reir.aruon.ai/pricing.json. Empty, with a reason, while ordering is closed.
Annotations the server declares
- readOnlyHint: true
- 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.
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 out2
- 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 16, 2026, 14:21 UTC, unchanged since Nov 16, 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
- 5
- 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 5 tools that change things (1 irreversible, 4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://reir.aruon.ai/mcp: tools/list returned 7 tools to an anonymous client, including confirm_crypto_payment (irreversible), check_coverage (write), create_order (write), start_crypto_payment (write), request_new_quote (write)
Posture changes
- Nov 16, 2026
- Tools that change things, listed without credentials: 4 to 5
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.
Tools3 changed.~3 changedView diff
- Changed:check_coverageChanges thingsdescription
- Changed:create_orderChanges thingsdescriptioninputSchema
- Changed:start_crypto_paymentChanges thingsdescriptioninputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 4 -> 5.View diff
- Tools that change things, listed without credentials: 4 to 5
Tools1 added, 1 changed.+1 added~1 changedView diff
- Added:request_new_quoteChanges things
- Changed:confirm_crypto_paymentCan't be undonedescription
Install
Pinned to version 1.0.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http reir https://reir.aruon.ai/mcpclaude mcp add --transport http reir https://reir.aruon.ai/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__reir__list_products",
"mcp__reir__get_order_status"
],
"ask": [
"mcp__reir__check_coverage",
"mcp__reir__create_order",
"mcp__reir__start_crypto_payment",
"mcp__reir__confirm_crypto_payment",
"mcp__reir__request_new_quote"
],
"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 reir. Review it before you use it.
Capability tags behind 3 rules
- mcp__reir__create_order outbound
- mcp__reir__get_order_status untrusted-input
- mcp__reir__start_crypto_payment outbound
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.Aruon-AI/reir/verify?hash=aeeed7489b6579a036395000d1533f01ced14c9f485f687e553aa8995e6ab7e5" | jq -e '.changed == false'Pinned hash aeeed7489b65, from Nov 18, 2026, 15: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.Aruon-AI/reir/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Aruon-AI/reir)Source: MCP Registry. Synced Nov 18, 2026, 15:17 UTC.
ARUON Research MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the ARUON Research MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 5 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 ARUON Research MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the ARUON Research MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: confirm_crypto_payment.
What tools does the ARUON Research MCP server have?
- 7 tools: 1 irreversible, 4 write, 2 read. confirm_crypto_payment, check_coverage, create_order, start_crypto_payment, request_new_quote, list_products and get_order_status.
Does the ARUON Research MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the ARUON Research MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_order and start_crypto_payment.
Has the ARUON Research MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.