Developer Builds MCP Linter and Discovers Security Issues in Anthropic Official Servers
A developer has created mcp-linter, a zero-dependency security linter for the Model Context Protocol (MCP) introduced by Anthropic. The tool helps developers avoid common pitfalls when building servers that connect Claude Desktop, Claude Code, Cursor, and autonomous agents to external resources.
The Model Context Protocol is built on JSON-RPC 2.0 and uses stdio transport for local servers. Any unintended output to stdout, such as a stray console.log statement, immediately breaks the protocol framing and causes the client to disconnect or fail parsing.
Four hidden problems identified
The article details four recurring issues. First, stdout pollution occurs when diagnostic messages are written to the wrong stream instead of stderr. Second, missing destructiveHint and readOnlyHint annotations allow agents to invoke dangerous tools like delete_user without human oversight. Third, tool poisoning lets attackers embed prompt-injection directives inside tool descriptions that are fed directly to the model. Fourth, incomplete input schemas without descriptions force the LLM to guess argument formats, raising hallucination rates.
The linter launches the target server in an isolated child process, performs an initialize handshake, requests tools/list, resources/list and prompts/list, then evaluates 34 rules before cleanly exiting. It produces a health score from 0 to 100 and can emit SARIF reports for GitHub Code Scanning.
Results on official Anthropic servers
- @modelcontextprotocol/server-everything scored 90/100; one parameter lacked a description.
- @modelcontextprotocol/server-memory scored 66/100; four parameters were missing descriptions and top-level instructions were absent.
- @modelcontextprotocol/server-filesystem scored only 38/100; 18 parameters had no descriptions, making correct tool calls significantly harder for models.
The project is available on npm and GitHub under the MIT license. Planned enhancements include support for SSE and WebSocket transports, context-budget auditing, and LLM-assisted schema repair.
Related articles
AI Agents Exploit PaperCut Flaw, Compromising 395 Organizations Across 48 Countries
PaperCut released a security bulletin on 27 August 2026. GreyNoise observed the first real-world code execution just four days later, with the operator moving from initial access to execution in under four hours. After the mass campaign launched, 11 organizations were compromised in only 26 seconds. In total, at least 440 PaperCut NG/MF instances belonging to 395 organizations were breached. The incident is detailed in the November report by Google Threat Intelligence Group and Mandiant, which examines the role of AI agents in the attacks. GTIG also discovered an automated exploit_agent system capable of handling exploitation without constant human input. Additional cases involved LLMjacking and unauthorized configuration changes in Claude Code repositories at cryptocurrency firms.
Google Threat Intelligence Group Warns of Fully Autonomous AI Cyberattacks Within Six Months
Google's Threat Intelligence Group (GTIG) has observed the first real-world instances of attackers using multi-agent AI frameworks to autonomously discover vulnerabilities, generate exploits, and compromise targets without human intervention. The discovery came from an exposed server running a framework called exploit_agent that analyzed software update logs from popular web applications to identify and exploit weaknesses. Four previously defensive tools—ARTEX, CAIRN, CyberStrikeAI, and HexStrike AI—have been repurposed for offensive operations, with documented cases targeting French media, U.S. aerospace, and cryptocurrency firms. GTIG projects that low-complexity automated attacks will become common within three months, while sophisticated fully autonomous operations are expected within six months. The report highlights how these systems compress patch windows, overwhelm security teams with AI-generated proof-of-concepts, and turn detailed vendor advisories into attack playbooks. Defenders are urged to minimize public exposure, accelerate patching cycles to weekly, and tightly control API keys to prevent LLMjacking.
OpenAI Rolls Out KYC, Hardware Keys and Tiered Access for Cybersecurity Tasks in GPT-6.2
OpenAI has introduced stricter access controls for GPT-6.2 Astra and Sol models when users attempt cybersecurity-related tasks. Certain legitimate security research and testing activities now trigger automatic blocks unless the user obtains Daybreak trusted access. The program requires paid subscriptions, FIDO2 hardware keys, Advanced Account Security, and identity verification through Persona. Developers report that even after meeting preliminary requirements, access to reduced refusal rates is not guaranteed and may require separate organizational approval. The changes stem from the models reaching Critical capability levels under OpenAI’s Preparedness Framework for dual-use cybersecurity skills. Similar verification processes previously led to account blocks for users of competing services such as Anthropic’s Claude.
Positive Technologies Releases PT Application Inspector Plugins 3.0.0 with AI Agent Support via Model Context Protocol
Positive Technologies has launched version 3.0.0 of its free PT Application Inspector plugins, introducing native support for AI agents through an integrated MCP server. The update enables AI agents to initiate vulnerability scans on entire projects or specific code changes, review findings, and assist developers in remediation directly within supported environments. Integration via the Model Context Protocol connects tools such as OpenCode, Claude Code, and Codex, providing agents with detailed vulnerability data including exploitation conditions. Static analysis remains the core detection method, while the new AI Hooks feature automatically validates modifications made by agents without requiring full project rescans. The How to Fix capability, which generates AI-driven remediation suggestions, is now available in Visual Studio Code in addition to JetBrains IDEs, with support for on-premise models to keep source code internal. Director of AppSec and WAF Products Anton Zhabolenko stated the goal is to embed vulnerability detection and fixing into the code generation workflow itself.