mcp-latchpoint
Related Servers
Alternatives to mcp-latchpoint
AlicenseAqualityCmaintenanceTracks buying and momentum signals for companies, such as funding rounds, senior hires, office openings, customer wins, and partnerships, with each event carrying its date.1014 npmMIT
Related Servers
- AlicenseNot gradedqualityBmaintenanceAudits MCP server configurations and packages for security risks such as typosquats, credential exposure, and malicious code, with zero dependencies and no execution.1MIT
- AlicenseNot gradedqualityBmaintenanceAudits MCP server configurations for security risks including capability inventory, SSRF, prompt injection, and drift detection. Works in read-only mode and can also be used as an MCP server to let AI agents audit their own attack surface.182 PyPI4MIT
- AlicenseAqualityBmaintenanceEnables static, read-only auditing of MCP servers’ registry entries, package metadata, client configurations, and tool definitions for supply-chain security indicators. It returns merged reports with transparent skipped checks and never executes the inspected code.6113 PyPIMIT
- FlicenseNot gradedqualityFmaintenanceScans MCP servers for security hardening issues including capability declarations, transport, and tool descriptions.1-
- AlicenseNot gradedqualityBmaintenanceLets an agent inspect and audit MCP servers before connecting to them, checking their exposed tools, prompts and resources for tool poisoning, shadowing, excessive permissions, leaked secrets and unsafe transports against 24 deterministic rules. Results are returned as findings with evidence, remediation and CWE/OWASP references, and can fail CI with SARIF, Markdown or standalone HTML reports.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceRead-only scanner that finds leaked secrets in MCP client configs, agent logs and shell history without printing values.Apache 2.0
TDQS
Scored across 2 tools
list_rules enumerates audit rules while scan analyzes a config file or directory—two clearly distinct purposes targeting different objects (rule metadata vs. actual files). No overlap or confusion.
list_rules follows a clean verb_noun pattern, but scan is a bare verb without a noun target, a minor deviation from the convention. Still readable and predictable overall.
Two tools is borderline thin for an audit/lint server; listing rules and running a scan are essential, but the surface feels minimal for the apparent scanning domain.
The core discover-then-scan workflow exists, but there's no way to fetch a single rule's detail, filter by severity, or apply/view remediation beyond what list_rules returns. Notable gaps limit deeper audit workflows.