Aruon Beacon
Order Aruon Beacon for a website: AI assistants can read it, a person checks it.
¿Debería usar esto?
Calidad y seguridad
Hallazgos (2)
- HIGH
- MEDIUMen list_products
Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.
Costo de contexto
Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.
Instalar
Instalación con un clic
Agrega esto a tu archivo `claude_desktop_config.json`:
{
"mcpServers": {
"beacon": {
"url": "https://beacon.aruon.ai/mcp"
}
}
}Puntos de conexión remotos
https://beacon.aruon.ai/mcpstreamable-httpQué puede hacer
Inventario de herramientas
Herramientas (7)
🟢list_products
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.
Esquema de entrada
{
"type": "object",
"properties": {},
"additionalProperties": false
}🟡create_order(sku, site, contact_email, rail, operator_id, ...)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"sku": {
"type": "string",
"description": "a sku from list_products with a crypto total"
},
"site": {
"type": "string",
"description": "the website, e.g. example.com"
},
"contact_email": {
"type": "string",
"description": "the site owner's email address"
},
"rail": {
"type": "string",
"enum": [
"card",
"btc",
"eth_ethereum",
"usdc_ethereum",
"usdc_base"
],
"default": "card",
"description": "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 and a person at Aruon reviews it. Or one of list_products' rails"
},
"operator_id": {
"type": "string",
"description": "your operator id, given by Aruon with your key"
},
"operator_key": {
"type": "string",
"description": "your operator key, given by Aruon"
},
"ai_agent_name": {
"type": "string",
"description": "required with a crypto rail"
},
"agent_operator": {
"type": "string",
"description": "required with a crypto rail"
},
"contact": {
"type": "string",
"description": "how a person at Aruon reaches the operator; required with a crypto rail"
},
"authorization_statement": {
"type": "string",
"description": "the principal's authorisation of this agent, logged; required with a crypto rail"
},
"principal": {
"type": "object",
"description": "the site owner's details for the payment service's intake (all optional here; what is still missing comes back in principal.missing)",
"properties": {
"legal_name": {
"type": "string"
},
"organization": {
"type": "string"
},
"phone": {
"type": "string"
},
"role": {
"type": "string"
},
"intended_use": {
"type": "string"
},
"billing": {
"type": "object",
"properties": {
"line1": {
"type": "string"
},
"line2": {
"type": "string"
},
"city": {
"type": "string"
},
"region": {
"type": "string"
},
"postal": {
"type": "string"
},
"country": {
"type": "string"
}
},
"additionalProperties": false
},
"declared_wallets": {
"type": "array",
"items": {
"type": "object",
"properties": {
"family": {
"type": "string"
},
"address": {
"type": "string"
}
},
"required": [
"family",
"address"
],
"additionalProperties": false
}
}
},
"additionalProperties": false
}
},
"required": [
"sku",
"site",
"contact_email"
],
"additionalProperties": false
}🟢check_coverage(site, platform)
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".
Esquema de entrada
{
"type": "object",
"properties": {
"site": {
"type": "string",
"description": "the website, e.g. example.com"
},
"platform": {
"type": "string",
"description": "what it is built on, if known, e.g. WordPress"
}
},
"required": [
"site"
],
"additionalProperties": false
}🟡get_order_status(order_token, order_id, operator_key)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"order_token": {
"type": "string"
},
"order_id": {
"type": "string"
},
"operator_key": {
"type": "string"
}
},
"additionalProperties": false
}🟡start_crypto_payment(order_token, rail, billing, role, wallet_address, ...)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"order_token": {
"type": "string"
},
"rail": {
"type": "string"
},
"billing": {
"type": "object",
"additionalProperties": false,
"required": [
"line1",
"city",
"postal",
"country"
],
"properties": {
"line1": {
"type": "string"
},
"line2": {
"type": "string"
},
"city": {
"type": "string"
},
"region": {
"type": "string"
},
"postal": {
"type": "string"
},
"country": {
"type": "string"
}
}
},
"role": {
"type": "string",
"enum": [
"investor",
"broker",
"carrier",
"developer",
"other"
]
},
"wallet_address": {
"type": "string"
},
"phone": {
"type": "string",
"description": "the buyer's phone, if not given at create_order"
},
"accept": {
"type": "boolean",
"description": "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)"
}
},
"required": [
"order_token",
"rail",
"billing",
"role",
"wallet_address",
"accept"
],
"additionalProperties": false
}🟡confirm_crypto_payment(order_token, code)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"order_token": {
"type": "string"
},
"code": {
"type": "string"
}
},
"required": [
"order_token",
"code"
],
"additionalProperties": false
}🟢request_new_quote(order_token)
For an order token whose quote has expired: a fresh 20-minute quote, and the order's status read again.
Esquema de entrada
{
"type": "object",
"properties": {
"order_token": {
"type": "string"
}
},
"required": [
"order_token"
],
"additionalProperties": false
}Comunidad
Evidencia