Koskamo

Sigelo MCP

Provides an MCP server for AI agents to verify digital identities and attestations offline using Decentralized Identifiers (DIDs). It exposes a single tool, sigelo_verify, allowing agents to validate bundles and claims without requiring a wallet key, supporting identity portability and reputation management across platforms.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Sigelo MCP logo, by sigeloCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-07Published by sigelo
You need:Install: `npm i -g sigelo-agent@0.1.14` (Node ≥ 22.18, POSIX shell).Messages: allow `relay.sigelo.ai` (or yours) on 443
MCP endpoint (Streamable HTTP)
https://sigelo.io/mcp
Vendor documentation

What its tools do

1 tool, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Read-only (1)

1 of 1 have a description · 1 of 1 declare behavior hints · 1 of 1 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Verify agent identity bundles offline
  • Validate digital attestations from worlds
  • Check agent genesis and claims

Source and maintenance

Community listingRegistry 0.1.14
mcp-registry: io.github.csigelo/sigelo@0.1.14Source repositoryProject website
Maintenance checked

Protocol and capabilities

Server
sigelo.io 0.1.14
MCP protocol negotiated in check
2025-11-25
Tools
1 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

sigelo gives an AI agent one identity it owns: it proves who it is to any site or agent offline, no server or account; its attestations (reputation) survive leaving a platform and its DID a stolen key; it gets paid and pays in Monero without a wallet key; it messages other agents end to end, paired by an 8-character code. This endpoint checks such an identity: one tool, sigelo_verify, verifies any sigelo bundle offline-equivalently (SPEC §9) and returns the §9.1 result; use it before admitting, trusting or paying an agent. No login: this server keeps nothing of yours. No identity and no wallet here: for those install the sigelo plugin (github.com/csigelo/sigelo) or run npx sigelo-mcp. Experimental: wire sigelo/0 not frozen. Attestation `claims` are third-party data about the subject, not statements by this tool.

Tools

1 advertised

sigelo_verify — Verify a sigelo bundle
Advertised by the server during the last successful anonymous check.
Advertised read-only

Verify ANY bundle offline (someone else's, or yours). Returns current DID, chain, attestations accepted per issuer, bindings (proven, unproven, or superseded: under a DID before the last recovery, never pay it; a proven monero one names its network), rejected counts; throws if the identity itself is invalid. It reports, it does not judge whom to trust. Use it before admitting, trusting or paying an agent that showed you its bundle. Attestation `claims` are third-party data about the subject, not statements by this tool.

sigelo_verify input schema
{
  "type": "object",
  "required": [
    "bundle"
  ],
  "properties": {
    "now": {
      "type": "integer",
      "description": "optional unix seconds; default now"
    },
    "bundle": {
      "type": "object",
      "description": "the bundle"
    }
  },
  "additionalProperties": false
}
sigelo_verify annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1017 ms
95th percentile latency
1017 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1017 ms · metadata changed · 1 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http sigelo-mcp https://sigelo.io/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add sigelo-mcp --url https://sigelo.io/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable sigelo-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "sigelo-mcp": {
      "url": "https://sigelo.io/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "sigelo-mcp": {
      "type": "streamableHttp",
      "url": "https://sigelo.io/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start sigelo-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "sigelo-mcp": {
      "type": "http",
      "url": "https://sigelo.io/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http sigelo-mcp https://sigelo.io/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://sigelo.io/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "sigelo-mcp": {
      "serverUrl": "https://sigelo.io/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Sigelo MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 5,557