# Clawhard Dev Tools (remote · dev.clawhard.com)

Exact developer checks: email DNS, Supabase RLS, cron, JSON, contrast, time zones, npm/PyPI packages

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `dev.clawhard.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-clawhard-dev/dev.md), [page](https://verifymcp.io/servers/com-clawhard-dev/dev)

## Channel facts

- Endpoint: `https://dev.clawhard.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4519 tokens (~129/item across 35 items; 19 tools + 16 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Clawhard Dev Tools MCP server?

Clawhard Dev Tools is a hosted endpoint at https://dev.clawhard.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-clawhard-dev 'https://dev.clawhard.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-clawhard-dev": {
      "url": "https://dev.clawhard.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-clawhard-dev": {
      "type": "http",
      "url": "https://dev.clawhard.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-clawhard-dev]
url = "https://dev.clawhard.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-clawhard-dev": {
      "type": "remote",
      "url": "https://dev.clawhard.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-clawhard-dev --url 'https://dev.clawhard.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-clawhard-dev:
    url: "https://dev.clawhard.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-clawhard-dev": {
      "Transport": "http",
      "Url": "https://dev.clawhard.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-clawhard-dev -t streamable-http -u 'https://dev.clawhard.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-clawhard-dev": {
      "type": "http",
      "url": "https://dev.clawhard.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 69, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-09 (score 68)

First indexed and scored.

## MCP tools (19)

### `stamp_check_email_domain` (~448 tokens)

Check a domain's email authentication (SPF, DKIM, DMARC, MX) from live DNS

Use when the user asks why their email goes to spam, whether their domain is set up to send email, or before they launch a newsletter, cold outreach, transactional email or a new sending service, e.g. "why are my emails going to spam?", "is my SPF/DKIM/DMARC right?", "do I meet Gmail and Yahoo's sender requirements?" or "I added SendGrid, did I break SPF?". Reads public DNS (DNS-over-HTTPS) and checks: SPF (exactly one record, every include followed and DNS lookups counted per RFC 7208 against the limit of 10, void lookups, loops, +all/?all, ptr), DMARC (RFC 7489 syntax, policy, pct, alignment, inherited from the parent domain, and whether an external report address authorized it), DKIM (17 common selectors plus any you pass; key type and RSA key size read from the key, revoked or broken keys), and MX (provider, null MX). Returns a grade A-F, a verdict, each check with status pass/warn/fail/info, whether the Gmail, Yahoo and Outlook.com sender rules are met, and copy-ready DNS records to fix problems (e.g. one merged SPF record, a starter DMARC record). DNS cannot list DKIM selectors, so when none of the common selectors is found the result says so and a known selector (the s= value in a DKIM-Signature header) can be passed in. Accepts a domain, an email address or a URL. Results are cached for 5 minutes; pass fresh=true right after the user changes DNS.

Input parameters:

- `dkim_selectors` (array): Extra DKIM selectors to try besides the common ones, e.g. ["mxvault"]. Find it as s= in a DKIM-Signature header or in the provider's setup page.
- `domain` (string, required): The sending domain, e.g. mycompany.com. An email address (you@mycompany.com) or a URL also works.
- `fresh` (boolean): true to skip the 5-minute cache, e.g. right after a DNS change.

### `stamp_check_dns_record` (~277 tokens)

Check an SPF, DMARC or DKIM record before publishing it

Use when you or the user are about to publish or edit an SPF, DMARC or DKIM TXT record, for example after writing a new SPF record that adds a sending service, or when the user pastes a record and asks "is this right?". Detects the record type. SPF: syntax per RFC 7208, every include and redirect followed live in DNS and counted against the 10-lookup limit, void lookups, loops, the final all; returns a lookup tree. DMARC: RFC 7489 tags and values (p, sp, pct, rua/ruf, adkim/aspf, fo). DKIM: key type and RSA key size read from the key, revoked (empty p=) or truncated keys. Returns valid true/false, errors, warnings and where to publish it. Pass domain so a/mx terms without a value can be resolved.

Input parameters:

- `domain` (string): Optional: the domain the record is for, so SPF a and mx terms can be checked.
- `record` (string, required): The TXT record value, e.g. "v=spf1 include:_spf.google.com ~all" or "v=DMARC1; p=none; rua=mailto:dmarc@mycompany.com". Quoted chunks ("..." "...") are joined.

### `deadbolt_check_supabase_access` (~349 tokens)

Check who can read and write Supabase tables (RLS, policies, grants)

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. Up to 200,000 characters.

Input parameters:

- `project_created_before_2026_10_30` (boolean): 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…
- `sql` (string, required): Migration SQL (one or many files concatenated, in order), or the single JSON value returned by the catalog query.

### `deadbolt_catalog_query` (~95 tokens)

Get the read-only SQL that snapshots a live Supabase database for Deadbolt

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.

### `tick_next_runs` (~286 tokens)

Next cron run times in a timezone

Use when you or the user just wrote a cron expression (GitHub Actions, Vercel cron, Cloudflare Cron Triggers, systemd, an agent schedule) and need its next fire times. Pass the expression and an IANA timezone (default UTC). Returns the next N runs as local wall times and UTC ISO, a plain-English field breakdown, and DST gap/fold warnings (spring-forward skips, fall-back double fires). Example: {"expression":"0 9 * * 1-5","timezone":"America/New_York","count":5}. Uses the tz database, so DST rules match the region and year. Not for converting a meeting time across cities (use Meridian) or for email DNS (use Stamp).

Input parameters:

- `count` (integer): How many next runs to return (1–20). Default 5.
- `expression` (string, required): Cron expression: 5 fields (minute hour day-of-month month day-of-week) or 6 with seconds first. Also accepts @hourly, @daily, @weekly, @monthly, @yearly.
- `from` (string): Optional ISO datetime to start from (default now), e.g. 2026-03-07T12:00:00Z.
- `timezone` (string): IANA timezone for local wall times, e.g. America/New_York. Default UTC.

### `tick_matches` (~182 tokens)

Would this cron fire at a datetime?

Use when you need a yes/no on whether a cron expression would fire at a specific instant in a timezone — for example before shipping a schedule that crosses a DST transition, or to verify a single expected fire. Example: {"expression":"0 9 * * 1-5","timezone":"America/New_York","at":"2026-11-06T14:00:00Z"}. Returns fires true/false, the local wall time of that instant, and DST notes if the local time is in a gap or fold.

Input parameters:

- `at` (string, required): ISO datetime to test, e.g. 2026-11-06T14:00:00Z.
- `expression` (string, required): Cron expression (5 or 6 fields, or a nickname like @hourly).
- `timezone` (string): IANA timezone. Default UTC.

### `mend_repair_json` (~230 tokens)

Repair broken or LLM-generated JSON

Use when JSON from an LLM, API, log, config or copy-paste fails to parse (JSON.parse error, "Unexpected token", "Expecting property name"), or the user pastes JSON with trailing commas, single quotes, unquoted keys, comments, Python True/False/None, NaN, missing commas or brackets, a ```json fence, text around it, or output that was cut off. Deterministic repair: returns valid, formatted JSON plus a list of every fix with line and column. Values are never rewritten, so big numbers, number formatting and key order stay exactly as written. If the text is already valid it says so. Up to 100,000 characters.

Input parameters:

- `indent` (integer): Spaces per indent level in the output. Default 2. Use 0 for one minified line.
- `sort_keys` (boolean): Sort object keys alphabetically. Default false (keep the original order).
- `text` (string, required): The broken JSON, or any text that contains JSON (a chat reply, a log line, a code block).

### `mend_outline_json` (~146 tokens)

Outline the structure of a large JSON payload

Use when you are about to read a big JSON response, log or export into context, before loading it: returns a compact outline of the structure (keys, types, array lengths, one example per repeated shape) so you can plan a query without spending tokens on the whole document. Repairs the JSON first if needed. Follow with mend_query_json to pull only the values you need. Up to 100,000 characters.

Input parameters:

- `max_depth` (integer): How many levels to expand. Default 4.
- `max_items` (integer): How many array items to show when items differ. Default 6.
- `text` (string, required): The JSON (or JSON-ish text).

### `mend_query_json` (~155 tokens)

Extract values from JSON by path

Use when you need specific fields from a JSON document without reading all of it: $.users[0].name, $.items[*].id, $.a.b[-1], $.list[1:3], $..email (recursive). Returns each match with its exact path, type and value. Repairs the JSON first if needed, so broken input still works. Up to 100,000 characters.

Input parameters:

- `max` (integer): Maximum matches to return. Default 50.
- `path` (string, required): Path such as $.users[*].email, data.items[0], $..id, $.list[-1], $.list[1:3].
- `text` (string, required): The JSON (or JSON-ish text).

### `swatch_check_contrast` (~193 tokens)

Check the WCAG contrast of a text and background color

Use when the user asks whether a color combination is readable or accessible, passes WCAG AA or AAA, or has enough contrast (text on a background, button, badge, link color), or what a color is in another format. Returns the exact contrast ratio, pass or fail for normal text, large text and UI components at AA and AAA, the APCA lightness contrast and a plain note. Colors can be hex, rgb(), hsl() or CSS names. Example: {"foreground": "#777777", "background": "#ffffff"}. Also returns each color in hex, rgb, hsl and oklch with its nearest CSS name.

Input parameters:

- `background` (string, required): Background color, e.g. "#ffffff".
- `foreground` (string, required): Text (or icon) color, e.g. "#767676" or "rgb(20 20 20)" or "tomato".

### `swatch_fix_contrast` (~139 tokens)

Find the nearest accessible color that passes contrast

Use when a color pair fails contrast and the user wants the smallest change that makes it pass, such as "make this gray text accessible without changing the look". Returns the closest text color on that background that reaches the target (AA, AAA, AA-large or ui), and separately the closest background, keeping the hue. Example: {"foreground": "#777777", "background": "#ffffff", "target": "AA"}. Returns already_passes if nothing needs to change.

Input parameters:

- `background` (string, required): Current background color.
- `foreground` (string, required): Current text color.
- `target` (string): Contrast target. Default AA.

### `swatch_make_scale` (~132 tokens)

Build a 50-950 color palette from one color

Use when the user asks for a palette, shades, tints, a design-token scale or a Tailwind-style 50 to 950 ramp from a brand color. Returns 11 steps that keep the hue, with the hex, contrast on white and on black, and the best text color for each step. Example: {"color": "#ff5a1f", "name": "brand"}.

Input parameters:

- `color` (string, required): Base color, e.g. "#ff5a1f".
- `name` (string): Token name used in the CSS and Tailwind output. Default "brand".

### `swatch_check_pairs` (~121 tokens)

Check contrast for many color pairs at once

Use when the user has a whole design system, theme or stylesheet and wants every text and background pair checked for accessibility in one go. Takes up to 50 pairs and returns the ratio and AA and AAA results for each, with a count of failures. Example: {"pairs": [{"foreground": "#777", "background": "#fff", "label": "muted text"}, {"foreground": "#fff", "background": "#ff5a1f", "label": "button"}]}.

Input parameters:

- `pairs` (array, required): Pairs to check.

### `meridian_now` (~104 tokens)

Current time in any places or time zones

Use when the user asks what time or date it is right now somewhere. Reads the server clock and returns the current time, date, UTC offset, abbreviation and daylight saving status for each place. Places can be cities ("Tokyo"), IANA zones ("Europe/Paris"), abbreviations ("PST") or "UTC+5:30".

Input parameters:

- `places` (array, required): Cities, IANA zones or abbreviations, e.g. ["London","Asia/Tokyo"].

### `meridian_convert_time` (~282 tokens)

Convert a time between time zones, DST-correct

Use when you need to convert a specific wall-clock time from one place to others, for any date. It uses the real tz database, so daylight saving is right for that exact date (the US and Europe switch on different weeks), and it warns when the time does not exist (spring forward) or happens twice (fall back). Time accepts "15:00", "3:30pm", "noon", "now" or an ISO local time like 2026-11-05T15:00 (no Z). Date defaults to today in the source zone. Returns {input, utc, source:{...}, converted:[{place, zone, local, time_12h, date, utc_offset, abbreviation, day_note, hours_ahead_of_source}], warning?, summary, open_url}.

Input parameters:

- `date` (string): Optional date YYYY-MM-DD in the source zone. Default today.
- `from` (string, required): Source place or zone, e.g. "New York" or "America/New_York".
- `time` (string, required): Local time in the source place, e.g. "15:00", "3:30pm", "noon", "now", "2026-11-05T15:00".
- `to` (array, required): Destination places, e.g. ["London","Tokyo"].

### `meridian_meeting_slots` (~219 tokens)

Find meeting times that work across time zones

Use when you need to schedule a call across several places. Scans the day in 15-minute steps and ranks start times so the most people are inside working hours and nobody is at night, using each place's real offset and DST for that date. Returns up to 5 slots with each person's local start and end, and says plainly when no time works for everyone. Defaults: working hours 9 to 17, 60 minutes, date today in the first place.

Input parameters:

- `count` (integer): How many slots to return, default 5.
- `date` (string): Date YYYY-MM-DD, local to the first place. Default today.
- `duration_minutes` (integer): Meeting length in minutes, multiple of 15. Default 60.
- `end_hour` (integer): Working day end hour, default 17.
- `places` (array, required): Where each attendee is, e.g. ["San Francisco","London","Tokyo"].
- `start_hour` (integer): Working day start hour, default 9.

### `meridian_zone_info` (~135 tokens)

Offset, abbreviation and daylight saving changes for a zone

Use when you need to answer "what is the UTC offset of X", "does X observe daylight saving" and "when do the clocks change". Returns the current offset and abbreviation, whether the place observes DST, every clock change in the year with exact local before and after times, and the next change. Abbreviations like IST or CST are ambiguous, so the answer says which zone was used.

Input parameters:

- `place` (string, required): City, IANA zone or abbreviation, e.g. "London" or "America/Phoenix".
- `year` (integer): Year to list clock changes for. Default this year.

### `doorman_check_ai_bot_access` (~230 tokens)

See which AI bots a website lets in

Use when the user asks whether their site (or any public site), or a robots.txt they pasted, blocks ChatGPT, Claude, Google AI, Perplexity or other AI crawlers, whether AI can read or train on their content, or why AI search does not mention their site. Fetches the live robots.txt and reports, for 22 named AI bots in four groups (AI training, AI search, assistants, search engines), which are let in, kept out or partly blocked, plus the site's content-signal preference and fixes. Example: {"url": "example.com"} or {"robots_txt": "User-agent: GPTBot\nDisallow: /"}. Pass robots_txt instead of url to check a draft or pasted file without fetching anything. Read-only.

Input parameters:

- `robots_txt` (string): robots.txt text to check instead of fetching a site (a draft or a pasted file, up to 512 KB). Empty means no robots.txt.
- `url` (string): Website address or domain, e.g. nytimes.com. Send this or robots_txt.

### `notary_check_packages` (~227 tokens)

Check that npm and PyPI packages really exist before installing them

Use when the user or an agent is about to install or import npm or PyPI packages: before npm install or pip install, when adding lines to package.json or requirements.txt, or when a package name came from an AI answer, a tutorial or memory and may be invented. Looks each name up in the live registry and returns whether it exists, the latest version, whether a pinned version exists, weekly downloads, first and last publish dates, deprecation or yanked status, install-time scripts, whether the name is one or two typed characters from a well-known package, and real similar packages when the name does not exist. Example: {"packages":[{"ecosystem":"npm","name":"@anthropic/mcp-client"},{"ecosystem":"pypi","name":"requests","version":"2.32.3"}]}. Up to 10 packages per call; versions must be exact, not ranges. Not a malware or vulnerability scan: "ok" means it exists and nothing looked wrong.

Input parameters:

- `packages` (array, required): 1 to 10 packages to look up.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-clawhard-dev/dev#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 74
- 2026-11-19: 73
- 2026-11-18: 73
- 2026-11-17: 72
- 2026-11-16: 72
- 2026-11-15: 71
- 2026-11-14: 71
- 2026-11-13: 70
- 2026-11-12: 70
- 2026-11-11: 69
- 2026-11-10: 69
- 2026-11-09: 68

## Common questions

### What is the Clawhard Dev Tools MCP server?

Clawhard Dev Tools is an MCP server listed in the public MCP registry as com.clawhard/dev. Exact developer checks: email DNS, Supabase RLS, cron, JSON, contrast, time zones, npm/PyPI packages. This page covers its hosted endpoint (https://dev.clawhard.com/mcp).

### Is the Clawhard Dev Tools MCP server safe to use?

Clawhard Dev Tools scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Clawhard Dev Tools MCP server expose?

Clawhard Dev Tools exposes 19 tools: stamp_check_email_domain, stamp_check_dns_record, deadbolt_check_supabase_access, deadbolt_catalog_query, tick_next_runs, and 14 more. Their descriptions and schemas cost roughly 3,950 tokens of context every time the server is loaded.

### Does the Clawhard Dev Tools MCP server require authentication?

No. We connected to Clawhard Dev Tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Clawhard Dev Tools MCP server still maintained?

Clawhard Dev Tools is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Clawhard Dev Tools MCP server?

VerifyMCP ran 14 checks on Clawhard Dev Tools, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://dev.clawhard.com/mcp
- Website: https://dev.clawhard.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-clawhard-dev/dev.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-clawhard-dev/dev/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-clawhard-dev/dev.json
- HTML version of this page: https://verifymcp.io/servers/com-clawhard-dev/dev
