ALEETH Authority MCP

What ALEETH Authority MCP does

The ALEETH Authority MCP MCP server provides a remote MCP endpoint with 51 governed tools: 41 base tools and 10 Astra plane tools declared by the deployed service. The repository does not contain the private implementation. Instead, it publishes the public interface, registry manifest, tool schemas, version history, and security information that callers and auditors can inspect.

Its defining behavior is governance around tool execution. Before a tool call runs, the service performs a risk check. A successful call is sealed with a signed Ed25519 receipt and added to a hash-linked ledger. The ledger is anchored to Bitcoin through OpenTimestamps, providing an external timestamping reference for the receipt chain.

How it works

Clients connect to the production endpoint at https://mcp.aleeth.com/mcp using MCP streamable HTTP over TLS. Requests must include an OAuth 2.0 bearer token. OAuth protected-resource discovery is available at https://mcp.aleeth.com/.well-known/oauth-protected-resource, and unauthenticated requests receive HTTP 401.

The service follows a fail-closed model. If its governance process cannot run, or if it cannot write the required receipt, it does not return the tool result. This makes receipt creation part of the call's execution contract rather than an optional after-the-fact record.

Receipts can be checked through the public verification endpoint at https://imperium.aleeth.com/api/receipts/verify/<hash>. The repository also identifies an offline trust anchor at https://imperium.aleeth.com/.well-known/ica-trust-anchor.json, which includes public keys, SHA-256 DER fingerprints, and an offline verification procedure.

Setup and configuration

Use an MCP client that supports a remote streamable-HTTP server and configure the endpoint URL. Obtain an OAuth bearer token before making calls; anonymous access is not supported. The repository states that read-only evaluation credentials may be requested from security@aleeth.com.

The ALEETH Authority MCP MCP server is hosted remotely, so this repository is not an installation package for a local implementation. The implementation is private, while the public repository contains the interface definition and provenance records. The published tool manifest is generated from the live server rather than maintained manually.

For protocol and authentication checks, the README provides this command pattern:

npx mcp-spec-check https://mcp.aleeth.com/mcp --bearer <token>

Tools and capabilities

The deployed service declares 51 tools in total. The available names, descriptions, and input schemas are published in tools/manifest.json. That manifest is generated from the live endpoint, so it is the appropriate source for determining the current tool surface and request shapes.

The server also supplies governance evidence for calls. Signed receipts can be verified online or against the published trust anchor without contacting ALEETH during offline verification. The repository includes performance data and a version history, allowing users to inspect documented runtime conditions and interface changes.

Limitations and notes

The source implementation is private. The repository supports interface and provenance inspection, but it does not provide local server code. Tool behavior should therefore be evaluated against the hosted endpoint and its published manifest.

Access requires OAuth 2.0 bearer authentication, TLS, and a compatible remote MCP client. Calls may fail without returning a result when governance or receipt persistence is unavailable. The README identifies the current independent protocol check as grade A, with the stated verification date of 2026-07-24; this is a point-in-time result rather than a guarantee for future deployments.

The repository does not list individual tool names in the provided material, so selecting the service for a particular operation requires reviewing tools/manifest.json or querying the authenticated server.