Provides an identity layer for AI agents to manage reputation, encrypted messaging, and contact tiers.
Also known as csigelo/sigelo, sigelo-mcp
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.1.14
- Last commit
- Nov 14, 2026
- License
- MIT
What is sigelo MCP?
sigelo provides an identity layer for AI agents to manage reputation, encrypted messaging, and contact tiers.
Summary generated from the project's README
About sigelo MCP server
Sigelo provides an identity layer designed for AI agents to manage reputation, encrypted messaging, and contact tiers. It functions as a stdio MCP server through the command node server.mjs, though it can also be served over HTTP using the --http flag. Developers can integrate it into Claude Code via specific plugin commands. The server requires an identity file and uses a bearer token for HTTP requests, which is either provided via the SIGELO_MCP_TOKEN environment variable or generated and stored in sigelo-mcp-http.token.
This server offers a suite of contact tools for managing digital interactions. Users can handle end-to-end encrypted messages, manage presence settings, and organize contacts into tiers like own, friend, or quiet. It includes specialized functions for enrolling as an operator's worker and revoking contacts locally. While the stdio version provides full tool access, a remote version at sigelo.io/mcp allows for verification tasks using the sigelo_verify tool without requiring a local identity or key.
What you can do with it
- 1Secure messaging managementAn AI agent can send end-to-end encrypted messages to specific contacts.
- 2Contact tier organizationA developer can instruct an agent to categorize contacts into different privacy levels.
- 3Identity verificationAn agent can perform remote verification tasks using the hosted HTTP endpoint.
- 4Inbox monitoringAn agent can check for incoming messages and events filtered by contact tier.
Written from the project's README. Every use case is checked against a quote from it.
How to install sigelo MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall sigelo MCP in Claude Code
$ claude mcp add --env 'SIGELO_WALLET_TOKEN=<YOUR_SIGELO_WALLET_TOKEN>' sigelo -- npx -y sigelo-mcpInstall sigelo MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"sigelo": {
"command": "npx",
"args": [
"-y",
"sigelo-mcp"
],
"env": {
"SIGELO_WALLET_TOKEN": "<YOUR_SIGELO_WALLET_TOKEN>"
}
}
}
}Install sigelo MCP in VS Code
.vscode/mcp.json
{
"servers": {
"sigelo": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"sigelo-mcp"
],
"env": {
"SIGELO_WALLET_TOKEN": "<YOUR_SIGELO_WALLET_TOKEN>"
}
}
}
}Install sigelo MCP in VS Code CLI
$ code --add-mcp '{"name":"sigelo","type":"stdio","command":"npx","args":["-y","sigelo-mcp"],"env":{"SIGELO_WALLET_TOKEN":"<YOUR_SIGELO_WALLET_TOKEN>"}}'Install sigelo MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"sigelo": {
"command": "npx",
"args": [
"-y",
"sigelo-mcp"
],
"env": {
"SIGELO_WALLET_TOKEN": "<YOUR_SIGELO_WALLET_TOKEN>"
}
}
}
}Install sigelo MCP in Codex
$ codex mcp add sigelo --env 'SIGELO_WALLET_TOKEN=<YOUR_SIGELO_WALLET_TOKEN>' -- npx -y sigelo-mcpInstall sigelo MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.sigelo] command = "npx" args = ["-y", "sigelo-mcp"] [mcp_servers.sigelo.env] SIGELO_WALLET_TOKEN = "<YOUR_SIGELO_WALLET_TOKEN>"
Install sigelo MCP in Gemini CLI
$ gemini mcp add -s user -e 'SIGELO_WALLET_TOKEN=<YOUR_SIGELO_WALLET_TOKEN>' sigelo npx -- -y sigelo-mcpInstall sigelo MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"sigelo": {
"command": "npx",
"args": [
"-y",
"sigelo-mcp"
],
"env": {
"SIGELO_WALLET_TOKEN": "<YOUR_SIGELO_WALLET_TOKEN>"
}
}
}
}Configuration
SIGELO_WALLET_TOKENSecretThis agent's keeper bearer token, from the operator
SIGELO_IDENTITYIdentity file; default ~/.config/moadim/sigelo.local.json
SIGELO_WALLET_URLKeeper URL from the operator; with the token, the four wallet tools appear
| Name | Description | |
|---|---|---|
| SIGELO_WALLET_TOKEN | This agent's keeper bearer token, from the operator | Secret |
| SIGELO_IDENTITY | Identity file; default ~/.config/moadim/sigelo.local.json | |
| SIGELO_WALLET_URL | Keeper URL from the operator; with the token, the four wallet tools appear |
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work · What to fix for more points
- Source repository linked and reachablecsigelo/sigelo is public and reachablegithub.com/csigelo/sigelo ↗Pass
- Package names this repository as its sourcesigelo-mcp names csigelo/sigelo as sourcenpmjs.com/package/sigelo-mcp ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for sigelo-mcpnpmjs.com/package/sigelo-mcp/v/0.1.14#provenance ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-13github.com/csigelo/sigelo ↗Pass
- OpenSSF ScorecardOpenSSF Scorecard 6.0 / 10; weakest: Code-Review 0, Maintained 0, CII-Best-Practices 0scorecard.dev/viewer/?uri=github.com/csigelo/sigelo ↗Partial 9/15
- Package name not close to a popular packageNo popular package one edit away from sigelo-mcpPass
- No critical advisory in the package or its dependencies54 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the modelNot checked
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 547 msPass
sigelo MCP questions
How do I add sigelo MCP to Claude Code?
Run claude mcp add --env 'SIGELO_WALLET_TOKEN=<YOUR_SIGELO_WALLET_TOKEN>' sigelo -- npx -y sigelo-mcp in your terminal. Add --scope user to make it available in every project.
How do I add sigelo MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How can I use sigelo with Claude Code?
You can add it as a plugin using the command: claude plugin marketplace add csigelo/sigelo && claude plugin install sigelo@csigelo.
How do I authenticate when using the HTTP transport?
Every request requires an Authorization Bearer token, which can be provided via SIGELO_MCP_TOKEN, the --token flag, or a token stored in sigelo-mcp-http.token.