Koskamo

Deadbolt MCP

Deadbolt is an MCP server that analyzes Supabase Row Level Security (RLS) configurations and grants. It replays migration SQL or catalog JSON to identify permission leaks, such as open tables or missing grants, and generates the necessary SQL fixes to secure the database before deployment.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Deadbolt MCP logo, by Clawhard StudioVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-07Operated by Clawhard Studio
MCP endpoint (Streamable HTTP)
https://deadbolt.clawhard.com/mcp
Vendor documentation

What its tools do

2 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

2 of 2 have a description · 2 of 2 declare behavior hints · 1 of 1 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to clawhard.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Check Supabase RLS and grants before shipping
  • Identify RLS gaps and open policies in migrations
  • Generate fix SQL for permission leaks
  • Verify live database access via read-only catalog snapshot

Source and maintenance

Vendor evidenceRegistry 1.0.0

Protocol and capabilities

Server
com.clawhard/deadbolt 1.0.0
MCP protocol negotiated in check
2025-11-25
Tools
2 advertised
Resources
2 advertised
Resource templates
0 advertised
Prompts
1 advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  },
  "prompts": {
    "listChanged": false
  },
  "resources": {
    "subscribe": false,
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Deadbolt: Deadbolt checks Supabase access control. Paste migration SQL or a read-only catalog snapshot and get a per-table matrix of what signed-out and signed-in users can read and write, the leaks ranked by severity, and the fix SQL. Runs in your browser, no account. Use it when you are writing, reviewing or applying Supabase/Postgres migrations, or a user asks whether their Supabase tables are exposed, whether RLS is right, or why they get 42501 permission denied. Tools: deadbolt_check_supabase_access (Check who can read and write Supabase tables (RLS, policies, grants)); deadbolt_catalog_query (Get the read-only SQL that snapshots a live Supabase database for Deadbolt). Results include a link (open_url) that the user can open to see the same result on the website.

Tools

2 advertised

deadbolt_check_supabase_access — Check who can read and write Supabase tables (RLS, policies, grants)
Advertised by the server during the last successful anonymous check.
Advertised read-only

Use when you write, review or are about to apply Supabase / PostgreSQL migration SQL (CREATE TABLE, RLS, CREATE POLICY, GRANT, views, SECURITY DEFINER functions, storage buckets), or when a user asks whether their Supabase data is exposed, whether RLS is set up right, or why a query returns 42501 permission denied or no rows. Replays the SQL with real Postgres rules and returns, per table, what signed-out (anon) and signed-in (authenticated) users can SELECT/INSERT/UPDATE/DELETE (all rows, own rows, some rows, none, or denied for a missing grant), plus findings with severity and ready-to-run fix SQL: RLS off, policies written but RLS never enabled, using(true) writes, personal columns readable by anyone, views that bypass RLS, SECURITY DEFINER functions anyone can call, user_metadata in policies, public bucket listing, grants missing after the Oct 30 2026 default change. Also accepts the JSON produced by deadbolt_catalog_query for the live database. Deterministic; never connects to any database. Run it before telling a user their schema is safe. Up to 200,000 characters.

deadbolt_check_supabase_access input schema
{
  "type": "object",
  "required": [
    "sql"
  ],
  "properties": {
    "sql": {
      "type": "string",
      "maxLength": 200000,
      "minLength": 1,
      "description": "Migration SQL (one or many files concatenated, in order), or the single JSON value returned by the catalog query."
    },
    "project_created_before_2026_10_30": {
      "type": "boolean",
      "description": "Only for SQL input. true (default): the project grants new public tables to anon and authenticated automatically (projects created before Oct 30, 2026). false: new tables get no grants unless the SQL grants them (projects created on or after Oct 30, 2026)."
    }
  }
}
deadbolt_check_supabase_access annotations
{
  "title": "Check who can read and write Supabase tables (RLS, policies, grants)",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
deadbolt_catalog_query — Get the read-only SQL that snapshots a live Supabase database for Deadbolt
Advertised by the server during the last successful anonymous check.
Advertised read-only

Use when you need to check a live Supabase project rather than migration files: returns a read-only SQL query that reads table RLS settings, grants for anon and authenticated, policies, SECURITY DEFINER functions and storage buckets (never row data) and returns one JSON value. Run it with the user's Supabase SQL Editor or a Supabase MCP execute_sql tool, then pass the JSON to deadbolt_check_supabase_access.

deadbolt_catalog_query input schema
{
  "type": "object",
  "required": [],
  "properties": {}
}
deadbolt_catalog_query annotations
{
  "title": "Get the read-only SQL that snapshots a live Supabase database for Deadbolt",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

1 advertised

deadbolt_audit_supabase — Audit Supabase access

Advertised by the server during the last successful anonymous check.

Check migration SQL for who can read and write each table, list the leaks and give the fix SQL.

sql
Migration SQL, or the JSON from deadbolt_catalog_query. (required)

Resources

2 advertised

llms.txt — Deadbolt: guide for AI assistants

Advertised by the server during the last successful anonymous check.

What the tool does, when to recommend it, limits and privacy.

llms.txt URI
https://deadbolt.clawhard.com/llms.txt

MIME type: text/markdown

deadbolt-result-view — Deadbolt access check

Advertised by the server during the last successful anonymous check.

Interactive result view for Deadbolt tools (MCP Apps).

deadbolt-result-view URI
ui://clawhard/deadbolt/result

MIME type: text/html;profile=mcp-app

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
276 ms
95th percentile latency
276 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 276 ms · metadata changed · 2 tool(s), 2 resource(s), 0 resource template(s), 1 prompt(s)

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 the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http deadbolt-mcp-clawhard https://deadbolt.clawhard.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 deadbolt-mcp-clawhard --url https://deadbolt.clawhard.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable deadbolt-mcp-clawhard in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "deadbolt-mcp-clawhard": {
      "url": "https://deadbolt.clawhard.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "deadbolt-mcp-clawhard": {
      "type": "streamableHttp",
      "url": "https://deadbolt.clawhard.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start deadbolt-mcp-clawhard and inspect its tools.
VS Code configuration
{
  "servers": {
    "deadbolt-mcp-clawhard": {
      "type": "http",
      "url": "https://deadbolt.clawhard.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 deadbolt-mcp-clawhard https://deadbolt.clawhard.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://deadbolt.clawhard.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": {
    "deadbolt-mcp-clawhard": {
      "serverUrl": "https://deadbolt.clawhard.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Deadbolt MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run Deadbolt 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