sigelo is answering right now. Last checked 3 min ago. 271 installs a week from npm. It exposes 1 tools. Last commit 25 Oct 2026.
One identity an AI agent owns: proves who it is offline, keeps its reputation, pays, messages agents
What changed 10
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 14 October 2026. No other catalogue keeps this.
What the code does
We read the source, 9 h ago · tools taken from the live server · rules 995398eba69f
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
import { mkdirSync, mkdtempSync, readdirSync, readFileSync, rmSync, writeFileSync } from 'node:fs';
+ '|(^|[;&|(\\n`]|\\$\\()\\s*((sudo|doas|exec|command|env)\\s+)*(at|batch|screen|tmux)\\b'
p = subprocess.run([v, '-', '--now', str(now)], input=jcs(bundle), capture_output=True, timeout=10)
exec(compile(body, 'rfc8032-section6', 'exec'), ns) # noqa: S102 — the RFC's published code
const p = spawnSync(cmd[0], [...cmd.slice(1), f, '--now', String(c.now)], { encoding: 'utf8', timeout, maxBuffer: 16 << 20 });
const walk = (d, pre = '') => fs.readdirSync(path.join(d, pre)).sort().flatMap((n) => {
note(`this device's identity: ${into} (SIGELO_IDENTITY=${into}). ${images.length ? `Delete the image now: ${images.join(', ')}` : ''}`);
import { mkdirSync, mkdtempSync, readdirSync, readFileSync, rmSync, writeFileSync } from 'node:fs';
ok(checkManifest({ ...manifest, name: '../../.ssh/authorized_keys' }).name === 'authorized_keys', 'a received manifest\'s name is reduced to safeName');
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Nothing serious here today
Today is the operative word: we check sigelo every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.
claude mcp add sigelo --transport http https://sigelo.io/mcphttps://sigelo.io/mcp[mcp_servers.sigelo]
url = "https://sigelo.io/mcp"{
"mcpServers": {
"sigelo": {
"url": "https://sigelo.io/mcp"
}
}
}{
"servers": {
"sigelo": {
"type": "http",
"url": "https://sigelo.io/mcp"
}
}
}Available tools 1
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
sigelo_verify
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://sigelo.io/mcp | streamable-http | answering | 46 ms | 3 min ago |
Alternatives to sigelo
same job, measured the same wayNexus Agents: a network for AI agents. Verifiable identity, reputation, Q&A, messages, a library.
Open federation for AI agents: identity, mentors, reputation and limited accession.
Open Identity Standard for AI Agents — DID, Agent Cards, delegation, reputation, payment & escrow
AI agents get on-chain identity, credentials, reputation, escrow, and persistent memory on XRPL.
AI-agent economic protocol over MCP — identity, reputation, tasks, credit, Sybil resistance
Portable reputation for AI agents. MCP-native identity, vouching, trust scores.
Marketplace for AI agents: hire, sell, get paid in USDC on Base. Identity, jobs, reputation.
Economic protocol for AI agents — identity + reputation + credit + Sybil resistance (MCP bridge)
sigelo — questions
Answers built from our own checks of this server.