Bidda Compliance README
The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Bidda Compliance listing page.
Bidda Sovereign Intelligence MCP Server
10,100+ source-verified regulatory compliance nodes across 39 sovereign pillars. Built to reduce hallucination by grounding every node in primary legal sources.
Actively maintained. Last reviewed 2026-08-12 - 10,108 nodes across 39 pillars, 25 MCP tools (server v1.6.0). Live counts always available via list_pillars() and GET https://bidda.com/mcp.
What is Bidda?
Bidda is a sovereign compliance intelligence registry. Every node traces to a primary legal source (avg 7 citations per node) and contains machine-executable deterministic logic, not summaries, not PDFs, not paraphrased commentary.
Pillars covered: EU AI Act · GDPR · NIST AI 600-1 · Basel III · HIPAA · DORA · FATF · SOC 2 · ISO 27001 · CCPA · PIPEDA · APRA CPS 234 · MiCA · POPIA · plus a MITRE layer across ATT&CK Enterprise/Mobile/ICS, D3FEND, ATLAS and CAPEC, and 150+ others across 39 compliance domains.
MCP Endpoint
Transport: Streamable HTTP (MCP 2025-03-26). No API key required for the discovery tier.
Tools (25)
Free discovery and intelligence (no key required)
| Tool | Description |
|---|---|
list_pillars | List all 39 compliance pillars with live node counts |
search_nodes | Search by keyword across 10,100+ nodes; returns title, ID, pillar, and BLUF (plain-language obligation) |
get_node | Fetch a specific node by ID; returns summary plus link to machine-executable workflow |
get_dependency_chain | Walk the prerequisite chain for a node (1 to 4 hops). Plan a full compliance posture from one entry node. |
get_crosswalk | Cross-framework mapping dimensions for a node (e.g. GDPR Art 17 to CCPA right-to-delete to POPIA Sec 24) |
get_latest_changes | Regulatory change feed: most recently updated nodes, optional pillar filter |
get_jurisdiction_bundle | All nodes that apply in a specific jurisdiction (EU, US, UK, AU, SG, IN, CA, CN, ZA, JP, BR and others) |
get_mitre_mapping | MITRE technique ID to Bidda node plus mapped NIST/ISO/PCI/HIPAA/NIS2/DORA controls. Across 6 frameworks. |
check_action_compliance | Pre-flight runtime check. Describe an intended action in natural language; get ranked applicable regulations plus LOW/MODERATE/HIGH risk indicator. |
browse_topics | Browse the registry by cross-cutting compliance topic (e.g. data breach notification, AI transparency) across every pillar and jurisdiction |
Subscriber tools (pass your Bidda key as api_key; a free trial counts)
| Tool | Description |
|---|---|
compare_jurisdictions | Compare how jurisdictions address a topic side by side, including where their numeric thresholds differ (e.g. a breach-notification deadline of 72 hours versus 30 days). Does not rank which is stricter. |
create_attestation | Create a signed, time-stamped record of which rules a person or AI agent relied on for a decision, with a public verify URL |
point_in_time | Signed record of which committed version of a rule was authoritative at a past date, anchored to the public history chain |
watch_changes | Subscribe to email or webhook alerts when a watched rule or pillar's primary source changes |
open_run | Open a run ledger for a whole task or conversation (for example a support-bot chat). Returns a run_id. |
record_run_entry | Append one tamper-evident entry to an open run: the rules consulted, the decision, and the user input as text or a private hash |
seal_run | Seal a run into one signed run receipt covering every entry, with a public verify URL anyone can check against Bidda's public key |
get_run | Fetch a run and its entries; a sealed run is publicly readable and reports whether its signature is valid |
consult_node | Governed runs: fetch a full node and record a verified, hash-pinned entry in an open run in one call, so the sealed receipt proves exactly which version of the rule the agent read |
get_audit_pack | Export a sealed run as one auditor-ready evidence pack: the signed receipt, the entry chain, and an independent integrity self-check |
drift_check | Check whether a cached compliance snapshot is still current: pass node ids (optionally with version or content hash) and get fresh, drifted, or withdrawn per node |
create_control_attestation | Signed record mapping one of your internal controls to the Bidda obligations it addresses, with owner, framework, status, and a public verify URL. An audit trail, not a determination of compliance. |
gap_check | Walk the public dependency graph from the nodes you cover to surface prerequisite obligations you may be missing |
obligation_deltas | Obligation-level feed of which primary sources changed or were withdrawn since a date, filterable by pillar or node |
oscal_assessment_results | Export a sealed governed run as a NIST OSCAL assessment-results document for GRC tooling |
The discovery responses for every free tool are free. Full vault unlock (deterministic_workflow, actionable_schema, full primary_citations) costs $0.01 per node via Skyfire JWT or USDC on Base. The subscriber tools require an active Bidda subscription, which includes a free trial.
Quick Start: Claude.ai / Claude Desktop / Cursor / any MCP HTTP client
Point your MCP client at:
That is it: no install, no API key, no config file for the discovery tier. The full server-info manifest is available at GET https://bidda.com/mcp (open in a browser to inspect available tools).
Run it locally (Node or Docker)
This repo also ships a runnable local stdio MCP server (server.js) that declares the full 25-tool surface. The free discovery and intelligence tools run locally by calling the public Bidda REST API, with no API key. The subscriber and governance tools are declared with their full schemas and execute on the hosted endpoint at https://bidda.com/mcp with your Bidda key. Use it when you want the server running on your own machine or CI.
With Node (18+):
With Docker:
Claude Desktop / Cursor config:
The local server declares all 25 tools. Ten run locally with no API key: list_pillars, search_nodes, get_node, get_dependency_chain, get_crosswalk, get_mitre_mapping, get_jurisdiction_bundle, browse_topics, get_latest_changes, and check_action_compliance. compare_jurisdictions uses your Bidda key when the comparison is gated. The remaining subscriber and governance tools (attestations, the run ledger, change alerts, drift checks, and OSCAL export) require a Bidda subscription key and execute on the hosted endpoint at https://bidda.com/mcp; a free trial counts.
Example Queries
Coverage (live numbers via list_pillars())
| Pillar | Approx. nodes |
|---|---|
| Cybersecurity | ~1,900 |
| Legal & IP Sovereignty | ~700 |
| Banking & Global Finance | ~580 |
| AI Governance & Law | ~570 |
| Medical & Healthcare | ~325 |
| Sustainability & ESG | ~285 |
| Workplace | ~280 |
| + 32 more pillars | (call list_pillars) |
For exact live counts, call list_pillars(). The manifest at GET https://bidda.com/mcp returns the current totals dynamically.
Full coverage browser: bidda.com/intelligence
How Bidda reduces hallucination
Nodes are produced by Bidda's internal deterministic pipeline: source parsers and verification scripts do the heavy lifting, AI assists only in a small, tightly-gated drafting step, and every node passes multiple independent verification gates before publication. The whole design exists to keep drift to a minimum.
Every node has:
- Primary legal citations: real instruments, real URLs, real section numbers (avg 7 per node)
- Deterministic workflow: machine-executable steps, not prose summaries
- Integrity hash: a cryptographic fingerprint of the node content
- Source integrity watcher: regular TLS and content fingerprint checks against live regulator URLs, results published at
/api/v1/registry-health.json - Verbatim mandate on amendments: every regulatory amendment is quote-justified against the source text before it can change a node
No inference without a regulatory anchor. No blog posts. No secondary commentary. No Wikipedia. Bidda is an information tool, not legal advice; review each rule and its primary source before relying on it.
CISA Secure by Design
Bidda has signed the CISA Secure by Design Pledge, the seven public goals the U.S. Cybersecurity and Infrastructure Security Agency asks software manufacturers to commit to, and publishes its evidence against each goal. Additional Bidda and CISA mappings:
- CISA CPG crosswalk: bidirectional mapping between Bidda compliance nodes and CISA's Cybersecurity Performance Goals: bidda.com/cisa/cpg-crosswalk
- CISA Free Tools catalogue: no-cost capabilities Bidda offers federal, SLTT and critical-infrastructure defenders: bidda.com/cisa/free
Registry Health
Live integrity-check results: source URL liveness, verification coverage percentage, regulatory change detection categories, with a public timestamp on the last sweep.
Links
- Website: bidda.com
- Developer docs: bidda.com/developers
- Full node registry: bidda.com/intelligence
- CISA programs: bidda.com/cisa
- Verify a node: bidda.com/verify
- Methodology: bidda.com/methodology
- Contact: info@bidda.com