Sep 29, 2026 · 52 min · 11 segments
MCP servers are showing up on the internet without authentication, malicious tool definitions are being injected into trusted projects, and three security teams are defending the same environment…
Matthias ReinwarthHostGuest PanelistGuestOn another point, if I remember correctly, you said it's a de facto standard, but it's still coined and created by a vendor, by Anthropic, if I remember correctly.
If there are that many issues, challenges just right now, and it's so heavily used, shouldn't that just be fixed by the owner, by Anthropic?
But basically, yes, Anthropic has come up with the standard, and they created a reference implementation.
So if you are building an MCP server with Python or JavaScript or whatnot, you're probably using the SDK.
And the implementation in that SDK basically has We would call it a vulnerability.
So if we, as you said, if we think of MCP just another tool that gives access to resources, to anything that can be behind such an MCP server, so is it not an MCP vulnerability, in air quotes, but something where we see that it's just the focus point, the crystallization point for security problems that... come from mcp or do not so what is is mcp a new kind of security problem or is it just a new focal point where they happen
well again matthias you are hitting kind of the nail on the head and you are scratching a huge itch i had we discussed it earlier as well like People love inventing new labels for old things because labels sell.
But if you are following coping equals year-long kind of advice and say, stop looking at labels, look at functionalities and capabilities behind.
On another point, if I remember correctly, you said it's a de facto standard, but it's still coined and created by a vendor, by Anthropic, if I remember correctly.
If there are that many issues, challenges just right now, and it's so heavily used, shouldn't that just be fixed by the owner, by Anthropic?
But basically, yes, Anthropic has come up with the standard, and they created a reference implementation.
So if you are building an MCP server with Python or JavaScript or whatnot, you're probably using the SDK.
And the implementation in that SDK basically has We would call it a vulnerability.
So if we, as you said, if we think of MCP just another tool that gives access to resources, to anything that can be behind such an MCP server, so is it not an MCP vulnerability, in air quotes, but something where we see that it's just the focus point, the crystallization point for security problems that... come from mcp or do not so what is is mcp a new kind of security problem or is it just a new focal point where they happen
well again matthias you are hitting kind of the nail on the head and you are scratching a huge itch i had we discussed it earlier as well like People love inventing new labels for old things because labels sell.
But if you are following coping equals year-long kind of advice and say, stop looking at labels, look at functionalities and capabilities behind.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.