Home / MCP registry index / com.bidda/bidda-compliance
com.bidda/bidda-compliance
com.bidda/bidda-compliance in the official MCP registry.
Endpoint https://bidda.com/mcp.
The registry describes it as: 10,065 source-verified compliance nodes, 39 pillars, 25 MCP tools (EU AI Act, GDPR, NIST, MITRE).
We read its 25 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
list_pillars search_nodes get_node get_dependency_chain get_crosswalk get_latest_changes get_jurisdiction_bundle get_mitre_mapping check_action_compliance browse_topics compare_jurisdictions create_attestation point_in_time watch_changes open_run record_run_entry consult_node get_audit_pack seal_run get_run drift_check create_control_attestation gap_check obligation_deltas oscal_assessment_results
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-bidda-bidda-compliance)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.