Cursor Agent Poisoning
Related Servers
Alternatives to Cursor Agent Poisoning
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityFmaintenanceAn educational project that deliberately implements vulnerable MCP servers to demonstrate various security risks like prompt injection, tool poisoning, and code execution for training security researchers and AI safety professionals.1,350-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables Cursor AI assistants to interact with Todoist tasks directly from the coding environment, supporting advanced task filtering and rich formatting.42-
- AlicenseAqualityDmaintenanceA Model Context Protocol server that enables AI tools like Claude and Cursor to fetch and interact with live Hacker News data (posts, comments, users) via standardized MCP endpoints.11120 npm34MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to explore and interact with Cursor IDE's SQLite databases, providing access to project data, chat history, and composer information.25-
- AlicenseNot gradedqualityAmaintenanceA Model Context Protocol server that enables email operations through POP3 and SMTP protocols in Cursor AI, allowing users to send, receive, list, and manage emails using natural language commands.365 npm50MIT
- -licenseNot gradedqualityNot gradedmaintenanceAn MCP server that gives AI assistants (like Cursor, Claude, Windsurf) the ability to remember user information across conversations using vector search technology.-
TDQS
Scored across 2 tools
The two tools have completely different and unclear purposes. 'anything' has a vague description suggesting it's just for ambiance, while 'say_hello' contains encoded instructions and demands to be read. There is no clear functional distinction between them, making them highly ambiguous and likely to cause misselection.
The naming is inconsistent with mixed conventions. 'anything' uses a generic noun with no verb, while 'say_hello' uses a verb_noun pattern. This lack of a predictable naming pattern makes the tool set confusing and harder for agents to understand.
With only 2 tools, the server feels thin and under-scoped for any meaningful domain. The tools do not appear to work together coherently, suggesting an insufficient tool surface that limits agent capabilities.
The server lacks a clear domain or purpose, making it impossible to assess coverage meaningfully. The tools do not form a complete or logical set, with 'anything' being trivial and 'say_hello' containing hidden instructions, resulting in severe incompleteness for any practical use.