Hands-on MCP security, one problem at a time
September 9, 2026 · Granthinge
Dynamic client registration is the default answer for MCP, and it is the one enterprise reviewers question first. Here is how to decide which agent clients may connect to your server, and how to prove it.
Read moreSeptember 9, 2026 · Granthinge
Request logs are not audit. Here is an event schema for MCP tool calls that a customer's security team can ingest, correlate, and hand to an auditor, and how to get it out of your server without inventing a format.
Read moreSeptember 9, 2026 · Granthinge
The test sequence we run against an MCP server before handover: token fixtures, the four authorization rejections, exhaustive cross-tenant checks, prompt injection containment, session replay, and the record a reviewer reads.
Read moreAugust 24, 2026 · Granthinge
Resource indicators bind a token to one server; audience validation is what makes the binding real. How to verify the aud claim on every MCP request, with code and the failure modes reviewers look for.
Read moreAugust 20, 2026 · Granthinge
The discovery handshake is the first thing an MCP client runs against your server. A hands-on walkthrough of RFC 9728 protected resource metadata: the pointing 401, the well-known document, and how to test both.
Read more