@signet-auth/mcp-tools

Standalone MCP server exposing Signet cryptographic tools over stdio. Use it from any MCP-compatible client without embedding Signet directly into your app.

Best for:

• Plugging Signet into Claude, Codex, or any MCP-compatible client
• Running signing and verification as an external tool server
• Quick experiments that need Signet over stdio

Use another package if:

• You want to embed Signet directly into app code: @signet-auth/core
• You want client-side MCP transport signing: @signet-auth/mcp
• You want server-side execution-boundary verification: @signet-auth/mcp-server

Tools

• signet_generate_keypair: Generate an Ed25519 keypair and return the public key.
• signet_sign: Sign a tool action and return a Signet receipt.
• signet_verify: Verify a Signet receipt against a public key.
• signet_content_hash: Compute the canonical SHA-256 content hash for JSON input.

Quick start

npx @signet-auth/mcp-tools

Or install globally:

npm install -g @signet-auth/mcp-tools
signet-mcp-tools

To avoid passing secret keys through MCP arguments, prefer setting:

export SIGNET_SECRET_KEY=...
signet-mcp-tools

Local Development

npm run build --workspace @signet-auth/mcp-tools
npm run test --workspace @signet-auth/mcp-tools
npm run start --workspace @signet-auth/mcp-tools

MCP Registry / Glama

This package is intended to be published with the MCP name:

io.github.prismer-ai/signet-mcp-tools

The registry manifest is in server.json.

Related packages

• @signet-auth/core — lower-level signing and verification primitives
• @signet-auth/mcp — sign outbound MCP requests on the client side
• @signet-auth/mcp-server — verify requests before execution on the server side
• Full documentation & all SDKs

If Signet is useful to you, star us on GitHub — it helps others discover the project.