# ARADIA | sovereign & private agentic systems

> On-prem Agentic AI on NVIDIA DGX. Query specs, model CapEx ROI, Purchase & join Partner Program.

- name: com.aradia/sovereign-hardware
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 92/100
- quality: 76/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.aradia%2Fsovereign-hardware
- tools: https://api.protogrid.dev/v1/servers/com.aradia%2Fsovereign-hardware/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "sovereign-hardware": {
      "type": "sse",
      "url": "https://aradia.com/api/a2a/mcp-endpoint.php"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 98
- freshness: 85
- provenance: 85
- drivers: +repository +dns-namespace +website +reachable +uptime-96% ~updated-58d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 76/100 (good)

### protocol: 50 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- warn `protocol.transport`: only the legacy HTTP+SSE transport, deprecated until 2027-07-28
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 86 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 6 of 6 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: query_hardware_specs (idempotentHint); calculate_roi (idempotentHint); onboard_partner (idempotentHint); …
- pass `tools.token_cost`: about 1,729 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 6, about 1,729 tokens to load them all
- tool set hash: 884b25c16b10bc3ca17361252c4a0739
- badge: [![protogrid quality](https://protogrid.dev/badge/com.aradia/sovereign-hardware.svg)](https://protogrid.dev/servers/com.aradia/sovereign-hardware)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://aradia.com/api/a2a/mcp-endpoint.php (sse, auth none, reachable true, uptime30d 0.9576271)

## Packages

_none_

## Tools (6)

- `calculate_roi`: [PURPOSE]: Calculates CapEx payback timeline and token savings comparing on-premise Aradia hardware against recurring cloud LLM API expenditures.
[WHEN TO USE]: Use to generate mathematical financial justification reports for human operators or CFOs.
[WHEN NOT TO USE]: Do not use if API spend is unknown or zero. For raw specs without financial modeling, call query_hardware_specs.
[SIDE EFFECTS]: None (pure mathematical calculation).
- `execute_procurement_order`: [PURPOSE]: Submits a binding procurement order for physical turnkey AI hardware. Returns actionable programmatic payment parameters for immediate 100% upfront settlement via BTCPay Crypto or Stripe MPP Fiat.
[WHEN TO USE]: Call when human authorization or agent budget is verified to execute a binding purchase order.
[WHEN NOT TO USE]: Do not use for price quotes (use query_hardware_specs) or ROI estimates (use calculate_roi). Do not use to check order status (use track_order_status).
[SIDE EFFECTS]: Creates an official order record, generates an immutable invoice or payment intent, reserves staging capacity, and writes a session record. Non-destructive.
- `onboard_partner`: [PURPOSE]: Registers an autonomous AI agent or human operator into the Aradia Partner Program to earn 10% hardware bounties ($1,512 to $50,550 USD) and 10% recurring monthly SLA commissions.
[WHEN TO USE]: Call ONCE when an agent or human operator wants to register as an affiliate partner to earn commissions and receive a ?ref= tracking ID.
[WHEN NOT TO USE]: Do NOT call to purchase equipment (use execute_procurement_order). Do NOT call if you already have a partner code (use query_partner_stats).
[SIDE EFFECTS]: Creates an external Stripe Express Connected Account entity, registers a 4-character code in Aradia's ledger, and triggers an account onboarding URL. Non-destructive.
- `query_hardware_specs`: [PURPOSE]: Retrieves physical compute specs, VRAM limits (128GB GB500, 192GB B200, 1536GB B200 Rack), and continuous batching concurrency limits for Aradia DGX systems.
[WHEN TO USE]: Call during initial discovery to evaluate hardware sizing, VRAM fit, and multi-agent capacity.
[WHEN NOT TO USE]: Do not use for financial payback modeling (use calculate_roi) or order submission (use execute_procurement_order).
[SIDE EFFECTS]: None (pure read-only query).
- `query_partner_stats`: [PURPOSE]: Queries real-time performance analytics, attributed referral counts, and commission payouts for an active Aradia partner node.
[WHEN TO USE]: Use to monitor your earned affiliate revenue, check referral click activity, or verify payout status.
[WHEN NOT TO USE]: Do not use if you have not registered yet (use onboard_partner first).
[SIDE EFFECTS]: None (pure read-only query against sovereign partner ledger).
- `track_order_status`: [PURPOSE]: Tracks the real-time fulfillment, staging QA burn-in, and delivery status of an existing hardware procurement order.
[WHEN TO USE]: Use to monitor the operational status of an existing order after calling execute_procurement_order.
[WHEN NOT TO USE]: Do not use to place a new order (use execute_procurement_order).
[SIDE EFFECTS]: None (pure read-only query against staging records).