mcp-behave
Related Servers
Alternatives to mcp-behave
- AlicenseAqualityBmaintenanceTransparent Go proxy that intercepts, signs, rate-limits, redacts, and audits all MCP JSON-RPC tool calls without modifying client or server. Stores to JSONL or SQLite with HMAC-SHA256 signatures.148Apache 2.0
Related Servers
- AlicenseAqualityCmaintenanceAudits any MCP server against the official spec, providing HMAC-signed conformity reports.632 PyPIMIT
- FlicenseNot gradedqualityDmaintenanceA sandbox MCP server for testing and debugging MCP tools and interactions via the MCP Inspector.-
- FlicenseNot gradedqualityDmaintenanceA basic MCP server implementation for testing purposes. Communicates via stdio and is designed to work with MCP-compliant clients.-
- FlicenseNot gradedqualityDmaintenanceDamn Vulnerable MCP Server for Security Researchers.7-
- AlicenseNot gradedqualityDmaintenanceA thin MCP server wrapper that automatically audits all tool calls via Attestive's AuditClient, logging decisions and enabling verification of the hash chain. It provides an example server with audited tools and demonstrates end-to-end recording and verification through the MCP protocol.MIT
- AlicenseAqualityBmaintenanceMCP server for https://oathe.ai security audits. Runtime behavioral analysis and security scanner for Ai systems. Check trust scores before installing MCP servers, plugins, or AI agent skills.5281 npm1MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct modes: inspect_manifest is static, read-only manifest inspection, while audit_server performs runtime execution and syscall tracing. Although both mention rug-pull detection, the descriptions make the static-vs-runtime boundary explicit.
Both names follow a consistent snake_case verb_noun pattern (inspect_manifest, audit_server). The verbs accurately reflect each tool's action.
Two tools is thin for the server's scope, though each covers a meaningful analysis mode (static and runtime). Additional tools for managing or comparing audit runs would make the set feel more complete.
The surface covers the core static and dynamic auditing workflows, including rug-pull detection. Minor gaps exist around retrieving, listing, or comparing prior audit results and managing baselines.