Aruon Beacon
REMOTE · BEACON.ARUON.AI
Order Aruon Beacon for a website: AI assistants can read it, a person checks it.
Available components
Last scanned (16 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 21 Nov 2026.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1144 tokens (~163/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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 58% 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
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.
- 21 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.
- 19 Nov 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “create_order” rewrote its description, which is the text the model reads security
- Tool “get_order_status” rewrote its description, which is the text the model reads security
- Tool “list_products” rewrote its description, which is the text the model reads security
- Tool coverage: 78% → 58% ▼ functional
- Schema quality: pass → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “confirm_crypto_payment” functional
- New tool “request_new_quote” functional
- New tool “start_crypto_payment” functional
- “create_order” added an optional parameter “agent_operator” cosmetic
- “create_order” added an optional parameter “ai_agent_name” cosmetic
- “create_order” added an optional parameter “authorization_statement” cosmetic
- “create_order” added an optional parameter “contact” cosmetic
- “create_order” added an optional parameter “principal” cosmetic
- “create_order” added an optional parameter “rail” cosmetic
- “get_order_status” added an optional parameter “order_token” cosmetic
- “create_order” reworded the description of “sku” cosmetic
- “get_order_status” made “operator_key” optional cosmetic
- “get_order_status” made “order_id” optional cosmetic
- Tool “create_order” changed its title: Ask for a product for a website → Ask for a product for a website, paid in crypto cosmetic
- 18 Nov 26 63
First indexed and scored.
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://beacon.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=beacon.aruon.ai | CN=YR1,O=Let's Encrypt,C=US | 7 Oct 2026 | 5 Jan 2027 | RSA 2048 | SHA256-RSA | 6aaca428df2654e02bd348463bd326ea613 |
| SANs: beacon.aruon.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of beacon.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=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://beacon.aruon.ai/mcp | Verified | 200 | |
| http (plaintext) | http://beacon.aruon.ai/mcp | HTTPS enforced | 308 | https://beacon.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 Can Beacon serve this site ~95
Whether Beacon can score a website and install on it, from the published platform list and Beacon's address rules. Nothing is fetched in this call: what can only be known from the site itself is answered "we will check it when we score it".
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | what it is built on, if known, e.g. WordPress |
| site | string | yes | the website, e.g. example.com |
No output schema declared.
No examples provided.
confirm_crypto_payment Confirm a crypto payment ~122
For the code the buyer received: answers the quote, or the hold and who must act. The quote is an exact amount (price, 5% Texas sales tax and a small unique tail), a receive address and a 20-minute window to send it, from the wallet declared. The agent never pays: the buyer sends from their own wallet. Paying publishes nothing by itself: a person at Aruon reviews the build, and the site owner approves a preview before anything goes live.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
| order_token | string | yes | – |
No output schema declared.
No examples provided.
create_order Ask for a product for a website, paid in crypto ~471
Records an order request for a website's owner (the principal). Nothing is charged. While crypto is open for the contact_email, rail usdc_base answers an order_token, and no operator key is needed: start_crypto_payment is next. Otherwise, with a crypto rail, an approved operator gets a crypto quote (exact amount, address, 20-minute send window) next to the card link, or a hold that waits for a person or for the principal; every other request is answered pending_review and a person at Aruon reviews it. Without rail, or with rail "card", it is a card order. A person at Aruon checks the first order from a new agent operator or a new buyer before anything goes live; the payment service can also hold an order before it is quoted. Once quoted, a payment on Base can take about 20 minutes to finalise after the send. A person reviews first-time and large orders. Paying publishes nothing by itself: a person at Aruon reviews the build, and the site owner approves a preview before anything goes live.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_operator | string | – | required with a crypto rail |
| ai_agent_name | string | – | required with a crypto rail |
| authorization_statement | string | – | the principal's authorisation of this agent, logged; required with a crypto rail |
| contact | string | – | how a person at Aruon reaches the operator; required with a crypto rail |
| contact_email | string | yes | the site owner's email address |
| operator_id | string | – | your operator id, given by Aruon with your key |
| operator_key | string | – | your operator key, given by Aruon |
| principal | object | – | the site owner's details for the payment service's intake (all optional here; what is still missing comes back in principal.missing) |
| rail | string | – | card (the default, as with no rail): the website's card path, where an approved operator gets the product's checkout link for the site owner; this service itself answers a card order pending_review a… |
| site | string | yes | the website, e.g. example.com |
| sku | string | yes | a sku from list_products with a crypto total |
No output schema declared.
No examples provided.
get_order_status Order status ~107
With the order_token create_order gave: this order's status and its crypto block. Or with order_id and operator_key, for the operator whose key made the order: pending_review while a person has not approved the operator, else the payment service's order view (held and why, quoted and the quote, paid, expired or denied). Paid publishes nothing by itself.
| Name | Type | Req | Description |
|---|---|---|---|
| operator_key | string | – | – |
| order_id | string | – | – |
| order_token | string | – | – |
No output schema declared.
No examples provided.
list_products List products ~73
The Aruon Beacon products offered today, with their prices in US dollars before tax (5% Texas sales tax on SaaS is added at checkout), each orderable one's crypto total, and the payment rails accepted now. Other products are quoted by a person: see https://beacon.aruon.ai/pricing.json.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
request_new_quote Ask for a new quote ~41
For an order token whose quote has expired: a fresh 20-minute quote, and the order's status read again.
| Name | Type | Req | Description |
|---|---|---|---|
| order_token | string | yes | – |
No output schema declared.
No examples provided.
start_crypto_payment Start a crypto payment ~183
For an order token from create_order: files the payment details (rail usdc_base, billing address with a two-letter state for the US, the wallet the buyer pays from, role, acceptance) and Beacon emails a one-time code to the buyer's own inbox (the order's email address), never to the agent. Answers the order's status.
| Name | Type | Req | Description |
|---|---|---|---|
| accept | boolean | yes | true only when the buyer has read and accepted the Terms of Service including Schedule C, the refund policy and the Privacy Policy (https://aruon.ai/terms-of-service, https://aruon.ai/privacy) |
| billing | object | yes | – |
| order_token | string | yes | – |
| phone | string | – | the buyer's phone, if not given at create_order |
| rail | string | yes | – |
| role | string | yes | – |
| wallet_address | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Aruon Beacon MCP server?
Aruon Beacon is a hosted endpoint at https://beacon.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 · beacon.aruon.ai
claude mcp add --transport http aruon-ai-beacon 'https://beacon.aruon.ai/mcp'
What is the Aruon Beacon MCP server?
Aruon Beacon is an MCP server listed in the public MCP registry as io.github.Aruon-AI/beacon. Order Aruon Beacon for a website: AI assistants can read it, a person checks it. This page covers its hosted endpoint (https://beacon.aruon.ai/mcp).
Is the Aruon Beacon MCP server safe to use?
Aruon Beacon scores 63 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 Beacon MCP server expose?
Aruon Beacon exposes 7 tools: list_products, create_order, check_coverage, get_order_status, start_crypto_payment, and 2 more. Their descriptions and schemas cost roughly 1,092 tokens of context every time the server is loaded.
Does the Aruon Beacon MCP server require authentication?
No. We connected to Aruon Beacon without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Aruon Beacon MCP server still maintained?
Aruon Beacon 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 Beacon MCP server?
VerifyMCP ran 12 checks on Aruon Beacon, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Aruon Beacon: Authorization. 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.