mcpField
A
Attestify OS

Attestify OS

Local
attestifyos.comAI & Agents0Updated 9w ago

About Attestify OS

Attestify OS is a stdio MCP server for governed agent execution and signed evidence, aimed at financial, compliance, and regulated workflows. It exposes research runs and Attestify Trust receipt submission and verification as callable tools.

Key features

  1. 01Run deep research and return structured briefs
  2. 02Govern runs and record evidence
  3. 03Sign and submit work-completion evidence
  4. 04Independently verify receipts by ID

Use cases

  1. 01Conduct research in financial and compliance workflows
  2. 02Create verifiable receipts for agent work
  3. 03Check the validity of existing receipts

MCP support

This stdio MCP server exposes research, evidence submission, and receipt verification tools to hosts such as Claude Desktop, Cursor, and Windsurf. Trust tools require the relevant identity credentials.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"attestifyagent-attestify": {
"command": "npx",
"args": [
"-y",
"attestify-mcp"
],
"env": {
"ATTESTIFY_BASE_URL": "<ATTESTIFY_BASE_URL>",
"ATTESTIFY_API_KEY": "<ATTESTIFY_API_KEY>",
"TRUST_AGENT_ID": "<TRUST_AGENT_ID>",
"TRUST_PRIVATE_KEY": "<TRUST_PRIVATE_KEY>"
}
}
}
}
Run commandnpx -y attestify-mcp
Environment variables to set
ATTESTIFY_BASE_URLBase URL of the deployed Attestify app.
ATTESTIFY_API_KEYSecretTenant API key issued via POST /api/keys, sent as X-API-Key on /api/run calls.
TRUST_AGENT_IDAttestify Trust agent ID, from a one-time `npx attestify trust-init` run. Enables attestify_trust_submit_evidence and attestify_trust_verify.
TRUST_PRIVATE_KEYSecretThat agent's Ed25519 private key (base64url), from the same trust-init run. Never leaves this server except as a signature.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmattestify-mcp0.2.1

Tools

1

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
urlstringNoOptional source URL to include as context for the research run.
querystringYesThe research question, topic, or subject to investigate.
session_idstringNoOptional session ID for conversation continuity.

Details

From the project README

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:

FieldRequiredDescription
queryYesThe research question, topic, or subject to investigate.
urlNoOptional source URL to include as context for the research run.
session_idNoOptional 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.

FieldRequiredDescription
summaryYesPlain-language description of the work done. Gets signed and permanently recorded.
schemaNoEvidence schema version. Default work-completion/v1.
action_basisNoexplicit (default) or discretionary.

attestify_trust_verify independently re-verifies any receipt by ID — public, no API key needed, works for receipts from any agent.

FieldRequiredDescription
receipt_idYesThe 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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.