Attestify OS

io.github.attestifyagentPublished by GitHub account attestifyagentv0.2.1Updated Oct 24, 2026

MCP stdio server for Attestify OS — governed agent execution and Attestify Trust signed evidence.

VerifiedSTDIODesktop onlyFinanceSecurity & MonitoringAI & ML

Overview

AI-generated overview

Local stdio MCP server that lets an assistant run Attestify OS research agents and submit or verify Attestify Trust signed evidence receipts.

What you can do
Run a deep research query through the Attestify Research Agent and get a structured briefing with summary, findings and caveats, plus run and receipt identifiers and a USDC price. Submit signed work-completion evidence for a registered Trust agent and receive a timestamped, publicly verifiable receipt. Verify any Trust receipt by its ID, including receipts from other agents.
When to use it
Useful when you want an assistant to produce metered research briefings through Attestify OS, or to record and later verify signed proof that an agent completed work in compliance or regulated contexts.
Requirements
Runs locally as an npm package spawned by an MCP host such as Claude Desktop, Cursor or Windsurf. Needs ATTESTIFY_BASE_URL and usually ATTESTIFY_API_KEY; the Trust tools additionally need TRUST_AGENT_ID and TRUST_PRIVATE_KEY, generated once with the trust-init command. Network access to the Attestify service.
Before you install
Research calls are metered at $0.023 USDC each and logged to an evidence ledger; without an API key runs are unauthenticated and subject to anonymous plan limits. TRUST_PRIVATE_KEY is an Ed25519 signing key that should be generated once and kept out of session configs. Submitted evidence summaries are signed and permanently recorded.

Installation

In SourceWeft

  1. Open Attestify OS in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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):

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:

bash
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 key2. POST /api/budgets   → set USDC spend ceiling3. POST /api/policies  → attach governance rules4. (this MCP server)   → every run auto-enforced

Links

Source: README.md at commit e80dded

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.1LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.