Everything here was measured by our prober or read from a registry. Nothing is self-reported.
30-day availability1/1 checks ok
30 days agotoday
Endpoints
https://bidda.com/mcpmcp streamable http · checked on a schedule
Registry facts
Not distributed through a package registry we index.
when
check
result
http
latency
detail
1 h ago
mcp initialize
ok
200
24 ms
server bidda-compliance 1.7.0 · protocol 2025-06-18 · 25 tools
Tools observed via MCP handshake
list_pillars — List all compliance pillars in the Bidda Sovereign Intelligence registry with node counts. Use this first to discover available compliance domains before search
search_nodes — Search Bidda compliance nodes by keyword. Returns matching node summaries including a one-sentence BLUF (Bottom Line Up Front): the exact compliance obligation
get_node — Get a specific compliance node by its ID. Returns the node summary: title, compliance pillar, version, last updated, and BLUF. The full node (machine-executable
get_dependency_chain — Walk the prerequisite chain for a compliance node. Given one node, returns its full dependency tree (the prior obligations an agent must satisfy before this one
get_crosswalk — Return the cross-framework mapping dimensions for a node: which other regulations, standards, or jurisdictions this rule maps to (e.g. GDPR Article 17 → CCPA ri
get_latest_changes — List the most recently updated compliance nodes: the regulatory change feed. Use to monitor incoming amendments, new guidance, or freshly added rules. Filter by
get_jurisdiction_bundle — Return all compliance nodes that apply in a specific jurisdiction (EU, US, UK, Australia, Singapore, India, Canada, China, South Africa, Japan, Brazil and other
get_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), return the Bidda node for
check_action_compliance — Pre-flight regulatory check. Agent describes an intended action in natural language ("process EU resident biometric data", "transfer health records to a third-p
browse_topics — Browse the registry by cross-cutting compliance TOPIC (for example data breach notification, AI transparency, AML and KYC). Returns each topic with how many rul
compare_jurisdictions — Compare how different jurisdictions address a compliance topic, side by side, including where their numeric thresholds differ (for example a breach-notification
create_attestation
Declared by sources
What the publisher says
Attributed to the source that supplied each field. Treated as claims, not facts.
No long description beyond the summary.
kind ← Official MCP Registry
name ← Official MCP Registry
summary ← Official MCP Registry
version ← Official MCP Registry
description ← Official MCP Registry
publisherName ← Official MCP Registry
Derived by Wellknown
Capabilities
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
4 h ago · declared · summary → "10,065 source-verified compliance nodes, 39 pillars, 25 MCP tools (EU AI Act, GDPR, NIST, MITRE)."
4 h ago · declared · description → "10,065 source-verified compliance nodes, 39 pillars, 25 MCP tools (EU AI Act, GDPR, NIST, MITRE)."
4 h ago · declared · publisherName → "com.bidda"
4 h ago · declared · version → "1.6.0"
4 h ago · declared · protocols → ["mcp"]
— 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 verify URL so anyone c
point_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. Useful when an agent m
watch_changes — Subscribe to regulatory change alerts: watch specific rules and/or whole pillars and get notified by email or webhook when their primary source changes. Require
open_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). Returns a run_id. Re
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 privately as input_hash)
consult_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 verified node_consulted e
get_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), an independent hash
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 returns the same receipt.
get_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 reports whether its signa
drift_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 stored when you last g
create_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 to its current version
gap_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 - the 'you missed th
obligation_deltas — The obligation-level change feed: primary sources whose content changed (or whose node was withdrawn), mapped to the Bidda obligation nodes they affect, filtera
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): reviewed-controls (th
Plan W-2 event staffing from 345 catalog entries; a coordinator confirms each order.