Categories › Security › Code & dependency scanning
10,065 source-verified compliance nodes, 39 pillars, 25 MCP tools (EU AI Act, GDPR, NIST, MITRE).
Remote server: your requests and data go to bidda.com. Claude Code: claude mcp add --transport http bidda-compliance https://bidda.com/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
list_pillars — List all compliance pillars in the Bidda Sovereign Intelligence registry with node counts. Use this first to discover available compliance dsearch_nodes — Search Bidda compliance nodes by keyword. Returns matching node summaries including a one-sentence BLUF (Bottom Line Up Front): the exact coget_node — Get a specific compliance node by its ID. Returns the node summary: title, compliance pillar, version, last updated, and BLUF. The full nodeget_dependency_chain — Walk the prerequisite chain for a compliance node. Given one node, returns its full dependency tree (the prior obligations an agent must satget_crosswalk — Return the cross-framework mapping dimensions for a node: which other regulations, standards, or jurisdictions this rule maps to (e.g. GDPR get_latest_changes — List the most recently updated compliance nodes: the regulatory change feed. Use to monitor incoming amendments, new guidance, or freshly adget_jurisdiction_bundle — Return all compliance nodes that apply in a specific jurisdiction (EU, US, UK, Australia, Singapore, India, Canada, China, South Africa, Japget_mitre_mapping — The MITRE Rosetta Stone. Given a MITRE technique ID across 5 frameworks (ATT&CK Enterprise, ATT&CK Mobile, ATT&CK ICS, D3FEND, ATLAS), returcheck_action_compliance — Pre-flight regulatory check. Agent describes an intended action in natural language ("process EU resident biometric data", "transfer health browse_topics — Browse the registry by cross-cutting compliance TOPIC (for example data breach notification, AI transparency, AML and KYC). Returns each topcompare_jurisdictions — Compare how different jurisdictions address a compliance topic, side by side, including where their numeric thresholds differ (for example acreate_attestation — Create a signed, time-stamped record of which Bidda rules a person or AI agent relied on for a decision. Returns a record ID and a public vepoint_in_time — Get a signed record of which committed version of a rule was authoritative at a specific past date, anchored to the public history chain. Uswatch_changes — Subscribe to regulatory change alerts: watch specific rules and/or whole pillars and get notified by email or webhook when their primary souopen_run — Open a run ledger: a signed, tamper-evident log of what an agent does across a whole task or conversation (for example a support-bot chat). record_run_entry — Append one entry to an open run: which Bidda rules the agent consulted, what it decided, and the end user's input (as text via note, or privconsult_node — The one-call governed turn: fetch the full vault node (this consumes one call on your key, exactly like unlocking a node) AND record a verifget_audit_pack — Export a run as a governance evidence pack: the signed receipt, every entry, a roll-up of the nodes consulted (with pinned versions/hashes),seal_run — Seal an open run into one signed Run Receipt covering every entry, with a public verify URL. Idempotent: sealing an already-sealed run returget_run — Fetch a run and its entries. The owner can read an open or sealed run (pass api_key); a sealed run is also publicly readable by id and repordrift_check — Check whether the compliance rules an agent has cached in its own memory are still current. Submit the node_id and the integrity hash you stcreate_control_attestation — Sign a tamper-evident record of one of YOUR OWN controls or policies and the Bidda obligation nodes it maps to. Each obligation is pinned togap_check — Given the compliance rules a team says it covers, return the prerequisite rules Bidda's dependency graph links to them that were NOT listed obligation_deltas — The obligation-level change feed: primary sources whose content changed (or whose node was withdrawn), mapped to the Bidda obligation nodes oscal_assessment_results — Export a governed run's evidence as a NIST OSCAL assessment-results document (the machine-readable format GRC and audit tooling consumes): rNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.