Xident MCP
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Xident MCPVerify this Xident webhook signature for me"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Xident MCP servers and agent skill
Tools for building — and running — Xident age and identity verification from an AI agent.
Package | What it is |
Build-time MCP server. Docs lookup, sandbox test verifications, webhook debugging. Runs on a developer machine. | |
Runtime MCP server for production agents — an OAuth 2.1 resource server. Holds no tenant credential; forwards the caller's token. | |
Agent skill — teaches any agent to integrate Xident correctly. No runtime, no credentials. | |
Claude Code plugin bundling the skill and the dev server. |
Quick start
Claude Code
/plugin marketplace add xident-io/mcp
/plugin install xident@xident-ioAny MCP client
{
"mcpServers": {
"xident-dev": {
"command": "npx",
"args": ["-y", "@xident/mcp-dev"],
"env": { "XIDENT_API_KEY": "sk_test_your_sandbox_key" }
}
}
}XIDENT_API_KEY is optional. Without it you still get xident_search_docs,
xident_get_endpoint, xident_verify_webhook_signature, and
xident_explain_session — enough to write a correct integration.
Related MCP server: Agent Identity MCP Server
Tools
Tool | Key needed | Read-only |
| no | yes |
| no | yes |
| no | yes |
| no* | yes |
| sandbox | yes |
| sandbox | no |
| sandbox | yes |
| sandbox | no |
| sandbox | yes |
* xident_explain_session needs a key only when you pass a token instead of a
reason code.
What these servers deliberately cannot do
No tool deletes anything, writes to a fraud blacklist, or changes billing.
Specifically excluded: DELETE /verify/v1/2fa/users/:id (GDPR hard delete), all
blacklist writes, and any key or billing mutation. This is enforced by a test,
not a convention.
xident_simulate_webhook refuses any target that is not localhost, so it cannot
be used to make requests on someone else's behalf.
Running agents in production
@xident/mcp is a remote MCP server. A tenant authorises a client through
Xident's consent screen, and the client calls the server with the resulting
bearer token. Tools outside the token's scopes are not advertised.
docker run -p 8080:8080 \
-e XIDENT_MCP_RESOURCE_URL=https://mcp.yourdomain.com \
ghcr.io/xident-io/mcpSee packages/mcp for the full contract.
Stability
Tool names and input schemas are additive-only, pinned by a golden test. A rename is a broken promise, not a snapshot to regenerate.
Development
pnpm install
pnpm -r build
pnpm -r testLicence
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
Give AI agents identity, scoped access, trusted context, and verifiable actions through MCP.
MCP server for building and testing AI agents with multi-model experimentation and insights.
A paid remote MCP for ZeroID, built to return verdicts, receipts, usage logs, and audit-ready JSON.
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
Related MCP Servers
- AlicenseAqualityDmaintenanceMCP server for AI agent identity — verify agents with Ed25519 signatures, check trust scores, sign and verify content, exchange encrypted messages. Built on the Agent Identity Protocol (AIP).8MIT
- AlicenseNot gradedqualityDmaintenanceMCP Server for AI agent identity and authorization. Create, verify, and manage agent identities with trust scores and scoped authorization tokens.MIT
- AlicenseAqualityDmaintenanceMCP server for enterprise authentication and authorization — JWT validation, OIDC token inspection, OAuth 2.0 introspection, and role-based access control for AI agents.8MIT
- AlicenseAqualityDmaintenanceMCP server for AI agent trust verification, enabling agents to verify identities, check trust scores, and build reputation across multiple blockchain and web platforms.125 npm1MIT