# sigelo (remote · sigelo.io)

One identity an AI agent owns: proves who it is offline, keeps its reputation, pays, messages agents

- Trust score: 86/100 (high trust)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `sigelo.io`: 86/100 (this document), [markdown](https://verifymcp.io/servers/csigelo-sigelo/sigelo.md), [page](https://verifymcp.io/servers/csigelo-sigelo/sigelo)
- npm · `sigelo-mcp`: 91/100, [markdown](https://verifymcp.io/servers/csigelo-sigelo/sigelo-mcp.md), [page](https://verifymcp.io/servers/csigelo-sigelo/sigelo-mcp)

## Channel facts

- Endpoint: `https://sigelo.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.14`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 343 tokens (~343/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the sigelo MCP server?

sigelo is a hosted endpoint at https://sigelo.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http csigelo-sigelo 'https://sigelo.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "csigelo-sigelo": {
      "url": "https://sigelo.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "csigelo-sigelo": {
      "type": "http",
      "url": "https://sigelo.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.csigelo-sigelo]
url = "https://sigelo.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "csigelo-sigelo": {
      "type": "remote",
      "url": "https://sigelo.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add csigelo-sigelo --url 'https://sigelo.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  csigelo-sigelo:
    url: "https://sigelo.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "csigelo-sigelo": {
      "Transport": "http",
      "Url": "https://sigelo.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add csigelo-sigelo -t streamable-http -u 'https://sigelo.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "csigelo-sigelo": {
      "type": "http",
      "url": "https://sigelo.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 86, 0)

- [security] Stability: 0.97 → pass
- [functional] Server version: 0.1.13 → 0.1.14

### 2026-11-02 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 85, 0)

- [functional] Server version: 0.1.10 → 0.1.13

### 2026-10-30 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 83, +1)

- [functional] Server version: 0.1.9 → 0.1.10

### 2026-10-24 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (1)

### `sigelo_verify` (~145 tokens)

Verify a sigelo bundle

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.

Input parameters:

- `bundle` (object, required): the bundle
- `now` (integer): optional unix seconds; default now

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/csigelo-sigelo/sigelo#diagnostics

## Score history

- 2026-11-05: 86
- 2026-11-04: 86
- 2026-11-03: 86
- 2026-11-02: 86
- 2026-11-01: 85
- 2026-10-31: 85
- 2026-10-30: 85
- 2026-10-29: 84
- 2026-10-28: 84
- 2026-10-27: 83
- 2026-10-26: 83
- 2026-10-25: 82
- 2026-10-24: 82
- 2026-10-23: 81
- 2026-10-22: 81
- 2026-10-21: 80
- 2026-10-20: 80
- 2026-10-19: 81
- 2026-10-18: 80
- 2026-10-17: 80
- 2026-10-16: 79
- 2026-10-15: 79
- 2026-10-14: 78
- 2026-10-13: 78
- 2026-10-12: 77
- 2026-10-10: 76
- 2026-10-07: 75
- 2026-10-04: 74

## Common questions

### What is the sigelo MCP server?

sigelo is an MCP server listed in the public MCP registry as io.github.csigelo/sigelo. One identity an AI agent owns: proves who it is offline, keeps its reputation, pays, messages agents. This page covers its hosted endpoint (https://sigelo.io/mcp).

### Is the sigelo MCP server safe to use?

sigelo scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the sigelo MCP server expose?

sigelo exposes 1 tool: sigelo_verify. Their descriptions and schemas cost roughly 145 tokens of context every time the server is loaded.

### Does the sigelo MCP server require authentication?

No. We connected to sigelo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the sigelo MCP server still maintained?

sigelo is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the sigelo MCP server?

VerifyMCP ran 13 checks on sigelo, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://sigelo.io/mcp
- Repository: https://github.com/csigelo/sigelo
- Website: https://sigelo.io/adopt.html#from-an-mcp-client
- Changelog RSS feed: https://verifymcp.io/servers/csigelo-sigelo/sigelo.xml
- Changelog JSON feed: https://verifymcp.io/servers/csigelo-sigelo/sigelo/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/csigelo-sigelo/sigelo.json
- HTML version of this page: https://verifymcp.io/servers/csigelo-sigelo/sigelo