sigelo

io.github.csigelov0.1.0Updated Oct 4, 2026

Portable, offline-verifiable identity for AI agents: DID, challenges, attestations, bundles.

VerifiedStreamable HTTPWeb executableDeveloper Tools Security & Monitoring

Overview

AI-generated overview

Lets an assistant verify portable, offline-checkable identity bundles for AI agents, returning a pass or reject result.

What it does: The server exposes a single verification tool, sigelo_verify, which checks identity bundles and returns the section 9.1 result on success or a REJECT error otherwise (R6, R11). The same verifier is available as a remote Streamable HTTP endpoint, as a plain HTTP POST, and offline from the local server or the sigelo-verify implementation (R6, R10, R12). It is described as stateless and as holding no identity, wallet, or key (R7).
When to use it: Use it when an assistant needs to check whether an agent identity bundle, attestation, or challenge response is valid, either online through the hosted verifier or offline on the local machine. It fits workflows that want the same verification result from a remote endpoint, a plain HTTP call, or a local implementation (R12).
Requirements: Either the remote endpoint at over Streamable HTTP, or a local Node.js runtime to run the zero-dependency stdio server with node server.mjs (R2). No accounts, API keys, environment variables, or headers are declared. Network access is needed only for the remote and plain-HTTP verification routes (R6, R10).

Before you install

The remote endpoint is described as stateless and holding no identity, wallet, or key (R7), and the manifest declares no authentication, environment variables, or headers. Verification sends the bundle to the remote service when the remote or HTTP route is used (R6, R10), so treat bundle contents as data leaving your machine; the offline tool avoids that. No write, delete, or payment behavior is described.

Installation

In SourceWeft

Open sigelo in the dashboard and add it to a workspace.
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.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "sigelo": {
      "type": "http",
      "url": "https://sigelo.io/mcp"
    }
  }
}

README

sigelo-mcp

A zero-dependency stdio MCP server: node server.mjs. Tools, configs per harness and test status are in ../README.md; npm test → ALL PASS.

Claude Code plugin, no wallet (plugins/): claude plugin marketplace add csigelo/sigelo && claude plugin install sigelo@csigelo.

Remote (verify only)

https://sigelo.io/mcp: MCP over Streamable HTTP (revision 2026-07-28, also answering the legacy initialize handshake), stateless, JSON responses only, one tool — this server's sigelo_verify, the same definition and result. No identity, no wallet, nothing that holds a key. Add it with claude mcp add --transport http sigelo-remote https://sigelo.io/mcp, or, in server.json, the remotes entry. Details and limits: world/README.md. The same verifier as plain HTTP:

node -e 'fetch("https://sigelo.io/world/verify",{method:"POST",body:require("fs").readFileSync("bundle.json")}).then(r=>r.text()).then(console.log)'

node -e 'fetch("https://sigelo.io/world/verify",{method:"POST",body:require("fs").readFileSync("bundle.json")}).then(r=>r.text()).then(console.log)'

The answer is the §9.1 result (200), or {"error": "REJECT: …"} (422); the body may be a bare bundle or {bundle, now}. An agent never needs either: the same result comes offline from this server's sigelo_verify, from sigelo-verify, or from any implementation that passes the vectors.

Source: integrations/mcp/README.md at commit f8149bb

Tools

Tool metadata has not been indexed yet.

Version history

v0.1.0LatestOct 4, 2026