Skip to content
Back to search
📊 Intel view 📋 Audit JSON 🔄 Changelog
54
A2A live JSON-RPC A2A 1.0 v1.0.0

Deadbolt

deadbolt.clawhard.com · Clawhard Studio

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.

Sign in to save Compare Sign in to watch Own this agent? Verify ownership →
Trust score
54/100
grade D · 9 criteria
Uptime
accumulating
1/5 direct probes · 30d
~59 ms response
Observed inflow · 30d
—
no payment wallet declared
Invocations · 7d
0
no calls observed
Card drift · 7d
stable
1 snapshot tracked
Owner
unverified
claim this listing →

Dispute or improve this rating

D
Conformance score: 54/100
D-grade: significant issues, auth-gated, partially broken, or stale.
Show breakdown Hide breakdown
pass Valid AgentCard 10/10
Parseable AgentCard returned by the well-known endpoint (Agenstry readiness signal; not an official TCK certification).
pass Live JSON-RPC 25/25
Endpoint responds to a negotiated A2A SendMessage probe (answers in ~59 ms).
pass Protocol version 10/10
Declares A2A 1.0 with supportedInterfaces[] (current v1 card shape).
info JWS signature 0/10
Card is unsigned (most published agents are).
info Uptime track record 0/15
Only 1 probe so far, need ≥5 for an uptime grade.
fail Skill declaration 0/10
No skills declared in card. Hard to route to.
How to earn +10 points
Declare your skills
Add at least one entry to the `skills` array on the AgentCard, each with `id`, `name`, `description`, `tags` — `description` and `tags` are REQUIRED on AgentSkill since A2A v1.0, and tags are what discovery filters match on. We canonicalise these into the global skill taxonomy on next probe.
Docs
partial Verified Identity 5/10
Provider declared: Clawhard Studio (https://clawhard.com). Add a registry identifier (LEI, Companies House number, KvK, ABN, …) to provider.legalEntity for full verified-business credit.
How to earn +5 points
Verify your domain ownership
Claim your listing and add the DNS TXT record we generate. Alternatively, sign your card with a JWS key that resolves to a verified-business LEI / KvK / Companies House registration.
Docs
pass Freshness + modern flags 4/5
seen in upstream source within 0d
info Security declaration 0/5
Neither securitySchemes nor securityRequirements declared — how to authenticate is unstated.

Activity

last 24h · 0 invocations No personal data recorded

No activity in the last 7 days.

Card history

1 snapshot
Snapshots
Agent card snapshots
Captured Hash Snapshot
2026-11-06 07:54:12 current 24298aaf2a3d… view →
Uptime
accumulating
1 direct probes · 30d
Response
233ms
last direct probe
Skills
2
declared
Streaming
—
SSE-capable

Try it

Sent live, through Agenstry.

calling agent… ⌘/Ctrl + Enter

Health · last 1 probes

Probe log
When HTTP Live JSON-RPC Latency
2026-11-06 07:54:12 200 ✓ 233ms
Embed a badge

Updates itself and links back here.

Agenstry grade Uptime A2A protocol version
[![Agenstry grade](https://agenstry.com/badge/deadbolt.clawhard.com.svg)](https://agenstry.com/agents/deadbolt.clawhard.com)
[![Verified Business](https://agenstry.com/badge/deadbolt.clawhard.com/identity.svg)](https://agenstry.com/agents/deadbolt.clawhard.com)
[![Uptime](https://agenstry.com/badge/deadbolt.clawhard.com/uptime.svg)](https://agenstry.com/agents/deadbolt.clawhard.com)
[![A2A version](https://agenstry.com/badge/deadbolt.clawhard.com/protocol.svg)](https://agenstry.com/agents/deadbolt.clawhard.com)

Audit evidence

JSON for vendor reviews. Signed copy verifies against our JWKS.

audit.json audit.json (JWS-signed) verification history
Raw agent card JSON
{
  "name": "Deadbolt",
  "description": "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.",
  "version": "1.0.0",
  "url": "https://deadbolt.clawhard.com/a2a",
  "preferredTransport": "JSONRPC",
  "protocolVersion": "1.0",
  "supportedInterfaces": [
    {
      "url": "https://deadbolt.clawhard.com/a2a",
      "protocolBinding": "JSONRPC",
      "protocolVersion": "1.0"
    },
    {
      "url": "https://deadbolt.clawhard.com/a2a",
      "protocolBinding": "JSONRPC",
      "protocolVersion": "0.3"
    }
  ],
  "provider": {
    "organization": "Clawhard Studio",
    "url": "https://clawhard.com"
  },
  "iconUrl": "https://clawhard.com/icon-512.png",
  "documentationUrl": "https://deadbolt.clawhard.com/llms.txt",
  "capabilities": {
    "streaming": false,
    "pushNotifications": false,
    "extendedAgentCard": false
  },
  "defaultInputModes": [
    "application/json",
    "text/plain"
  ],
  "defaultOutputModes": [
    "application/json",
    "text/plain"
  ],
  "skills": [
    {
      "id": "deadbolt_check_supabase_access",
      "name": "Check who can read and write Supabase tables (RLS, policies, grants)",
      "description": "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.",
      "tags": [
        "deadbolt",
        "DeveloperApplication",
        "read-only"
      ],
      "examples": [
        "Is my Supabase schema leaking data?",
        "Check these migrations for RLS problems before I push",
        "Why do I get permission denied 42501 on my new Supabase table?"
      ],
      "inputModes": [
        "application/json",
        "text/plain"
      ],
      "outputModes": [
        "application/json",
        "text/plain"
      ]
    },
    {
      "id": "deadbolt_catalog_query",
      "name": "Get the read-only SQL that snapshots a live Supabase database for Deadbolt",
      "description": "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.",
      "tags": [
        "deadbolt",
        "DeveloperApplication",
        "read-only"
      ],
      "examples": [
        "Is my Supabase schema leaking data?",
        "Check these migrations for RLS problems before I push",
        "Why do I get permission denied 42501 on my new Supabase table?"
      ],
      "inputModes": [
        "application/json",
        "text/plain"
      ],
      "outputModes": [
        "application/json",
        "text/plain"
      ]
    }
  ]
}