Back to articles
Is that MCP request actually from your AI agent

Is that MCP request actually from your AI agent

via Dev.towillamhou

Is that MCP request actually from your AI agent? Last week we open-sourced Signet — cryptographic signing for every AI agent tool call. Someone asked a good question: the agent signs, but does the server verify? Fair point. v0.1 was one-sided. The agent signed every request, but the server didn't check. Like mailing a signed contract that nobody verifies on the other end. Better than nothing, but the trust chain is broken. This week we closed the loop. From one-sided to bilateral v0.1 Agent signs (one-sided) → proves the agent sent the request v0.2 Compound receipt (request + response bound) → proves the request and response are paired v0.3 Server verification → server can verify "this request was signed by a specific agent" v0.4 Bilateral co-signing → agent signs the request, server signs the response, both hold proof Server verification: 3 lines Add this to your MCP server handler: import { verifyRequest } from " @signet-auth/mcp-server " ; server . setRequestHandler ( CallToolReques

Continue reading on Dev.to

Opens in a new tab

Read Full Article
2 views

Related Articles