Agent Negotiation MCP Server

The server implements a rate-limiting and tiered access system, but has significant security concerns that limit its trustworthiness for production use. The authentication middleware is functional but stored credentials (API keys) are written to plaintext JSON files in the user's home directory without encryption. Additionally, in-memory state management (_NEGOTIATIONS dict) has no expiration or cleanup mechanism, creating potential for memory exhaustion DoS attacks. The code lacks input validation on critical parameters (deal terms, agent names, bids JSON), and the "read-only" behavioral claims in docstrings are misleading since multiple tools modify internal state. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.

7 files analyzed · 18 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.