Bidda MCP MCP server

An official MCP server providing access to Bidda's source-verified regulatory intelligence. It allows AI agents to query compliance nodes, search regulations, and map dependencies across 39 domains including GDPR, EU AI Act, and NIST, helping reduce AI hallucination in regulated industries.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Bidda

MCP endpoint (Streamable HTTP)

https://bidda.com/mcp

Vendor documentation

What you can do with it

Search regulatory compliance nodes
List sovereign regulatory pillars
Get dependency chains for frameworks
Check action compliance status

Tools advertised by the last live check:

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

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http bidda-mcp https://bidda.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add bidda-mcp --url https://bidda.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable bidda-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "bidda-mcp": {
      "url": "https://bidda.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "bidda-mcp": {
      "type": "streamableHttp",
      "url": "https://bidda.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start bidda-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "bidda-mcp": {
      "type": "http",
      "url": "https://bidda.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http bidda-mcp https://bidda.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "bidda-mcp": {
      "url": "https://bidda.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "bidda-mcp": {
      "serverUrl": "https://bidda.com/mcp"
    }
  }
}

See all 248

Do you run Bidda MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing