bidda-compliance

warnings

bidda.com

10,065 source-verified compliance nodes, 39 pillars, 25 MCP tools (EU AI Act, GDPR, NIST, MITRE).

https://bidda.com/mcpNo authMCP 2025-03-26v1.6.0last checked 24 Aug 2026spoke MCP on 2 of 2 checks (30 days)initialize in 781 ms

How to authenticate

Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	No auth
Protected-resource metadata	✕Not found Without it a client has to guess where the authorization server lives.
Anonymous access	Handshake succeeds; 25 tools listable
Credentials demanded in prose	✕compare_jurisdictions, create_attestation, point_in_time, watch_changes, open_run, record_run_entry, consult_node, seal_run, create_control_attestation, gap_check, obligation_deltas These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error.

What the probe found

warningTools needing credentials are listed without a challenge

11 of the 25 tools listed anonymously say in their own descriptions that they need an account or a key (compare_jurisdictions, create_attestation, point_in_time, watch_changes, open_run, record_run_entry, consult_node, seal_run, create_control_attestation, gap_check, obligation_deltas), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.

Tools

browse_topicscheck_action_compliancecompare_jurisdictionsconsult_nodecreate_attestationcreate_control_attestationdrift_checkgap_checkget_audit_packget_crosswalkget_dependency_chainget_jurisdiction_bundleget_latest_changesget_mitre_mappingget_nodeget_runlist_pillarsobligation_deltasopen_runoscal_assessment_resultspoint_in_timerecord_run_entryseal_runsearch_nodeswatch_changes

Contract history

24 Aug 2026v1.6.0first recorded contract

Get alerted when this contract changes

Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/bidda-compliance/badge.svg)](https://mcpi.app/servers/bidda-compliance)