Skip to content

Add Signet - cryptographic action signing for MCP tool calls - #3759

Closed
willamhou wants to merge 1 commit into
modelcontextprotocol:mainfrom
willamhou:add-signet
Closed

Add Signet - cryptographic action signing for MCP tool calls#3759
willamhou wants to merge 1 commit into
modelcontextprotocol:mainfrom
willamhou:add-signet

Conversation

@willamhou

Copy link
Copy Markdown

Add Signet to the Community Servers section.

What is Signet?

Signet signs every MCP tool call with Ed25519 and maintains a hash-chained audit log. It's a client-side SigningTransport that wraps any MCP transport — servers don't need to change.

import { generateKeypair } from "@signet-auth/core";
import { SigningTransport } from "@signet-auth/mcp";

const { secretKey } = generateKeypair();
const transport = new SigningTransport(innerTransport, secretKey, "my-agent");
// Every tools/call is now signed, receipt injected into params._meta._signet

Details

@olaservo

Copy link
Copy Markdown
Member

Thanks for contributing to the MCP servers repo!

We've retired the third-party server list from the README in favor of the MCP Registry — see #3950 for context. The Official Integrations and Community Servers sections no longer exist in the README, so this PR no longer has a target.

Going forward, please publish your server to the MCP Registry using the quickstart guide:
https://github.com/modelcontextprotocol/registry/blob/main/docs/modelcontextprotocol-io/quickstart.mdx

That's where server discovery now happens. Thanks for building on MCP!


Note: I'm working through the backlog with help from Claude Code to give everyone a prompt response.

@olaservo olaservo closed this Apr 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants