npm attestify-mcpstdioupdated 11d ago
MCP server exposing Attestify OS agents — and Attestify Trust's no-wallet agent identity + signed evidence — as callable tools for Claude Desktop, Cursor, Windsurf, and any MCP-compatible host.
What can you do with Attestify OS?
attestify-mcp
MCP server exposing Attestify OS agents — and Attestify Trust's no-wallet agent identity + signed evidence — as callable tools for Claude Desktop, Cursor, Windsurf, and any MCP-compatible host.
Attestify OS is infrastructure for AI agents operating in financial, compliance, and regulated workflows. Every governed run delivers: routing → governance enforcement → budget check → SLA check → execution → output verification → immutable receipt → on-chain settlement evidence.
Live base URL: https://attestifyos.com
This package is a real Model Context Protocol stdio server — your MCP host spawns it as a subprocess and talks JSON-RPC to it directly. It is not a plain HTTP client library.
Quick start
Add to your MCP host's config (e.g. Claude Desktop's claude_desktop_config.json):
{
"mcpServers": {
"attestify": {
"command": "npx",
"args": ["-y", "attestify-mcp"],
"env": {
"ATTESTIFY_BASE_URL": "https://attestifyos.com",
"ATTESTIFY_API_KEY": "<your-tenant-api-key>",
"TRUST_AGENT_ID": "<optional — see Attestify Trust below>",
"TRUST_PRIVATE_KEY": "<optional — see Attestify Trust below>"
}
}
}
}
ATTESTIFY_API_KEY is a tenant API key issued via POST /api/keys — it's sent as the X-API-Key header on every run. Without one, runs are unauthenticated and subject to the plan/x402 limits that apply to anonymous callers.
TRUST_AGENT_ID / TRUST_PRIVATE_KEY are optional and unlock two more tools — see Attestify Trust below.
Tools
attestify_research
Runs a deep research query through the Attestify Research Agent (researcher-v2) via POST /api/run. Returns a structured briefing with executive summary, key findings, and caveats. Each call is metered at $0.023 USDC and logged to the Attestify evidence ledger.
Arguments:
| Field | Required | Description |
|---|---|---|
query |
Yes | The research question, topic, or subject to investigate. |
url |
No | Optional source URL to include as context for the research run. |
session_id |
No | Optional session ID for conversation continuity. |
Returns: a JSON blob with summary, loop_id, run_id, input_hash, output_hash, price_usdc, agent_id, receipt_url, and created_at.
attestify_trust_submit_evidence / attestify_trust_verify
Available whenever TRUST_AGENT_ID and TRUST_PRIVATE_KEY are both set. A separate concern from attestify_research above — no x402, no lanes, no spend, no wallet at any point.
attestify_trust_submit_evidence signs (Ed25519, via Node's built-in node:crypto — no extra dependency) and submits evidence that the agent completed real work, returning a signed, timestamped, publicly verifiable receipt.
| Field | Required | Description |
|---|---|---|
summary |
Yes | Plain-language description of the work done. Gets signed and permanently recorded. |
schema |
No | Evidence schema version. Default work-completion/v1. |
action_basis |
No | explicit (default) or discretionary. |
attestify_trust_verify independently re-verifies any receipt by ID — public, no API key needed, works for receipts from any agent.
| Field | Required | Description |
|---|---|---|
receipt_id |
Yes | The receipt ID to verify. |
Getting TRUST_AGENT_ID / TRUST_PRIVATE_KEY: run this once, outside of any MCP session — never generate a fresh identity per session, it would both break the agent's own verified-active streak and add noise to Attestify's public census instead of a real, citable number:
npx attestify trust-init --name "My MCP Agent"
This registers a free Trust agent, generates its Ed25519 signing key locally, and prints the two values to set in your MCP host's config. The private key never leaves your machine except as a signature.
Enterprise self-serve
Issue a tenant key, set a budget, attach policies — every subsequent run through this server is auto-governed:
1. POST /api/keys → issue tenant API key
2. POST /api/budgets → set USDC spend ceiling
3. POST /api/policies → attach governance rules
4. (this MCP server) → every run auto-enforced
Links
- Homepage: https://attestifyos.com
- Attestify Trust: https://attestifyos.com/trust
- Quickstart: https://attestifyos.com/quickstart
- OpenAPI spec: https://attestifyos.com/openapi.json
- x402 discovery: https://attestifyos.com/.well-known/x402.json
- GitHub: https://github.com/attestifyagent/attestify-mcp
Install
Add Attestify OS to your client. Pick the one you use.
claude mcp add attestify-mcp -- npx -y attestify-mcpcodex mcp add attestify-mcp -- npx -y attestify-mcpamp mcp add attestify-mcp -- npx -y attestify-mcp{
"mcpServers": {
"attestify-mcp": {
"command": "npx",
"args": [
"-y",
"attestify-mcp"
]
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"attestify-mcp": {
"command": "npx",
"args": [
"-y",
"attestify-mcp"
]
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
code --add-mcp '{"name":"attestify-mcp","command":"npx","args":["-y","attestify-mcp"]}'Or add the block manually to `.vscode/mcp.json` under `servers`.
{
"mcpServers": {
"attestify-mcp": {
"command": "npx",
"args": [
"-y",
"attestify-mcp"
]
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
{
"mcpServers": {
"attestify-mcp": {
"command": "npx",
"args": [
"-y",
"attestify-mcp"
]
}
}
}Add to `cline_mcp_settings.json` via the MCP Servers panel.
{
"mcpServers": {
"attestify-mcp": {
"command": "npx",
"args": [
"-y",
"attestify-mcp"
]
}
}
}Add to `~/.gemini/settings.json`.
{
"mcpServers": {
"attestify-mcp": {
"type": "local",
"command": "npx",
"args": [
"-y",
"attestify-mcp"
],
"tools": [
"*"
]
}
}
}Add to `~/.copilot/mcp-config.json`, or run `/mcp add` inside the CLI.
{
"context_servers": {
"attestify-mcp": {
"command": {
"path": "npx",
"args": [
"-y",
"attestify-mcp"
]
}
}
}
}Add to your Zed `settings.json`.
npx -y attestify-mcpRun `goose configure`, choose **Add Extension → Command-line Extension**, and paste this command.
Score
39 / 100
Incomplete
- Documentation25/25
- Maintenance19/25
- Trust6/20
- Capability0/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 4 days ago
- Has a release history
- Repository is not archived
- No licence detected
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 12 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Version history
| Versions | Published |
|---|---|
| 0.2.1Latest | Aug 28, 2026 |
| 0.1.7 | Aug 13, 2026 |