Skip to content

BDK Native MCP server

com.thebdk/bdk-nativethebdk.comstreamable-httpv2026-11-17-ios-badgeScanned

Turn a web app from Lovable, Bolt, Replit, Base44, Bubble or any stack into iOS and Android apps.

11 tools: 6 can delete or cancel things, 3 change things and 2 only read.

Tools: 6 delete, 0 irreversible, 3 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 11
  • Can send data out · 0
  • 11 findings

Tools listed without sign-in. Remote posture

With Anlyon

6 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 BDK Native MCP server can do

The BDK Native MCP server is published by thebdk.com, a domain the MCP Registry verified. It has 11 tools. It can delete or cancel things (6 tools: bdk_next, bdk_configure, bdk_setup_preview, bdk_check and 2 more) and create or change data (3 tools: bdk_create_project, bdk_upload and bdk_estimate). 2 tools only read.

1 tool reads private data (bdk_projects); 11 tools bring in text other people can write (bdk_whoami, bdk_projects, bdk_next and 8 more).

The fixed checks matched 11 findings (credentials-mention, long-description and annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 4 times since Anlyon Radar first saw them.

Last scanned Nov 18, 2026, version 2026-11-17-ios-badge.

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.

11 tools

Deletes or cancels 6Claude Code: deny
  • bdk_buildRequest a build or rebuild only after explicit approval of that request and the saved settings.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "request": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    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
    Request a build or rebuild only after explicit approval of that request and the saved settings. A first build requires confirm_build:true after the customer says yes. A ledger rebuild consumes one banked rebuild: pass build_kind:rebuild and confirm_consumes_rebuild:true. free_rebuild is legacy-only. action:status lists delivered history, not the current request; use bdk_next. action:download returns available Android/iOS build download links; fetch and share them with the customer, as in the portal’s Your Builds. Android archives contain an .aab for Play Console, not a phone installer; iOS builds are uploaded to App Store Connect for TestFlight. Never paste keystore passwords or secrets into chat. BDK builds and signs; the customer submits. Holds/checks can refuse a request. Portal-editable identity fields follow the portal metadata rules; locked identity changes require BDK admin.

    Annotations the server declares

    • title: Request build or read delivery
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • bdk_checkRead health checks and health_checked_at, not build execution status.Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "..., after the customer changed screens or credentials on the portal, or when the customer ask..."

      What this check looks for
    Description, as the server wrote it
    Read health checks and health_checked_at, not build execution status. run:true schedules an asynchronous check: use it when no snapshot exists yet, after the customer changed screens or credentials on the portal, or when the customer asks for a new check; otherwise read without run. If scheduled, re-read without run after a minute. If not scheduled, say so and use the portal. A passing check is an observation, not compatibility or store approval.

    Annotations the server declares

    • title: Read or schedule health check
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • bdk_checkoutCreates a Stripe-hosted checkout page that the customer reviews and pays on themselves; this tool never charges, never sees card details and never completes a payment.Reads text others write1 finding

    Why it is in this group

    • The name "bdk_checkout" says "checkout": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 2,571 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...oval does not authorize a build request. Legacy polling uses checkout_session_id."

      What this check looks for
    Description, as the server wrote it
    Creates a Stripe-hosted checkout page that the customer reviews and pays on themselves; this tool never charges, never sees card details and never completes a payment. Start or poll a project purchase only after purchase approval. First read bdk_next.commerce and confirm the customer’s platform via bdk_next confirm_product; a default Both is not consent. Checkout requires recorded platform confirmation and refuses purchases when an unused entitlement or active request already covers them. Same-platform repeat purchases are refused; rebuild purchases require first delivery. Only an explicit customer request to buy an extra rebuild permits confirm_extra_rebuild:true despite an unused rebuild or active request. Ledger start selects the current offer for kind (build or rebuild) and the confirmed product_selected; pass kind explicitly, otherwise it defaults to rebuild after delivery and build before delivery. Optional promotion_code comes from the customer. Omit attempt for the stable agent-1 default key scoped to project and current offer, preserving existing checkout keys. Reuse the same attempt for retries. Use a new attempt only for an approved new purchase or when the returned recovery guidance explicitly directs it; never bypass an unresolved purchase. This is a gateway preflight check, not a global purchase lock. An existing open checkout returns resumed:true; paid purchases return status:paid with no payment URL and guidance to bdk_next/bdk_build. An expired unpaid checkout gets at most one replacement start. Completed-but-unverified and disputed purchases stop; never change attempt to bypass an unresolved purchase. If a fulfilled purchase has no usable credit left, or the customer explicitly approves an extra rebuild, next_step directs a new attempt (and confirm_extra_rebuild:true for rebuilds). On an unreadable replay, retry the same start with the same attempt. Resolve ambiguous outcomes through bdk_next and the portal’s Purchases tab; use portal support if the purchase cannot be reconciled. Inspect status and next_step before sharing a URL; paid responses have no payment URL. When quote is present, tell the customer quote.total_minor (minor units of quote.currency) before relaying the URL; when quote is absent, the amount is shown on Stripe’s page. Relay only your own returned Stripe URL unchanged; never request card details in chat. Retain purchase_id and poll it until fulfilled:true; paid with fulfilled:false is not usable. Purchase approval does not authorize a build request. Legacy polling uses checkout_session_id.

    Annotations the server declares

    • title: Start or poll purchase
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • bdk_configureChange a project's settings after the customer approves each value.Reads text others write1 finding

    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 destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 2,925 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...ing status, not listing copy. Field reference: https://thebdk.com/agent/skill.md."

      What this check looks for
    Description, as the server wrote it
    Change a project's settings after the customer approves each value. Writable keys: app_name, launch_link, product_selected, statusbar_color, push_prompt_mode, push_enabled, app_icon_link, app_orientation_ios, app_orientation_android, app_tracking_ios, background_audio_ios, background_location_enabled_android, location_precision_android, target_devices_ios, message_apptracking, message_camera, message_contacts, message_geolocation, message_medialibrary, message_microphone, message_photos, android_notification_icon_zip, tnc_accepted, app_platform, app_platform_name, feature_nfc_enabled_ios, feature_nfc_enabled_android, feature_nfc_usage_description, feature_nfc_launch_domain, feature_nfc_launch_path_prefix, feature_badge_autoclear_ios, feature_badge_autoclear_android, feature_push_data_enabled, feature_health_read_enabled_ios, feature_health_read_enabled_android, feature_health_read_types, feature_health_read_usage_description, feature_health_read_privacy_policy_url, feature_share_inbound_enabled, feature_share_inbound_types, feature_share_inbound_upload_url, feature_share_inbound_max_size_mb, feature_share_inbound_open_app, ios_listing_info, android_listing_info, apple_team_name, apple_entity_type, apple_account_holder_email, onesignal_app_id, apple_team_id, ios_app_listing_id, ios_app_bundle_id, android_package_name. Any other key is refused with a reason and a fix. product_selected is iOS, Android or Both, only after asking the customer; bdk_next confirm_product records the confirmation checkout needs. Set tnc_accepted:true only after explicit acceptance of https://thebdk.com/terms for this project; a sign-in or connection approval is not terms acceptance. launch_link changes installed apps: obtain approval for the exact URL. push_prompt_mode is automatic/manual and updates installed apps on their next config read. statusbar_color updates installed apps immediately through the portal Additional Tools live action, including before first delivery. push_enabled is boolean or Yes/No and needs a rebuild; run bdk_check with run:true afterwards. feature_badge_autoclear_ios accepts Yes/No strings: absent or Yes clears the iOS app icon badge on open (default); No keeps it. It only matters while push is on (OneSignal); Android badge auto-clear is independent of push. App icons must first be uploaded with bdk_upload; configure accepts this project’s sb://project-files agent-upload reference and revalidates its bytes. External icon URLs are refused. Keep secrets on the portal. Returns applied, refused and failed keys. After an upstream error it re-reads affected settings; failed live propagation remains unconfirmed. Preserve applied results on partial failure. Portal-editable identity fields follow the portal metadata rules; locked identity changes require BDK admin. Listing fields describe existing listing status, not listing copy. Field reference: https://thebdk.com/agent/skill.md.

    Annotations the server declares

    • title: Change project settings
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • bdk_nextRead workflow state and next steps; call again after each action.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    • The server marks it destructive (destructiveHint: true).

    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
    Read workflow state and next steps; call again after each action. confirm_product writes and records the customer-confirmed iOS / Android / Both choice: ask first. Checkout requires recorded confirmation matching the saved platform, even when the saved default already matches the customer's choice. If confirmation is missing or mismatched, send the answer as confirm_product, then re-read. A purchased platform can be locked: use the purchased platform or portal support; do not loop through bdk_configure. Milestones summarise project progress; unknown health or confirmation remains unknown. Preview refers to this project or its matching launch domain and is not proof of phone testing. allowed_tools is advisory. can_request_now does not guarantee the request will be accepted.

    Annotations the server declares

    • title: Read next steps or confirm platform
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • bdk_setup_previewCreation requires intent:new; legacy app_link + preview_id updates that selected preview.Reads text others write2 findings

    Why it is in this group

    • The name "bdk_setup_preview" says "preview": a word for reading.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...to add another. Password protection and credentials, including clearing them, stay human-on..."

      What this check looks for
    • Warn

      The server marks "bdk_setup_preview" destructive (destructiveHint: true), and its name says "preview", a word for reading.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":true,"idempotentHint":false,"openWorldHint":true}; The name "bdk_setup_preview" says "preview": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Creation requires intent:new; legacy app_link + preview_id updates that selected preview. list returns account preview names, published URLs, IDs and creation times. new calls the portal preview-manage create path (same-URL reuse and 20-preview cap); update requires the customer-selected preview_id and replaces that link. Published-link checks reject editor and builder-share links. At cap: Delete an existing preview to add another. Password protection and credentials, including clearing them, stay human-only on the portal. Pairing stays on the customer’s phone, never in chat. On iPhone only own previews open.

    Annotations the server declares

    • title: List, create or update previews
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Changes things 3Claude Code: ask
  • bdk_create_projectCreate a project after approval of the reference label and published app URL.Reads text others writeNo findings

    Why it is in this group

    • The name "bdk_create_project" 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 project after approval of the reference label and published app URL. project_name is a reference label, not the home-screen app name; that starts as the website hostname until configured. Duplicates by reference label or site host return candidates: ask the customer to choose create_new or use_existing with project_code; never reuse automatically. For an owner preview, pass from_preview_id to read editable prefill, then submit its observed_website_link. A same_site_project conflict requires explicit link_existing:true with project_code or false to create separately.

    Annotations the server declares

    • title: Create project
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • bdk_estimateWith project_code, verify access and read ledger offers; report lookup failure rather than substituting a standard quote.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
    With project_code, verify access and read ledger offers; report lookup failure rather than substituting a standard quote. A legacy project without product returns legacy_project; with product, it returns standard prices. Without project_code, product also selects standard prices, not eligibility. offer.unit_amount is in minor units of currency. The tool never creates a payment URL. BDK builds and signs; the customer submits.

    Annotations the server declares

    • title: Read current offers
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • bdk_uploadImport a direct public HTTPS PNG, JPEG or WebP image up to 8 MB, without redirects; this does not assign a screen.Reads text others write5 findings

    Why it is in this group

    • The name "bdk_upload" says "upload": 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.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...ortal for local files and screens. kind:credential returns portal instructions, never acce..."

      What this check looks for
    • Info

      The input schema at properties.source_url.description mentions "credential".

      Matched text

      inputSchema.properties.source_url.description: "...stomer approval; not a private asset or credential URL."

      What this check looks for
    • Info

      The input schema at properties.kind.description mentions "credential".

      Matched text

      inputSchema.properties.kind.description: "asset imports a public image; credential returns a portal-entry handoff, never a..."

      What this check looks for
    • Info

      The input schema at properties.kind.enum[1] mentions "credential".

      Matched text

      inputSchema.properties.kind.enum[1]: "credential"

      What this check looks for
    • Info

      The input schema at properties.credential.description mentions "Credential".

      Matched text

      inputSchema.properties.credential.description: "Credential category for portal-entry instructions;..."

      What this check looks for
    Description, as the server wrote it
    Import a direct public HTTPS PNG, JPEG or WebP image up to 8 MB, without redirects; this does not assign a screen. Explicit purpose:app_icon decodes actual bytes and enforces the portal’s 1024×1024 PNG/JPG, no transparency or animation requirements. Omitted purpose or purpose:image accepts other images without icon validation; never use an unvalidated image as an icon. Use the portal for local files and screens. kind:credential returns portal instructions, never accepts the secret itself. OneSignal, Firebase and APNs are needed only while push is on; App Store Connect credentials still apply for iOS. After portal credential entry, run bdk_check with run:true and re-read the result and timestamp.

    Annotations the server declares

    • title: Import asset or get key-entry instructions
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • bdk_projectsList projects or read a status/progress/health snapshot, not full settings or credentials.Reads private dataReads text others write1 finding

    Why it is in this group

    • The description's first verb is "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "credential": it reads secrets.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...s/health snapshot, not full settings or credentials. Use bdk_next.commerce for ledger entit..."

      What this check looks for
    Description, as the server wrote it
    List projects or read a status/progress/health snapshot, not full settings or credentials. Use bdk_next.commerce for ledger entitlement and current requests. Do not infer payment or delivery from legacy status, paid_for_service, requested_build, build_complete, rebuild_credits or free_rebuild_expires_at.

    Annotations the server declares

    • title: Read projects
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • bdk_whoamiRead the signed-in user and their projects, with the project codes the other tools take.Reads text others writeNo findings

    Why it is in this group

    • The name "bdk_whoami" says "whoami": 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
    Read the signed-in user and their projects, with the project codes the other tools take. product_selected can be an unconfirmed default. Legacy status is not ledger entitlement; bdk_next.commerce has the entitlement.

    Annotations the server declares

    • title: Read account
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: 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 outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write11
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
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.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:22 UTC, unchanged since Nov 13, 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
9
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.thebdk.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://vwilkatgaasdppgkaatq.supabase.co/auth/v1
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 9 tools that change things (6 destructive, 3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.thebdk.com/mcp: tools/list returned 11 tools to an anonymous client, including bdk_next (destructive), bdk_configure (destructive), bdk_setup_preview (destructive), bdk_check (destructive), bdk_checkout (destructive) and 4 more

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 10 to 9
    • RFC 9728 protected resource metadata: https://mcp.thebdk.com/.well-known/oauth-protected-resource to https://mcp.thebdk.com/.well-known/oauth-protected-resource/mcp

Findings

Matches of fixed checks, with the text they matched.

1 warn10 info
  • The server marks "bdk_setup_preview" destructive (destructiveHint: true), and its name says "preview", a word for reading.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":true,"idempotentHint":false,"openWorldHint":true}; The name "bdk_setup_preview" says "preview": a word for reading.

    What this check looks for
  • The description mentions "credentials".

    Matched text

    description: "...s/health snapshot, not full settings or credentials. Use bdk_next.commerce for ledger entit..."

    What this check looks for
  • The description is 2,925 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...ing status, not listing copy. Field reference: https://thebdk.com/agent/skill.md."

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "...ortal for local files and screens. kind:credential returns portal instructions, never acce..."

    What this check looks for
  • The input schema at properties.source_url.description mentions "credential".

    Matched text

    inputSchema.properties.source_url.description: "...stomer approval; not a private asset or credential URL."

    What this check looks for
  • The input schema at properties.kind.description mentions "credential".

    Matched text

    inputSchema.properties.kind.description: "asset imports a public image; credential returns a portal-entry handoff, never a..."

    What this check looks for
Show 5 more findings
  • The input schema at properties.kind.enum[1] mentions "credential".

    Matched text

    inputSchema.properties.kind.enum[1]: "credential"

    What this check looks for
  • The input schema at properties.credential.description mentions "Credential".

    Matched text

    inputSchema.properties.credential.description: "Credential category for portal-entry instructions;..."

    What this check looks for
  • The description mentions "credentials".

    Matched text

    description: "...to add another. Password protection and credentials, including clearing them, stay human-on..."

    What this check looks for
  • The description mentions "credentials".

    Matched text

    description: "..., after the customer changed screens or credentials on the portal, or when the customer ask..."

    What this check looks for
  • The description is 2,571 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...oval does not authorize a build request. Legacy polling uses checkout_session_id."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 10 -> 9; RFC 9728 protected resource metadata: https://mcp.thebdk.com/.well-known/oauth-protected-resource -> https://mcp.thebdk.com/.well-known/oauth-protected-r…View diff
    • Tools that change things, listed without credentials: 10 to 9
    • RFC 9728 protected resource metadata: https://mcp.thebdk.com/.well-known/oauth-protected-resource to https://mcp.thebdk.com/.well-known/oauth-protected-resource/mcp
  3. Tools1 removed, 11 changed.−1 removed~11 changedView diff
  4. Tools9 changed.~9 changedView diff
  5. Tools4 changed.~4 changedView diff

Install

Pinned to version 2026-11-17-ios-badge. Values in angle brackets are yours to fill in.

claude mcp add --transport http bdk-native https://mcp.thebdk.com/mcp
claude mcp add --transport http bdk-native https://mcp.thebdk.com/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__bdk-native__bdk_whoami",
      "mcp__bdk-native__bdk_projects"
    ],
    "ask": [
      "mcp__bdk-native__bdk_create_project",
      "mcp__bdk-native__bdk_upload",
      "mcp__bdk-native__bdk_estimate"
    ],
    "deny": [
      "mcp__bdk-native__bdk_next",
      "mcp__bdk-native__bdk_configure",
      "mcp__bdk-native__bdk_setup_preview",
      "mcp__bdk-native__bdk_check",
      "mcp__bdk-native__bdk_checkout",
      "mcp__bdk-native__bdk_build"
    ]
  }
}

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 bdk-native. Review it before you use it.

Capability tags behind 11 rules
  • mcp__bdk-native__bdk_whoami untrusted-input
  • mcp__bdk-native__bdk_projects private-data, untrusted-input
  • mcp__bdk-native__bdk_next untrusted-input
  • mcp__bdk-native__bdk_create_project untrusted-input
  • mcp__bdk-native__bdk_configure untrusted-input
  • mcp__bdk-native__bdk_upload untrusted-input
  • mcp__bdk-native__bdk_setup_preview untrusted-input
  • mcp__bdk-native__bdk_estimate untrusted-input
  • mcp__bdk-native__bdk_check untrusted-input
  • mcp__bdk-native__bdk_checkout untrusted-input
  • mcp__bdk-native__bdk_build 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.thebdk/bdk-native/verify?hash=0ed119ed5853afd2185d1d77e5e685096ba94bd098d3ad7ca637a7b9f4c6a406" | jq -e '.changed == false'

Pinned hash 0ed119ed5853, from Nov 18, 2026, 17:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.thebdk/bdk-native/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.thebdk/bdk-native
[![Anlyon Radar](https://radar.anlyon.com/badge/com.thebdk/bdk-native.svg)](https://radar.anlyon.com/servers/com.thebdk/bdk-native)

Source: MCP Registry. Synced Nov 18, 2026, 17:17 UTC.

BDK Native MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the BDK Native MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 9 of which can change, send or delete something, and 11 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the BDK Native MCP server delete data?

Yes. 6 tools can delete, cancel or revoke something: bdk_next, bdk_configure, bdk_setup_preview, bdk_check, bdk_checkout and bdk_build.

Can the BDK Native 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 BDK Native MCP server have?

11 tools: 6 destructive, 3 write, 2 read. bdk_next, bdk_configure, bdk_setup_preview, bdk_check, bdk_checkout, bdk_build, bdk_create_project, bdk_upload and 3 more.

Does the BDK Native MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the BDK Native MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the BDK Native MCP server changed its tools?

Yes, 4 times since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.