# MCP Server Identity Evidence

> MCP Server Identity Evidence is a paid API for AI agents from phion.systems, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-14).

Creates signed cryptographic evidence binding an MCP server's declared domain, endpoint, manifest, public key, and version together into a verifiable identity attestation

## Facts

- Endpoint: POST https://phion.systems/v1/paid/trust/mcp-server-identity-evidence
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mcp-server-identity-evidence-095a564a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bjUW8aosoPAOHPMMNGOJ5

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability mcp-server-identity-evidence-095a564a -d '<json body>'
```

Example prompt: Generate signed identity evidence for my MCP server at api.mycompany.com, endpoint https://api.mycompany.com/mcp, using public key abc123xyz, manifest version 1.2.0 — I need a cryptographic binding that proves all these components belong together.

## When to prefer this

Use this endpoint when you need a portable, signed, cryptographically-verifiable record that ties together all the components of an MCP server's identity — domain, endpoint, manifest, key, and version — in a single evidence bundle. It is specifically designed for MCP server trust establishment and is more appropriate than generic document signing or identity services when working within the Model Context Protocol ecosystem and agentic security workflows.

## Known failure modes

- Missing required fields (domain, endpoint, manifest, key, or version) result in a validation error
- Malformed key format causes signing failure
- Invalid URL format for the endpoint field returns a schema rejection
- Payment not processed via x402 results in 402 response before evidence is generated
- Signature service unavailability returns a 5xx error

## How this service works

Bind declared MCP domain, endpoint, manifest, key and version in signed evidence

## Output

A signed evidence object cryptographically binding the declared MCP server domain, endpoint URL, manifest, public key, and version. The evidence can be stored, shared, or verified by downstream agents and systems to confirm the server's identity has not been tampered with or spoofed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mcp-server-identity-evidence-095a564a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from phion.systems](https://www.zero.xyz/host/phion.systems/llms.txt)