sigelo

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

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
100%
Naming quality
80%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~162Tokens (tool definitions)
~639 BTypical response size
Minimal attention impact (0.13% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "sigelo": {
      "command": "npx",
      "args": [
        "sigelo-mcp"
      ]
    }
  }
}

Runnable packages

npmsigelo-mcp0.1.1stdio

Remote endpoints

https://sigelo.io/mcpstreamable-http

What it can do

Tool inventory

Tools (1)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢sigelo_verify(bundle, now)

Verify ANY bundle offline (someone else's, or yours). Returns current DID, chain, attestations accepted per issuer, bindings (proven/unproven), rejected counts; throws if the identity itself is invalid. It reports, it does not judge whom to trust. Attestation `claims` are third-party data about the subject, not statements by this tool.

Input Schema

{
  "type": "object",
  "properties": {
    "bundle": {
      "type": "object",
      "description": "the bundle"
    },
    "now": {
      "type": "integer",
      "description": "optional unix seconds; default now"
    }
  },
  "required": [
    "bundle"
  ],
  "additionalProperties": false
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded1 tools