bidda-compliance MCP server
com.bidda/bidda-compliancebidda.comstreamable-httpv1.7.0Scanned
10,000+ source-verified compliance nodes, 39 pillars, 25 MCP tools (EU AI Act, GDPR, NIST, MITRE).
25 tools: 13 change things and 12 only read.
- Reads private data · 0
- Reads text others write · 25
- Can send data out · 1
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
13 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the bidda-compliance MCP server can do
The bidda-compliance MCP server is published by bidda.com, a domain the MCP Registry verified. It has 25 tools. It can create or change data (13 tools: check_action_compliance, create_attestation, point_in_time, watch_changes and 9 more), but cannot delete data. 12 tools only read.
25 tools bring in text other people can write (list_pillars, search_nodes, get_node and 22 more); 1 tool can send data out of your system (watch_changes).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 17, 2026, version 1.7.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
25 tools
Changes things 13Claude Code: ask
check_action_compliancePre-flight regulatory check.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Pre-flight regulatory check. Agent describes an intended action in natural language ("process EU resident biometric data", "transfer health records to a third-party AI vendor", "deploy autonomous trading model in Singapore") and receives a ranked list of regulations that may apply, plus a risk indicator (LOW/MODERATE/HIGH). The primary tool for runtime compliance gating in autonomous agent workflows.
Annotations the server declares
- title: Pre-flight compliance check
- readOnlyHint: true
- openWorldHint: true
consult_nodeThe 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 entry for it on an op…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 entry for it on an open run, in a single step. The entry pins the node to its current version + integrity hash, so the run receipt proves what the agent actually consulted. Use this instead of get_node when you are inside a run. Requires an active Bidda subscription: pass api_key.
Annotations the server declares
- title: Consult a rule and record it
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
create_attestationCreate a signed, time-stamped record of which Bidda rules a person or AI agent relied on for a decision.Reads text others writeNo findings
Why it is in this group
- The name "create_attestation" says "create": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 can later confirm the record has not been changed. Useful for agents that must keep an audit trail of what they checked. Requires an active Bidda subscription: pass api_key.
Annotations the server declares
- title: Sign a decision record
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
create_control_attestationSign a tamper-evident record of one of YOUR OWN controls or policies and the Bidda obligation nodes it maps to.Reads text others writeNo findings
Why it is in this group
- The name "create_control_attestation" says "create": a word for a change.
- The input takes a statement or command to run (input.statement), which can change anything it can reach.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 + integrity hash at signing time, so the record shows what the control was mapped against on that date. This is the design-side evidence ('we operate this control, mapped to these obligations'); run receipts are the operating-side evidence. Requires an active Bidda subscription: pass api_key.
Annotations the server declares
- title: Sign a control attestation
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
drift_checkCheck whether the compliance rules an agent has cached in its own memory are still current.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 grounded on each rule; get back, per rule, whether it is fresh, has drifted (content changed), or was withdrawn (instrument repealed) - so the agent re-grounds before acting on stale law. Included with every API tier; the per-call batch size scales with your plan. Pass api_key.
Annotations the server declares
- title: Check cached rules for drift
- readOnlyHint: true
- openWorldHint: true
gap_checkGiven 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 the prerequisite oblig…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 the prerequisite obligation' gaps - plus any covered rule the registry marks withdrawn. A coverage aid for a qualified reviewer; it does not rank or determine compliance. Requires an active Bidda subscription: pass api_key.
Annotations the server declares
- title: Check coverage for prerequisite gaps
- readOnlyHint: true
- openWorldHint: true
obligation_deltasThe obligation-level change feed: primary sources whose content changed (or whose node was withdrawn), mapped to the Bidda obligation nodes they affect, filterable by time, pillar,…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it The obligation-level change feed: primary sources whose content changed (or whose node was withdrawn), mapped to the Bidda obligation nodes they affect, filterable by time, pillar, or specific nodes. Use it to answer 'what obligations changed since I last reviewed?'. Requires an active Bidda subscription: pass api_key.
Annotations the server declares
- title: Get obligation-level changes
- readOnlyHint: true
- openWorldHint: true
open_runOpen 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).Reads text others writeNo findings
Why it is in this group
- The name "open_run" says "open": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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. Record one entry per turn with record_run_entry, then seal_run to get a single signed Run Receipt. Requires an active Bidda subscription: pass api_key.
Annotations the server declares
- title: Open a run ledger
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
oscal_assessment_resultsExport a governed run's evidence as a NIST OSCAL assessment-results document (the machine-readable format GRC and audit tooling consumes): reviewed-controls (the obligation nodes c…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Export a governed run's evidence as a NIST OSCAL assessment-results document (the machine-readable format GRC and audit tooling consumes): reviewed-controls (the obligation nodes consulted), observations (each pinned to its version + integrity hash), and props recording the independent integrity self-check. A sealed run is readable by id; a still-open run needs your api_key.
Annotations the server declares
- title: Export OSCAL assessment results
- readOnlyHint: true
- openWorldHint: true
point_in_timeGet a signed record of which committed version of a rule was authoritative at a specific past date, anchored to the public history chain.Reads text others write1 finding
Why it is in this group
- The description's first verb is "get": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "point_in_time" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "get": a word for reading.
Description, as the server wrote it 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 must show what a rule said at the moment it acted. Requires an active Bidda subscription: pass api_key.
Annotations the server declares
- title: Sign a point-in-time record
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
record_run_entryAppend 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).Reads text others writeNo findings
Why it is in this group
- The name "record_run_entry" says "run": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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). Each entry is hash-chained to the previous one. Requires an active Bidda subscription: pass api_key.
Annotations the server declares
- title: Record a run entry
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
seal_runSeal an open run into one signed Run Receipt covering every entry, with a public verify URL.Reads text others writeNo findings
Why it is in this group
- The name "seal_run" says "run": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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. Requires an active Bidda subscription: pass api_key.
Annotations the server declares
- title: Seal a run into a signed receipt
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
watch_changesSubscribe to regulatory change alerts: watch specific rules and/or whole pillars and get notified by email or webhook when their primary source changes.Reads text others writeCan send data outNo findings
Why it is in this group
- The description's first verb is "subscribe": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.channels): what the tool writes goes there.
- outboundThe input takes a URL (input.webhook_url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Subscribe to regulatory change alerts: watch specific rules and/or whole pillars and get notified by email or webhook when their primary source changes. Requires an active Bidda subscription: pass api_key.
Annotations the server declares
- title: Create a regulatory change alert
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 12Show 12 read-only tools
browse_topicsBrowse the registry by cross-cutting compliance TOPIC (for example data breach notification, AI transparency, AML and KYC).Reads text others writeNo findings
Why it is in this group
- The name "browse_topics" says "browse": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe name "browse_topics" says "browse": it reads web pages, which anyone can write.
- untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
Description, as the server wrote it Browse the registry by cross-cutting compliance TOPIC (for example data breach notification, AI transparency, AML and KYC). Returns each topic with how many rules carry it and across how many pillars and jurisdictions. Topics sit on top of the 39 pillars without replacing them. Free, no key required. Pass a topic string to drill into one.
Annotations the server declares
- title: Browse rules by topic
- readOnlyHint: true
- openWorldHint: true
compare_jurisdictionsCompare how different jurisdictions address a compliance topic, side by side, including where their numeric thresholds differ (for example a breach-notification deadline of 72 hour…Reads text others writeNo findings
Why it is in this group
- The name "compare_jurisdictions" says "compare": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Compare how different jurisdictions address a compliance topic, side by side, including where their numeric thresholds differ (for example a breach-notification deadline of 72 hours versus 30 days). It surfaces the real rules and numbers and does not rank which jurisdiction is stricter. Requires an active Bidda subscription: pass your key as api_key.
Annotations the server declares
- title: Compare jurisdictions
- readOnlyHint: true
- openWorldHint: true
get_audit_packExport 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-chain + Merkle inte…Reads text others writeNo findings
Why it is in this group
- The name "get_audit_pack" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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-chain + Merkle integrity self-check, and a coversheet mapping the receipt to the record-keeping obligations it supports (EU AI Act Art. 12/26, ISO/IEC 42001, NIST AI RMF). A sealed run is readable by id; a still-open run's draft pack needs your api_key.
Annotations the server declares
- title: Export a governance evidence pack
- readOnlyHint: true
- openWorldHint: true
get_crosswalkReturn the cross-framework mapping dimensions for a node: which other regulations, standards, or jurisdictions this rule maps to (e.g.Reads text others writeNo findings
Why it is in this group
- The name "get_crosswalk" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 right-to-delete → POPIA Section 24). Discovery returns the available dimensions; full mapping values are vault-gated.
Annotations the server declares
- title: Get cross-framework mapping
- readOnlyHint: true
- openWorldHint: true
get_dependency_chainWalk the prerequisite chain for a compliance node.Reads text others writeNo findings
Why it is in this group
- The name "get_dependency_chain" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 applies). Use this to plan a complete compliance posture: unlocking one node usually requires understanding 3-8 upstream nodes. Defaults to depth 2; max 4.
Annotations the server declares
- title: Get prerequisite chain
- readOnlyHint: true
- openWorldHint: true
get_jurisdiction_bundleReturn all compliance nodes that apply in a specific jurisdiction (EU, US, UK, Australia, Singapore, India, Canada, China, South Africa, Japan, Brazil and others).Reads text others writeNo findings
Why it is in this group
- The name "get_jurisdiction_bundle" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Return all compliance nodes that apply in a specific jurisdiction (EU, US, UK, Australia, Singapore, India, Canada, China, South Africa, Japan, Brazil and others). Use when an agent enters a new market and needs the full regulatory surface for that geography.
Annotations the server declares
- title: Get rules by jurisdiction
- readOnlyHint: true
- openWorldHint: true
get_latest_changesList the most recently updated compliance nodes: the regulatory change feed.Reads text others writeNo findings
Why it is in this group
- The name "get_latest_changes" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it List the most recently updated compliance nodes: the regulatory change feed. Use to monitor incoming amendments, new guidance, or freshly added rules. Filter by pillar to focus on a domain. Agents should call this on a schedule to keep compliance posture current.
Annotations the server declares
- title: Get regulatory change feed
- readOnlyHint: true
- openWorldHint: true
get_mitre_mappingThe MITRE Rosetta Stone.Reads text others writeNo findings
Why it is in this group
- The name "get_mitre_mapping" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 that technique plus its mapped compliance obligations: NIST 800-53 controls, ISO 27001 Annex A clauses, PCI DSS requirements, NIS2 articles, HIPAA Security Rule, DORA articles, NERC CIP, IEC 62443. The bridge between how SOC teams think (technique IDs) and how compliance teams think (control families). Free.
Annotations the server declares
- title: Map MITRE technique to controls
- readOnlyHint: true
- openWorldHint: true
get_nodeGet a specific compliance node by its ID.Reads text others writeNo findings
Why it is in this group
- The name "get_node" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 deterministic workflow, actionable schema, primary legal citations, dependency chain) is available at bidda.com.
Annotations the server declares
- title: Get compliance rule
- readOnlyHint: true
- openWorldHint: true
get_runFetch a run and its entries.Reads text others writeNo findings
Why it is in this group
- The name "get_run" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 signature is valid.
Annotations the server declares
- title: Get a run and its entries
- readOnlyHint: true
- openWorldHint: true
list_pillarsList all compliance pillars in the Bidda Sovereign Intelligence registry with node counts.Reads text others writeNo findings
Why it is in this group
- The name "list_pillars" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it List all compliance pillars in the Bidda Sovereign Intelligence registry with node counts. Use this first to discover available compliance domains before searching. Bidda has 10,102 cryptographically-verified nodes across 39 pillars, including a MITRE layer spanning 6 frameworks (ATT&CK Enterprise/Mobile/ICS, D3FEND, ATLAS, CAPEC) plus Banking, AI Governance, Cybersecurity, Healthcare, Legal, ESG and more.
Annotations the server declares
- title: List compliance pillars
- readOnlyHint: true
- openWorldHint: true
search_nodesSearch Bidda compliance nodes by keyword.Reads text others writeNo findings
Why it is in this group
- The name "search_nodes" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Search Bidda compliance nodes by keyword. Returns matching node summaries including a one-sentence BLUF (Bottom Line Up Front): the exact compliance obligation in plain language. Every node traces to a primary legal source (no hallucination). Examples: "Basel III capital", "GDPR data breach", "AML transaction monitoring", "SOC 2 Type II".
Annotations the server declares
- title: Search compliance rules
- readOnlyHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write25
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:34 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 13
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 13 tools that change things (13 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://bidda.com/mcp: tools/list returned 25 tools to an anonymous client, including check_action_compliance (write), create_attestation (write), point_in_time (write), watch_changes (write), open_run (write) and 8 more
Findings
Matches of fixed checks, with the text they matched.
- Warnpoint_in_time
The server marks "point_in_time" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "get": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:list_pillarsOnly readsdescription
Tools1 changed.~1 changedView diff
- Changed:list_pillarsOnly readsdescription
Install
Pinned to version 1.7.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http bidda-compliance https://bidda.com/mcpclaude mcp add --transport http bidda-compliance https://bidda.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__bidda-compliance__list_pillars",
"mcp__bidda-compliance__search_nodes",
"mcp__bidda-compliance__get_node",
"mcp__bidda-compliance__get_dependency_chain",
"mcp__bidda-compliance__get_crosswalk",
"mcp__bidda-compliance__get_latest_changes",
"mcp__bidda-compliance__get_jurisdiction_bundle",
"mcp__bidda-compliance__get_mitre_mapping",
"mcp__bidda-compliance__browse_topics",
"mcp__bidda-compliance__compare_jurisdictions",
"mcp__bidda-compliance__get_audit_pack",
"mcp__bidda-compliance__get_run"
],
"ask": [
"mcp__bidda-compliance__check_action_compliance",
"mcp__bidda-compliance__create_attestation",
"mcp__bidda-compliance__point_in_time",
"mcp__bidda-compliance__watch_changes",
"mcp__bidda-compliance__open_run",
"mcp__bidda-compliance__record_run_entry",
"mcp__bidda-compliance__consult_node",
"mcp__bidda-compliance__seal_run",
"mcp__bidda-compliance__drift_check",
"mcp__bidda-compliance__create_control_attestation",
"mcp__bidda-compliance__gap_check",
"mcp__bidda-compliance__obligation_deltas",
"mcp__bidda-compliance__oscal_assessment_results"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bidda-compliance. Review it before you use it.
Capability tags behind 25 rules
- mcp__bidda-compliance__list_pillars untrusted-input
- mcp__bidda-compliance__search_nodes untrusted-input
- mcp__bidda-compliance__get_node untrusted-input
- mcp__bidda-compliance__get_dependency_chain untrusted-input
- mcp__bidda-compliance__get_crosswalk untrusted-input
- mcp__bidda-compliance__get_latest_changes untrusted-input
- mcp__bidda-compliance__get_jurisdiction_bundle untrusted-input
- mcp__bidda-compliance__get_mitre_mapping untrusted-input
- mcp__bidda-compliance__check_action_compliance untrusted-input
- mcp__bidda-compliance__browse_topics untrusted-input
- mcp__bidda-compliance__compare_jurisdictions untrusted-input
- mcp__bidda-compliance__create_attestation untrusted-input
- mcp__bidda-compliance__point_in_time untrusted-input
- mcp__bidda-compliance__watch_changes untrusted-input, outbound
- mcp__bidda-compliance__open_run untrusted-input
- mcp__bidda-compliance__record_run_entry untrusted-input
- mcp__bidda-compliance__consult_node untrusted-input
- mcp__bidda-compliance__get_audit_pack untrusted-input
- mcp__bidda-compliance__seal_run untrusted-input
- mcp__bidda-compliance__get_run untrusted-input
- mcp__bidda-compliance__drift_check untrusted-input
- mcp__bidda-compliance__create_control_attestation untrusted-input
- mcp__bidda-compliance__gap_check untrusted-input
- mcp__bidda-compliance__obligation_deltas untrusted-input
- mcp__bidda-compliance__oscal_assessment_results untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.bidda/bidda-compliance/verify?hash=c9a9804953bc929faaa74acf18ff53c90e27e251c25d675b2d89140c6138d97f" | jq -e '.changed == false'Pinned hash c9a9804953bc, from Nov 17, 2026, 06:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.bidda/bidda-compliance/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.bidda/bidda-compliance)Source: MCP Registry. Synced Nov 17, 2026, 07:17 UTC.
bidda-compliance MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the bidda-compliance MCP server safe?
- No scan can promise that. What its definitions show: 25 tools, 13 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the bidda-compliance MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the bidda-compliance MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the bidda-compliance MCP server have?
- 25 tools: 13 write, 12 read. check_action_compliance, create_attestation, point_in_time, watch_changes, open_run, record_run_entry, consult_node, seal_run and 17 more.
Does the bidda-compliance MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the bidda-compliance MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): watch_changes.
Has the bidda-compliance MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.