# Bidda Compliance MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.bidda%2Fbidda-compliance
Registry id: `mcp-registry/com.bidda/bidda-compliance`
Status: live (checked 2026-10-27T01:42:53.015Z)

## Verdict

Bidda Compliance MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 722 ms median handshake and 0 outages in 90 days. Its agent-readiness grade is A (96/100) across 25 tools, costing an agent about 6,235 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 722 ms | 34% of MCP servers |
| p95 handshake latency | 2993 ms | — |
| Checks in 30 days | 4,958 | — |
| Outages, 90 days | 0 | — |
| Median recovery | — | — |
| Agent-readiness score | 96/100 (A) | 82% of MCP servers |
| Tools | 25 | — |
| Tool-list size for an agent | ~6,235 tokens | 36% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "bidda-compliance-mcp-server": {
      "type": "http",
      "url": "https://bidda.com/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http bidda-compliance-mcp-server https://bidda.com/mcp
```

## Tools (25)

- `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
- `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
- `compare_jurisdictions`: Compare how different jurisdictions address a compliance topic, side by side, including where their numeric thresholds differ (for example a breach-notification
- `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
- `create_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 verify URL so anyone c
- `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
- `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
- `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
- `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
- `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_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_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_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_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
- `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_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
- `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
- `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
- `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
- `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
- `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
- `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)
- `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.
- `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 
- `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

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.