ARUON Research
REMOTE · REIR.ARUON.AI
Sourced, analyst-released CRE site and land screens. Pay by card or USDC on Base or Ethereum.
Available components
Last scanned (17 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability54
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2432 tokens (~347/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_coverage” rewrote its description, which is the text the model reads security
- Tool “create_order” rewrote its description, which is the text the model reads security
- Schema quality: 307 → 347 ▼ functional
- “create_order” added an optional parameter “idempotency_key” cosmetic
- “start_crypto_payment” reworded the description of “accept_terms” cosmetic
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 0
- “start_crypto_payment” reworded the description of “accept_terms” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +7
- HTTPS: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- 12 Nov 26 0
- Tool “start_crypto_payment” rewrote its description, which is the text the model reads security
- “create_order” reworded the description of “min_acres” cosmetic
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Nov 2026 · Probed https://reir.aruon.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=aruon.ai | CN=YE2,O=Let's Encrypt,C=US | 4 Oct 2026 | 2 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 658aaaf77b99eb3630ac8f3d90a63d76a94 |
| SANs: *.aruon.ai, aruon.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 reir.aruon.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| aruon.ai. | No DS | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://reir.aruon.ai/mcp | Verified | 200 | |
| http (plaintext) | http://reir.aruon.ai/mcp | HTTPS enforced | 301 | https://reir.aruon.ai/mcp |
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 →
check_coverage Check coverage for a place ~285
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | A street address (geocoded once; address lookups are limited per connection). |
| county_fips | string | – | Five-digit county FIPS. |
| lat | number | – | – |
| lng | number | – | – |
| place_fips | string | – | Optional place FIPS. |
| sku | string | yes | The report the coverage is read for. |
| state | string | – | Two-letter state (with county_fips). |
| zip | string | – | A five-digit ZIP (its primary county). |
No output schema declared.
No examples provided.
confirm_crypto_payment Confirm the buyer's code and get the crypto quote ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
| order_token | string | yes | – |
No output schema declared.
No examples provided.
create_order Place an order (nothing is charged here) ~941
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_operator | string | yes | The organisation that runs the agent. A person checks the first order from an operator before its report is released. |
| ai_agent_name | string | yes | The agent placing the order. |
| asking_price | number | – | The asking price, where the report reads one (Property Screen, Housing Screen). |
| company | string | – | The buyer's company (optional). |
| consent | boolean | yes | true: the buyer accepts the Privacy Policy and the SMS terms. Required. |
| string | yes | The buyer's email. The one confirmation and the report go here; it must be a deliverable address. | |
| full_name | string | yes | The buyer's name. |
| geography | object | yes | ONE place. kind=address: {address}; kind=zip: {zip}; kind=county: {state, county_fips}; kind=parcel: {state, county_fips, parcel_id}; kind=pin: {lat, lng} (saved as coordinates, never turned into an… |
| idempotency_key | string | – | Optional, and recommended: a key you choose for this order (8–128 letters, digits, '.', '_', ':' or '-'; a UUID fits). Send the SAME key when you retry: a repeat with the same key and agent_operator… |
| min_acres | number | – | Minimum lot size in acres; the search applies it as the floor, unless it is also posted as a nice-to-have chip (emphasis only). |
| must | array | – | Must-have chips for the ring searches (Tower Sheet, Site Search): the catalog's hunt_chips keys; min_acres posts as min_acres=<n>. |
| nice | array | – | Nice-to-have chips, same keys. Emphasis only; they filter nothing. |
| notes | string | – | Anything the analyst should read; longer text is cut at 4,000 characters. Read by a person; it changes nothing automatically. |
| on_behalf_of | – | – | The principal the agent orders for: a name, or {name, organization, email}. |
| paid_ack | boolean | yes | true: the buyer acknowledges, verbatim: “I understand this is a paid engagement. After payment, an ARUON analyst checks the order and starts the report; the clock starts at our analyst's go-ahead, no… |
| phone | string | – | The buyer's phone (optional). |
| radius_mi | integer | – | Search radius in whole miles, 1–100, for the ring searches. Blank is the default ring. |
| site_acres | number | – | Site size the buyer needs, in acres (read by the analyst). |
| sku | string | yes | The report, by its catalog key (list_products / pricing.json). |
| use | string | – | Intended use, for the SKUs that read one (Property Screen, Tower Sheet, Site Search). |
No output schema declared.
No examples provided.
get_order_status Get an order's status ~238
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.
| Name | Type | Req | Description |
|---|---|---|---|
| order_token | string | yes | From create_order. |
No output schema declared.
No examples provided.
list_products List products and prices ~76
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
request_new_quote Get a new crypto quote after the last one expired ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| order_token | string | yes | – |
No output schema declared.
No examples provided.
start_crypto_payment Pay an order by crypto instead of the card link ~510
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.
| Name | Type | Req | Description |
|---|---|---|---|
| accept | boolean | yes | The buyer accepts the terms, the refund policy and the privacy policy for this payment, and this acknowledgment (hub-ack-2026-11-02-crypto): "I understand this is a paid engagement. After payment, an… |
| accept_terms | boolean | yes | Must be true: the buyer has read and accepts Schedule C (Crypto Payments) of ARUON's Terms of Service, version 2026-11-17.1: https://aruon.ai/terms-of-service#schedule-c. Required before the code is… |
| billing | object | yes | – |
| order_token | string | yes | – |
| phone | string | – | The buyer's phone. Required here when the order was placed without one. |
| rail | string | yes | – |
| role | string | yes | – |
| wallet_address | string | yes | – |
No output schema declared.
No examples provided.
How do I install the ARUON Research MCP server?
ARUON Research is a hosted endpoint at https://reir.aruon.ai/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 · reir.aruon.ai
claude mcp add --transport http aruon-ai-reir 'https://reir.aruon.ai/mcp'
What is the ARUON Research MCP server?
ARUON Research is an MCP server listed in the public MCP registry as io.github.Aruon-AI/reir. Sourced, analyst-released CRE site and land screens. Pay by card or USDC on Base or Ethereum. This page covers its hosted endpoint (https://reir.aruon.ai/mcp).
Is the ARUON Research MCP server safe to use?
ARUON Research scores 75 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 ARUON Research MCP server expose?
ARUON Research exposes 7 tools: list_products, check_coverage, create_order, get_order_status, start_crypto_payment, and 2 more. Their descriptions and schemas cost roughly 2,291 tokens of context every time the server is loaded.
Does the ARUON Research MCP server require authentication?
No. We connected to ARUON Research without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ARUON Research MCP server still maintained?
ARUON Research is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the ARUON Research MCP server?
VerifyMCP ran 13 checks on ARUON Research, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.