Attestify Os

io.github.attestifyagentPublished by GitHub account attestifyagentv0.1.1Updated Oct 25, 2026

Governed agent execution: x402 payments, budgets, receipts, verification, and audit.

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

Attestify Os is a governed agent execution server offering x402 payments, budgets, receipts, verification and audit for AI assistants.

What you can do
Run governed agent executions through the /api/run endpoint, subject to budgets and controls described in the registry entry. Handle x402 payments as part of agent execution. Produce receipts and verification records for executed actions. Support audit of agent activity. Discover the service without credentials; governed runs require a tenant API key.
When to use it
Use it when an assistant needs to execute agent actions under governance, with payment handling, budget limits, receipts and an audit trail, rather than calling services directly.
Requirements
Runs as a remote endpoint or as a local npm package over stdio. A tenant API key in the ATTESTIFY_API_KEY environment variable, issued via the keys endpoint, is optional for discovery and required for governed run calls. No authentication is declared in the manifest.
Before you install
The server handles x402 payments, so governed runs may spend money; set and check budgets before use. The tenant API key is a secret and should be kept out of logs and shared configuration. Executed actions are governed and recorded, so expect activity to be auditable.

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.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.attestifyagent%2Fattestify-os/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "attestify-os": {
      "type": "http",
      "url": "https://attestify-os.vercel.app/api/run"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

60% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.