Zeroidagent MCP

What zeroidagent-mcp MCP server does

The zeroidagent-mcp MCP server provides a remote MCP interface to ZeroID Agent Identity. It is designed for workflows that need to establish agent accountability before tool use and retain structured records of identity-related actions.

Four MCP tools are available:

• issue_agent_identity for issuing an agent identity.
• check_scope_lease for checking a scope lease.
• revoke_agent_identity for revoking an agent identity.
• export_identity_receipt for exporting an identity receipt.

The hosted service also provides usage logs and receipt-oriented JSON. The supplied material describes these outputs as suitable for audit-ready workflows, but does not specify the fields or schemas returned by each tool.

How it works

Calls are sent to the remote MCP endpoint at https://zeroidagent.clauxel.com/mcp using Streamable HTTP. Clients send JSON-RPC requests and authenticate production calls with an HTTP bearer token:

Authorization: Bearer <token>

The token is issued through the ZeroID product website after selecting a plan and creating or requesting an API token. Unauthenticated browser requests to the MCP endpoint return a JSON error rather than internal service details.

A public server-card document is available at https://zeroidagent.clauxel.com/server-card.json. The registry name listed for the service is com.clauxel.zeroidagent/zeroidagent-mcp.

Setup and configuration

1. Open the ZeroID website and choose a plan.
2. Create or request an API token.
3. Configure an MCP client that supports remote Streamable HTTP servers with the endpoint URL.
4. Supply the bearer token when making JSON-RPC requests.

The repository is documentation and directory-submission material for the hosted service. It does not include the private production implementation, so local source installation is not documented. No required environment variable names are provided.

Limitations and notes

zeroidagent-mcp MCP server access is paid and hosted remotely; it is not presented as a local or self-hosted server. The available material does not document pricing amounts, token lifetime, request limits, identity fields, lease semantics, receipt schemas, or the exact usage-log format. Those details should be confirmed through the product website or server documentation before implementation.

The service exposes Streamable HTTP rather than a documented stdio transport. Choose an MCP client with remote Streamable HTTP support and a way to attach a bearer token. The public endpoint, server card, and product website are the documented integration points.