Skip to content

Clawhard Studio MCP server

com.clawhard/studioclawhard.comstreamable-httpv1.21.0Scanned

Token counts, contrast, time zones, cron, JSON, regex, DMARC, packages, Unicode, links, domains

38 tools: 1 do something that can't be undone, 31 change things and 6 only read.

Tools: 0 delete, 1 irreversible, 31 write, 6 read.

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • 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 Clawhard Studio MCP server can do

The Clawhard Studio MCP server is published by clawhard.com, a domain the MCP Registry verified. It has 38 tools. It can do things that cannot be undone, such as sending, paying or publishing (meridian_convert_time) and create or change data (31 tools: runsheet_create_schedule, halves_settle_up, halves_create_group_link, doorman_check_ai_bot_access and 27 more), but cannot delete data. 6 tools only read.

4 tools read private data (tokendiet_count_tokens, mend_query_json, deadbolt_catalog_query and 1 more); 16 tools bring in text other people can write (runsheet_create_schedule, halves_create_group_link, doorman_check_ai_bot_access and 13 more); 9 tools can send data out of your system (doorman_check_ai_bot_access, meridian_convert_time, xray_scan_text and 6 more). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 16 findings, 2 of them high severity (annotation-conflict, tool-shadowing, sensitive-path, credentials-mention and 1 more). Each one comes with the text it matched.

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

Last scanned Nov 20, 2026, version 1.21.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.

38 tools

Can't be undone 1Claude Code: ask
  • meridian_convert_timeUse when you need to convert a specific wall-clock time from one place to others, for any date.Can send data out1 finding

    Why it is in this group

    • The name "meridian_convert_time" says "convert": a word for a change.
    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "meridian_convert_time" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "meridian_convert_time" says "convert": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Convert a time between time zones, DST-correct
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Changes things 31Claude Code: ask
  • border_check_corsUse when the user hits a CORS error ("blocked by CORS policy", "No 'Access-Control-Allow-Origin' header", "preflight", "Failed to fetch" from a frontend) or is about to call a publ…Reads text others writeCan send data out2 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.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...rol-Allow-Headers", "withCredentials", "credentials include"). Sends the browser's own pref..."

      What this check looks for
    • Info

      The input schema at properties.credentials.description mentions "credentials".

      Matched text

      inputSchema.properties.credentials.description: "...e when the request sends cookies: fetch credentials: "include", XHR or axios withCredential..."

      What this check looks for
    Description, as the server wrote it
    Use when the user hits a CORS error ("blocked by CORS policy", "No 'Access-Control-Allow-Origin' header", "preflight", "Failed to fetch" from a frontend) or is about to call a public API from browser code (React, Next.js, Vue, a browser extension page) and asks whether it will work (signals: "CORS", "works in Postman but not in the browser", "preflight 401/404", "Access-Control-Allow-Headers", "withCredentials", "credentials include"). Sends the browser's own preflight (OPTIONS with Origin, Access-Control-Request-Method and -Headers) to the live API and, for GET and HEAD, the request itself with the Origin header, then applies the Fetch standard CORS rules as Chrome implements them. Returns verdict (allowed, blocked, preflight_passed, incomplete, same_origin, unreachable), the exact Chrome console error, which step fails (preflight or response) and why, whether a preflight is needed and why, the CORS headers the server sent, warnings (missing Vary: Origin, a server that echoes any origin with credentials, unreadable response headers, Authorization covered only by *), the exact response headers that fix it, and curl commands to reproduce. Example: {"url":"https://api.example.com/v1/items","origin":"http://localhost:3000","method":"POST","headers":["Content-Type: application/json","Authorization"],"credentials":true}. Limits: public http/https APIs on ports 80 and 443 only (localhost, private and staging servers go through border_check_cors_headers with pasted curl output); never sends POST, PUT, PATCH or DELETE (those get the preflight checked only) and never sends header values for Authorization or keys; a server can answer differently to a real browser session.

    Annotations the server declares

    • title: Check whether a browser would allow a cross-origin API call (CORS)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • border_check_cors_headersUse when a CORS problem involves a server Border cannot reach (localhost, a dev or staging server, a private network, a custom port) or a POST, PUT, PATCH or DELETE whose real resp…Can send data out2 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

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...age origin, method, request headers and credentials mode. Returns the same result as border..."

      What this check looks for
    • Info

      The input schema at properties.credentials.description mentions "credentials".

      Matched text

      inputSchema.properties.credentials.description: "...e when the request sends cookies: fetch credentials: "include", XHR or axios withCredential..."

      What this check looks for
    Description, as the server wrote it
    Use when a CORS problem involves a server Border cannot reach (localhost, a dev or staging server, a private network, a custom port) or a POST, PUT, PATCH or DELETE whose real response needs checking, and the raw response headers are available from curl -i or the browser DevTools Network tab (signals: "here is the OPTIONS response", "my local API returns these headers", "CORS works on localhost but not in production", "preflight response is"). Parses the pasted OPTIONS response and/or the actual response (status line plus headers; curl -i, curl -v, curl -iL with redirects, and DevTools copies are all read) and applies the Fetch standard CORS rules as Chrome implements them, for the given page origin, method, request headers and credentials mode. Returns the same result as border_check_cors: verdict, the exact Chrome console error, the failing step and reason, warnings, the response headers that fix it, and the curl commands to capture any missing response. Nothing is fetched. Example: {"url":"http://localhost:8000/api/login","origin":"http://localhost:5173","method":"POST","headers":["Content-Type: application/json"],"credentials":true,"preflight_response":"HTTP/1.1 200 OK\nAccess-Control-Allow-Origin: *\nAccess-Control-Allow-Headers: content-type"}. Limits: the verdict is only as complete as the pasted headers; a preflighted request needs both pastes for a full answer.

    Annotations the server declares

    • title: Check pasted preflight and response headers against the CORS rules
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • deadbolt_check_supabase_accessUse 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), …1 finding

    Why it is in this group

    • The input takes a statement or command to run (input.sql), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "deadbolt_check_supabase_access" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.sql), which can change anything it can reach.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check who can read and write Supabase tables (RLS, policies, grants)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • doorman_check_ai_bot_accessUse 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…Reads text others writeCan send data outNo 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.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: See which AI bots a website lets in
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • halves_settle_upUse when the user shares a trip, dinner, household or group expense list and asks who owes whom, how to split costs, or how to settle up.No 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.
    Description, as the server wrote it
    Use when the user shares a trip, dinner, household or group expense list and asks who owes whom, how to split costs, or how to settle up. Returns each person's paid, share and net balance, and the smallest set of payments that squares everyone up. Handles equal splits, splits among a subset, exact amounts and payments already made, with correct rounding. Nothing is saved. Example: {"people": ["Ana", "Ben", "Cy"], "expenses": [{"what": "Dinner", "amount": 90, "paid_by": "Ana"}, {"what": "Taxi", "amount": 24, "paid_by": "Ben", "split_between": ["Ben", "Cy"]}]}. Amounts are exact to the cent.

    Annotations the server declares

    • title: Work out who owes whom in the fewest payments
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • jig_check_schemaUse when the user asks whether a JSON Schema is valid, or whether it will work with OpenAI Structured Outputs or function calling with strict: true, Claude structured outputs or st…1 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 read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

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

      Matched text

      description ends: "...rs can change them, and very large schemas can still hit unpublished size limits."

      What this check looks for
    Description, as the server wrote it
    Use when the user asks whether a JSON Schema is valid, or whether it will work with OpenAI Structured Outputs or function calling with strict: true, Claude structured outputs or strict tool use, or Gemini structured output (response_json_schema), or is writing a tool or function schema, an MCP inputSchema, a response_format, or a schema exported from Zod or Pydantic (signals: "Invalid schema for response_format", "strict mode error", "Claude returns 400 for my schema", "will this schema work with OpenAI", "Gemini ignores maxLength", "additionalProperties false", "all fields must be required"). First checks the schema against its draft: type names like "int", "required": true on a property, misspelt keywords, unresolvable $ref, invalid regex, impossible ranges. Then checks each provider's documented rules: OpenAI (every property in required, additionalProperties false on every object, root an object and not anyOf, no allOf/not/if, at most 5000 properties, 10 levels, 1000 enum values, documented formats only), Claude (additionalProperties false, no minimum/maximum/multipleOf/minLength/maxLength, minItems only 0 or 1, no recursion, at most 24 optional and 16 union-typed parameters per request, regex without lookarounds or backreferences), Gemini (minLength, maxLength, uniqueItems, minProperties and similar are dropped without an error). Returns per provider a verdict (ok, warnings, fails), each issue with its JSON Pointer path, rule, fix and the provider's doc URL, plus a converted copy the provider accepts (optional fields made required and nullable for OpenAI, unsupported constraints moved into descriptions the way the official SDK helpers do), and counts (properties, depth, optional and union-typed parameters). Example: {"schema":{"type":"object","properties":{"city":{"type":"string","maxLength":40},"days":{"type":"integer","minimum":1}},"required":["city"]},"providers":["openai","anthropic"]}. Rules are from each provider's docs, checked 2026-11-18; providers can change them, and very large schemas can still hit unpublished size limits.

    Annotations the server declares

    • title: Check a JSON Schema, and whether OpenAI, Claude and Gemini strict modes accept it
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • mend_outline_jsonUse 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 examp…No 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.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Outline the structure of a large JSON payload
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • mend_repair_jsonUse 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 co…No 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.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Repair broken or LLM-generated JSON
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • meridian_meeting_slotsUse when you need to schedule a call across several places.No 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.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find meeting times that work across time zones
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • meridian_nowUse when the user asks what time or date it is right now somewhere.No 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.
    Description, as the server wrote it
    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".

    Annotations the server declares

    • title: Current time in any places or time zones
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • meridian_zone_infoUse when you need to answer "what is the UTC offset of X", "does X observe daylight saving" and "when do the clocks change".No 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.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Offset, abbreviation and daylight saving changes for a zone
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • notary_check_packagesUse 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 …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
    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.

    Annotations the server declares

    • title: Check that npm and PyPI packages really exist before installing them
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • runsheet_create_scheduleUse when the user wants a shareable run-of-show or day-of schedule for a wedding, conference, shoot or other event that guests or crew can open on their phone and that updates live…Reads text others writeNo findings

    Why it is in this group

    • The name "runsheet_create_schedule" 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
    Use when the user wants a shareable run-of-show or day-of schedule for a wedding, conference, shoot or other event that guests or crew can open on their phone and that updates live when edited. Creates the page and returns a view link to share with everyone and a private edit link to keep. Start from a template (wedding, conf, shoot, blank) or pass your own items. Example: {"name": "Maya and Sam wedding", "date": "2026-09-12", "timezone": "America/New_York", "template": "wedding"} or {"name": "Offsite", "items": [{"time": "09:00", "title": "Welcome", "duration_minutes": 30}]}. Each call creates a new saved page.

    Annotations the server declares

    • title: Create a live day-of schedule page
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • sieve_check_redosUse when a regular expression will run on user input or untrusted data (form validation, request routing, log parsing, WAF or search rules) and must not hang the server, or when re…No 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.
    Description, as the server wrote it
    Use when a regular expression will run on user input or untrusted data (form validation, request routing, log parsing, WAF or search rules) and must not hang the server, or when reviewing a codebase's regexes for ReDoS (signals: "is this regex safe", "ReDoS", "catastrophic backtracking", "regex hangs", "CPU spike on validation", "security review of regexes", "(a+)+"). Analyzes 1 to 20 patterns with recheck (automaton analysis with a fuzzing fallback) for backtracking engines with JavaScript syntax, and returns per pattern: safe (proven linear, or no attack found when backreferences or lookarounds force fuzzing), or vulnerable with the complexity (exponential, or polynomial with its degree), a concrete attack string (repr like 'a'.repeat(31) + '\\x00', plus the string itself when short), the hot part of the pattern and a fix hint. Example: {"patterns":["^(a+)+$","/^([a-z]+\\s)*$/","^[\\w.+-]+@[\\w-]+\\.[\\w.-]+$"]}. Python re, PCRE, Java, .NET and Ruby backtrack the same way on these constructs; RE2, Go regexp and Rust regex are linear-time and not affected. To also run the pattern on test strings, use sieve_test_regex.

    Annotations the server declares

    • title: Check regular expressions for ReDoS (catastrophic backtracking)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • sieve_test_regexUse when you have written, been given or are about to commit a regular expression and need to know what it really matches, instead of predicting it (signals: "write a regex for", "…1 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 read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

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

      Matched text

      description ends: "...l when clean), error? and hint? (invalid patterns), notes, checked_at, open_url}."

      What this check looks for
    Description, as the server wrote it
    Use when you have written, been given or are about to commit a regular expression and need to know what it really matches, instead of predicting it (signals: "write a regex for", "does this regex match", "validate emails/phone numbers/dates/slugs/URLs with a regex", "why doesn't my regex match", "test this pattern", "regex for Go", "is this regex safe", "catastrophic backtracking", "convert this Python regex to JavaScript"). Executes the pattern on the real engine: JavaScript (V8 RegExp, the engine in Chrome, Node.js and Cloudflare Workers; flags d g i m s u v y) or RE2 (re2js, with Go regexp parity: Go, RE2, Google Sheets and BigQuery syntax; flags i m s). Give strings that must match and strings that must not; each case comes back pass/fail with the matched text, index and capture groups (numbered and named), and why a "should not match" string matched (usually a missing ^...$). match: "full" tests the whole string. texts lists every match, replace_with shows the replacement ($1/$<name> in JavaScript, $1/${name} in Go). For JavaScript it also runs a ReDoS analysis (recheck): proven linear, or exponential/polynomial backtracking with a concrete attack string and the hot part of the pattern. Flags patterns that compile but mislead: ^a|b$ anchoring, \A/\Z/\h read as letters, [[:alpha:]], {,3}, [A-z], unescaped dots before extensions. Invalid patterns return the engine's error and a hint (Python (?P<name>), (?i), possessive and atomic groups; lookarounds and backreferences in RE2). Example: {"pattern":"[\\w.+-]+@[\\w-]+\\.[a-z]{2,}","should_match":["ann@example.com"],"should_not_match":["ann@example","see ann@x.io now"]}. Does not run Python, PCRE, Java or .NET engines; it reports what differs for common constructs. Up to 100 strings of 20000 characters; on a ReDoS-vulnerable pattern, long strings are skipped instead of hanging. Returns {valid, verdict: ok|warnings|redos|fails|invalid, summary, engine, engine_name, pattern, flags, match_mode, counts:{should_match, should_not_match, texts, passed, failed, skipped}, group_count, cases:[{text, length, expect: match|no_match|any, matched, pass (null = skipped), match_count, match:{text, index, end, groups?, named?}, matches? (texts only), why?, replaced?, skipped?}], warnings:[{rule, message, fix?, index?}], redos:{status: safe|vulnerable|unknown, complexity: linear|polynomial (degree n)|exponential|no attack found|unknown, attack?:{repr, length, string|null, sample}, hotspots?:[{start, end, text}], explanation?, fix_hint?, note?}|null, fix_message (ready-to-apply list, null when clean), error? and hint? (invalid patterns), notes, checked_at, open_url}.

    Annotations the server declares

    • title: Run a regular expression on test strings (JavaScript or RE2/Go) and check it for ReDoS
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • spill_scan_secretsUse when the user asks whether some text contains secrets, or before you paste, commit, share, log or send code, a .env file, a diff, config, logs, a stack trace or a prompt that m…3 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.

    Findings

    • High

      The description refers to ".env".

      Matched text

      description: "...ste, commit, share, log or send code, a .env file, a diff, config, logs, a stack tra..."

      What this check looks for
    • Info

      The description mentions "credentials".

      Matched text

      description: "...ck trace or a prompt that might contain credentials, for example "did I leak a key in this?..."

      What this check looks for
    • High

      The input schema at properties.text.description refers to ".env".

      Matched text

      inputSchema.properties.text.description: "The text to scan: code, a diff, .env, config, logs, a stack trace, a chat or..."

      What this check looks for
    Description, as the server wrote it
    Use when the user asks whether some text contains secrets, or before you paste, commit, share, log or send code, a .env file, a diff, config, logs, a stack trace or a prompt that might contain credentials, for example "did I leak a key in this?", "is this safe to post?" or "redact the secrets in this log". Detects 48 services by exact key format (OpenAI, Anthropic, Gemini/Google, Groq, xAI, OpenRouter, Stripe, Supabase, AWS, GitHub, GitLab, npm, PyPI, Slack, Discord, Twilio, SendGrid, Resend, Shopify, Cloudflare and more) plus PEM private keys, database URLs with passwords, JWTs, Authorization headers and high-entropy values in variables named like secret, token, api_key or password. It verifies what it can deterministically: GitHub token CRC32 checksums, JWT and Supabase key role and expiry (service_role vs anon), documented example keys and placeholders, and NEXT_PUBLIC_/VITE_/EXPO_PUBLIC_ variables that ship to every browser. Returns findings with severity (critical, high, medium, public, info), line and column, a masked preview (never the full secret), why it matters, the fix and the provider's revoke URL, plus a redacted copy with labels like [STRIPE_SECRET_KEY_1]. Text is processed in memory to answer and is not stored. Limits: format-based, so a random secret with a neutral name can be missed; it never tests keys against providers; up to 200,000 characters. The same scanner also runs entirely in the browser at https://spill.clawhard.com.

    Annotations the server declares

    • title: Find and redact API keys, tokens, private keys and passwords in text
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • stake_check_domainsUse when the user asks whether a domain is available or taken, wants product, startup, app or project name ideas with a free domain, or is about to put a domain into a plan, README…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
    Use when the user asks whether a domain is available or taken, wants product, startup, app or project name ideas with a free domain, or is about to put a domain into a plan, README, config or launch post (signals: "is the .com taken", "domain available", "name ideas with a .com", "which of these names has a free domain", ".io or .ai", "who owns this domain", "when does it expire"). Asks each ending's own registry through RDAP (the official successor to WHOIS; IANA's server list plus the registries of .io, .me, .sh, .ac, .us, .so, .de, .ch that are not in it), and returns per domain: available, registered, registered_expiring (redemption or pending delete), likely_available (DNS only: for endings with no public RDAP such as .co, .gg, .eu, .it, or when a registry's RDAP server refuses or rate-limits the check), unknown or invalid; for taken names the registration and expiry dates, days to expiry, registrar, status codes and nameservers, and a flag when the nameservers belong to a parking or domain-marketplace service (Afternic, Dan.com, Sedo, Atom and others: the owner may sell it). Pass full domains, or names plus endings: {"names":["tidewell","brightloop"],"tlds":["com","io","ai"]} or {"domains":["tidewell.com","münchen.de","foo.co.uk"]}. Default endings when only names are given: com, io, ai, dev, app, co, net, org. Up to 20 domains per call. Call it before presenting name ideas as available instead of guessing. Cannot see prices, premium or reserved status, trademarks, or social handles; "available" is not a reservation.

    Annotations the server declares

    • title: Check whether domain names are available to register (live registry lookup)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • stamp_check_dns_recordUse 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 pas…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
    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.

    Annotations the server declares

    • title: Check an SPF, DMARC or DKIM record before publishing it
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • stamp_check_email_domainUse 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 s…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
    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.

    Annotations the server declares

    • title: Check a domain's email authentication (SPF, DKIM, DMARC, MX) from live DNS
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • swatch_check_contrastUse 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 wh…No 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.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check the WCAG contrast of a text and background color
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • swatch_check_pairsUse when the user has a whole design system, theme or stylesheet and wants every text and background pair checked for accessibility in one go.No 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.
    Description, as the server wrote it
    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"}]}.

    Annotations the server declares

    • title: Check contrast for many color pairs at once
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • swatch_fix_contrastUse 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".No 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.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find the nearest accessible color that passes contrast
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • swatch_make_scaleUse 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.No 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.
    Description, as the server wrote it
    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"}.

    Annotations the server declares

    • title: Build a 50-950 color palette from one color
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • tack_check_workflowUse when the user asks to write, review, fix or harden a GitHub Actions workflow (.github/workflows/*.yml) or a composite action.yml, or when a workflow was just written or edited …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 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.

    Findings

    • Info

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

      Matched text

      description ends: "...ee private repositories, secrets or repository settings. Up to 200000 characters."

      What this check looks for
    Description, as the server wrote it
    Use when the user asks to write, review, fix or harden a GitHub Actions workflow (.github/workflows/*.yml) or a composite action.yml, or when a workflow was just written or edited and is about to be committed (signals: "write a CI workflow", "why does my workflow fail", "Invalid workflow file", "Unexpected input", "pin actions to SHA", "is actions/checkout@v4 still current", "Node 20 deprecated", "upload-artifact v3", "runs-on ubuntu-20.04", "script injection", "pull_request_target"). Parses the YAML (errors with line and column, duplicate keys, anchors), checks the structure against GitHub's workflow syntax as documented on 2026-11-19 (including recent keys such as schedule timezone, cache-mode, background, wait, wait-all, cancel, parallel and $/ self-repository references), then resolves every uses: reference live on github.com: whether the repository, tag, branch or commit exists, which release a SHA is, the latest release, retired versions that make a job fail (upload/download-artifact v3 and older, actions/cache v1-v2 and old exact pins), runs.using node20-or-older runtimes, with: inputs the action does not declare (with a did-you-mean), missing required inputs, reusable-workflow inputs, and pinned-SHA comments that name the wrong version. Also flags retired runner labels (live runner-images list), script injection through ${{ github.event... }} in run:, pull_request_target checkouts of PR code, and a missing permissions key. Returns each finding with line, path, fix and doc link, per-action resolution, fix_message, and pinned_workflow: the same file with every action pinned to its full commit SHA and a # version comment (retired or missing refs move to the latest release; upgrade:true moves all). Example: {"workflow":"on: push\njobs:\n test:\n runs-on: ubuntu-latest\n steps:\n - uses: actions/checkout@v4\n - uses: actions/setup-node@v4\n with:\n node_version: 20"}. Does not run the workflow, evaluate expressions or see private repositories, secrets or repository settings. Up to 200000 characters.

    Annotations the server declares

    • title: Check a GitHub Actions workflow and pin every action to a commit SHA (live)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • tick_matchesUse 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…No 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.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Would this cron fire at a datetime?
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • tick_next_runsUse 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.1 finding

    Why it is in this group

    • The name "tick_next_runs" says "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "tick_next_runs" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "tick_next_runs" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Next cron run times in a timezone
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • vouch_check_quoteUse when a quote, a statistic or a claim is attributed to a web page and the user asks whether the source says it, or before a citation goes into an answer, report, article or essa…Reads text others writeCan send data outNo 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.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Use when a quote, a statistic or a claim is attributed to a web page and the user asks whether the source says it, or before a citation goes into an answer, report, article or essay (signals: "does this article actually say", "verify this quote", "is this citation real", "check the source", "did they really write that", "fact-check this quote against the link"). Fetches the page once, extracts its visible text and returns per quote a verdict: exact (word for word), normalized (same words in order; only punctuation, capitals, spacing or curly quotes differ), close (similarity 0.85 or more, wording differs), partial (0.5 to 0.85) or not_found, with the matching passage, surrounding context, the words that differ and numbers_differ when a number changed (for example 1914 in the quote, 1912 on the page). Quotes with "..." are checked part by part. Example: {"url":"https://en.wikipedia.org/wiki/Alan_Turing","quotes":["widely regarded as the father of theoretical computer science"]}. Limits: a match shows the words are on the page, not that the claim is true; pages built by JavaScript may have little text in their HTML; PDFs and paywalled or bot-blocked pages cannot be read; up to 10 quotes of 1000 characters, at least 3 words each.

    Annotations the server declares

    • title: Check whether a web page really contains a quote
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • xray_scan_textUse when the user asks whether text, a prompt, a SKILL.md, AGENTS.md, CLAUDE.md, .cursorrules, README, MCP tool description, PR diff, email or web page hides anything, or before an…Reads text others writeCan send data outNo 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.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Use when the user asks whether text, a prompt, a SKILL.md, AGENTS.md, CLAUDE.md, .cursorrules, README, MCP tool description, PR diff, email or web page hides anything, or before an agent follows, installs or merges instructions that came from someone else (signals: "hidden characters", "invisible unicode", "ASCII smuggling", "prompt injection in this file", "Trojan Source", "why does this string not match", "is this domain spelled with a Cyrillic letter"). Inspects every code point and returns a verdict (clean, suspicious, dangerous) with each finding's line, column, code points and Unicode names: Unicode tag characters (decoded back to the hidden ASCII message), variation-selector payloads (decoded bytes), bidirectional overrides and isolates, long zero-width runs, zero-width and other invisible characters, ANSI terminal escapes, control characters, words that mix Latin with Cyrillic or Greek look-alikes (with the Latin word they imitate, from Unicode confusables), whole look-alike words, styled math letters, unusual spaces, line separators, private-use and unassigned code points, and HTML comments that do not render. Legitimate uses are not flagged (emoji ZWJ sequences, flag tag sequences, a single emoji variation selector, joiners in Arabic and Indic text, direction marks next to Hebrew or Arabic). Give text or url (one public https text file; GitHub and GitLab file pages are read as raw). Example: {"url":"https://github.com/owner/repo/blob/main/SKILL.md"} or {"text":"Visit pаypal.com","return_clean":true}. Optional return_clean adds a copy with hidden characters removed and look-alike letters inside mixed words replaced. Decoded hidden text is returned as data. Limits: finds characters and look-alikes, not prompt injection written in plain visible words; up to 200,000 characters (files up to 1 MB, first 200,000 characters scanned).

    Annotations the server declares

    • title: Find hidden Unicode characters and look-alike letters in text or a file
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 6Show 6 read-only tools
  • deadbolt_catalog_queryUse 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, poli…Reads private data1 finding

    Why it is in this group

    • The name "deadbolt_catalog_query" says "query": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "file": it reads files.

    Findings

    • Warn

      The description names a tool "execute_sql" that this server does not list.

      Matched text

      description: "...s Supabase SQL Editor or a Supabase MCP execute_sql tool, then pass the JSON to deadbolt_check_s..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get the read-only SQL that snapshots a live Supabase database for Deadbolt
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • jig_validate_jsonUse when the user asks whether some JSON matches a JSON Schema, or when JSON from a model reply, structured output, tool call, API response or file has to be checked against its sc…No findings

    Why it is in this group

    • The name "jig_validate_json" says "validate": a word for reading.
    Description, as the server wrote it
    Use when the user asks whether some JSON matches a JSON Schema, or when JSON from a model reply, structured output, tool call, API response or file has to be checked against its schema before it is used or stored (signals: "validate this JSON", "does this match the schema", "which field is wrong", "the model returned bad JSON", "check the tool-call arguments", "why does my parser reject this"). Validates a JSON value (data), or raw model text (json_text: a ```json fence or prose around one JSON value is stripped; a syntax error comes back with line and column), against JSON Schema draft 2020-12, 2019-09, 07, 06 or 04, including $ref/$defs, anyOf/oneOf/allOf, if/then/else, unevaluatedProperties, patterns and formats (email, date-time, date, time, uuid, uri, hostname, ipv4, ipv6, duration). Returns valid true/false, every problem with its JSON Pointer path, keyword, expected and got values, and retry_message: a ready-to-send list of fixes for the model that produced the JSON. Example: {"schema":{"type":"object","properties":{"price":{"type":"number"}},"required":["price","sku"]},"data":{"price":"12.50"}}. Gives the expected answer on 6,018 of 6,227 official JSON-Schema-Test-Suite cases (ajv 8: 5,981); most misses are external $ref URLs, which are not fetched, $dynamicRef, and the idn-email, idn-hostname and iri formats, which are not checked. Not for repairing broken JSON syntax or for checking whether a schema works with OpenAI, Claude or Gemini (jig_check_schema).

    Annotations the server declares

    • title: Validate JSON against a JSON Schema (every error with its path)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • mend_query_jsonUse 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).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "mend_query_json" says "query": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "document": it reads documents.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Extract values from JSON by path
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • postcard_check_preview_tagsUse when the share-card tags need checking in HTML that is not public yet: a page being built, a localhost or staging page, a template, or a <head> block the user pasted (signals: …Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "postcard_check_preview_tags" says "preview": 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 description's first sentence says "html": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Use when the share-card tags need checking in HTML that is not public yet: a page being built, a localhost or staging page, a template, or a <head> block the user pasted (signals: "check my meta tags", "are these og tags right", "before I deploy", "Next.js metadata", "index.html head"). Reads the og: and twitter: tags in the pasted HTML with X's documented fallbacks and returns the same result as postcard_check_link_preview: the card each platform will build, problems with fixes (missing og:image or twitter:card, relative image path, title over X's 70 characters, duplicates, name= instead of property=, tags in <body>, a JavaScript app shell with no tags) and a paste-ready <meta> block. The page is not fetched; with fetch_image true, a public absolute image URL is downloaded to read its real size, format and bytes. Example: {"html":"<head><meta property=\"og:title\" content=\"Launch\"><meta property=\"og:image\" content=\"/og.png\"></head>","url":"https://example.com/launch"}. Limits: robots.txt and redirects of the page are not checked (no fetch); without url, relative image paths cannot be resolved.

    Annotations the server declares

    • title: Check share-card tags in pasted HTML (before deploy, localhost, private pages)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • tack_resolve_actionsUse when a uses: line for a GitHub Action is about to be written and its current version, commit SHA or inputs are needed, or the user asks what the latest version of an action is,…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "tack_resolve_actions" says "resolve": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "commit": it reads repositories.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Use when a uses: line for a GitHub Action is about to be written and its current version, commit SHA or inputs are needed, or the user asks what the latest version of an action is, what SHA a tag points to, or whether an action or tag exists (signals: "latest actions/checkout", "pin setup-node to a SHA", "what inputs does this action take", "does v9 exist", "which version is this SHA"). Takes owner/repo (latest release), owner/repo@ref or owner/repo/path@ref, reads the tags and branches live from github.com and the action.yml at that commit, and returns per action: exists or not, the commit SHA, the release a SHA or major tag points to, the latest release and major tag, runs.using (flags node20 and older, which GitHub stopped shipping on 2026-09-23), retired versions that fail jobs, the declared inputs, and a ready-to-paste line: uses: owner/repo@<40-char sha> # vX.Y.Z. Example: {"actions":["actions/checkout","actions/setup-node@v4","docker/build-push-action@v6"]}. Up to 30 per call. Public github.com repositories only; for a whole workflow file use tack_check_workflow.

    Annotations the server declares

    • title: Look up GitHub Actions: latest release, commit SHA, runtime and inputs (live)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • tokendiet_count_tokensUse when the user asks how many tokens a text, prompt, log, document or code paste is, whether it fits a context window (128K, 200K, 1M), or how big something is before they send i…Reads private dataNo findings

    Why it is in this group

    • The name "tokendiet_count_tokens" says "count": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "document": it reads documents.
    Description, as the server wrote it
    Use when the user asks how many tokens a text, prompt, log, document or code paste is, whether it fits a context window (128K, 200K, 1M), or how big something is before they send it to an AI. Returns the exact o200k token count (GPT-4o family and later; Claude and Gemini usually within about 15%), plus words, characters and how much of each window it uses. Counts are exact for that tokenizer. Example: {"text": "<the text to measure>"}. Not for shortening text.

    Annotations the server declares

    • title: Count the exact tokens in a text
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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.

576 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 4 private-data tools breaks every one.

Reads private data4
Reads files, mail, messages, databases, secrets, calendars or repositories.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__studio__deadbolt_catalog_query",
      "mcp__studio__mend_query_json",
      "mcp__studio__tack_resolve_actions",
      "mcp__studio__tokendiet_count_tokens"
    ]
  }
}

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 19, 2026, 17:25 UTC, unchanged since Nov 19, 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
30
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
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 30 tools that change things (1 irreversible, 29 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.clawhard.com/mcp: tools/list returned 36 tools to an anonymous client, including meridian_convert_time (irreversible), runsheet_create_schedule (write), halves_settle_up (write), halves_create_group_link (write), doorman_check_ai_bot_access (write) and 25 more

    What this check looks for

Posture changes

  1. Nov 19, 2026
    • Tools that change things, listed without credentials: 24 to 30
  2. Nov 5, 2026
    • Tools that change things, listed without credentials: 7 to 24

Findings

Matches of fixed checks, with the text they matched.

2 high6 warn8 info
  • The description refers to ".env".

    Matched text

    description: "...ste, commit, share, log or send code, a .env file, a diff, config, logs, a stack tra..."

    What this check looks for
  • The input schema at properties.text.description refers to ".env".

    Matched text

    inputSchema.properties.text.description: "The text to scan: code, a diff, .env, config, logs, a stack trace, a chat or..."

    What this check looks for
  • The server marks "meridian_convert_time" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "meridian_convert_time" says "convert": a word for a change.

    What this check looks for
  • The server marks "deadbolt_check_supabase_access" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.sql), which can change anything it can reach.

    What this check looks for
  • The description names a tool "execute_sql" that this server does not list.

    Matched text

    description: "...s Supabase SQL Editor or a Supabase MCP execute_sql tool, then pass the JSON to deadbolt_check_s..."

    What this check looks for
  • The server marks "tick_next_runs" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "tick_next_runs" says "run": a word for a change.

    What this check looks for
Show 10 more findings
  • The server marks "vouch_check_links" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "vouch_check_links" says "link": a word for a change.

    What this check looks for
  • The server marks "postcard_check_link_preview" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "postcard_check_link_preview" says "link": a word for a change.

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

    Matched text

    description: "...ck trace or a prompt that might contain credentials, for example "did I leak a key in this?..."

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

    Matched text

    description: "...rol-Allow-Headers", "withCredentials", "credentials include"). Sends the browser's own pref..."

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

    Matched text

    inputSchema.properties.credentials.description: "...e when the request sends cookies: fetch credentials: "include", XHR or axios withCredential..."

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

    Matched text

    description: "...age origin, method, request headers and credentials mode. Returns the same result as border..."

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

    Matched text

    inputSchema.properties.credentials.description: "...e when the request sends cookies: fetch credentials: "include", XHR or axios withCredential..."

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

    Matched text

    description ends: "...rs can change them, and very large schemas can still hit unpublished size limits."

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

    Matched text

    description ends: "...ee private repositories, secrets or repository settings. Up to 200000 characters."

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

    Matched text

    description ends: "...l when clean), error? and hint? (invalid patterns), notes, checked_at, open_url}."

    What this check looks for

History

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

  1. Tools2 added.+2 addedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 24 -> 30.View diff
    • Tools that change things, listed without credentials: 24 to 30
  3. Tools2 added.+2 addedView diff
  4. Tools2 added.+2 addedView diff
  5. Tools1 added.+1 addedView diff
  6. Tools2 added.+2 addedView diff
  7. Tools2 added.+2 addedView diff
  8. Tools2 added.+2 addedView diff
  9. Tools1 added, 1 changed.+1 added~1 changedView diff
  10. Tools1 added, 9 removed, 12 changed.+1 added−9 removed~12 changedView diff

Install

Pinned to version 1.21.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http studio https://mcp.clawhard.com/mcp
claude mcp add --transport http studio https://mcp.clawhard.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__studio__tokendiet_count_tokens",
      "mcp__studio__mend_query_json",
      "mcp__studio__deadbolt_catalog_query",
      "mcp__studio__jig_validate_json",
      "mcp__studio__tack_resolve_actions"
    ],
    "ask": [
      "mcp__studio__runsheet_create_schedule",
      "mcp__studio__halves_settle_up",
      "mcp__studio__halves_create_group_link",
      "mcp__studio__doorman_check_ai_bot_access",
      "mcp__studio__swatch_check_contrast",
      "mcp__studio__swatch_fix_contrast",
      "mcp__studio__swatch_make_scale",
      "mcp__studio__swatch_check_pairs",
      "mcp__studio__meridian_now",
      "mcp__studio__meridian_convert_time",
      "mcp__studio__meridian_meeting_slots",
      "mcp__studio__meridian_zone_info",
      "mcp__studio__mend_repair_json",
      "mcp__studio__mend_outline_json",
      "mcp__studio__deadbolt_check_supabase_access",
      "mcp__studio__spill_scan_secrets",
      "mcp__studio__stamp_check_email_domain",
      "mcp__studio__stamp_check_dns_record",
      "mcp__studio__tick_next_runs",
      "mcp__studio__tick_matches",
      "mcp__studio__notary_check_packages",
      "mcp__studio__xray_scan_text",
      "mcp__studio__vouch_check_links",
      "mcp__studio__vouch_check_quote",
      "mcp__studio__border_check_cors",
      "mcp__studio__border_check_cors_headers",
      "mcp__studio__postcard_check_link_preview",
      "mcp__studio__postcard_check_preview_tags",
      "mcp__studio__stake_check_domains",
      "mcp__studio__jig_check_schema",
      "mcp__studio__tack_check_workflow",
      "mcp__studio__sieve_test_regex",
      "mcp__studio__sieve_check_redos"
    ],
    "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 studio. Review it before you use it.

Capability tags behind 20 rules
  • mcp__studio__tokendiet_count_tokens private-data
  • mcp__studio__runsheet_create_schedule untrusted-input
  • mcp__studio__halves_create_group_link untrusted-input
  • mcp__studio__doorman_check_ai_bot_access untrusted-input, outbound
  • mcp__studio__meridian_convert_time outbound
  • mcp__studio__mend_query_json private-data, untrusted-input
  • mcp__studio__deadbolt_catalog_query private-data
  • mcp__studio__stamp_check_email_domain untrusted-input
  • mcp__studio__stamp_check_dns_record untrusted-input
  • mcp__studio__notary_check_packages untrusted-input
  • mcp__studio__xray_scan_text untrusted-input, outbound
  • mcp__studio__vouch_check_links untrusted-input, outbound
  • mcp__studio__vouch_check_quote untrusted-input, outbound
  • mcp__studio__border_check_cors untrusted-input, outbound
  • mcp__studio__border_check_cors_headers outbound
  • mcp__studio__postcard_check_link_preview untrusted-input, outbound
  • mcp__studio__postcard_check_preview_tags untrusted-input, outbound
  • mcp__studio__stake_check_domains untrusted-input
  • mcp__studio__tack_check_workflow untrusted-input
  • mcp__studio__tack_resolve_actions private-data, 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.clawhard/studio/verify?hash=f7b0671ca89afa790568fffe46aa5981099353d1143c6654771f71efa73153af" | jq -e '.changed == false'

Pinned hash f7b0671ca89a, from Nov 20, 2026, 16:18 UTC.

Watch

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

https://radar.anlyon.com/servers/com.clawhard/studio/changes.xml

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

Badge

Anlyon Radar badge for com.clawhard/studio
[![Anlyon Radar](https://radar.anlyon.com/badge/com.clawhard/studio.svg)](https://radar.anlyon.com/servers/com.clawhard/studio)

Source: MCP Registry. Synced Nov 20, 2026, 16:17 UTC.

Clawhard Studio MCP server: questions and answers

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

Is the Clawhard Studio MCP server safe?

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

Can the Clawhard Studio MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Clawhard Studio MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: meridian_convert_time.

What tools does the Clawhard Studio MCP server have?

38 tools: 1 irreversible, 31 write, 6 read. meridian_convert_time, runsheet_create_schedule, halves_settle_up, halves_create_group_link, doorman_check_ai_bot_access, swatch_check_contrast, swatch_fix_contrast, swatch_make_scale and 30 more.

Does the Clawhard Studio MCP server need sign-in or OAuth?

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

Does the Clawhard Studio MCP server send data to outside services?

9 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): doorman_check_ai_bot_access, meridian_convert_time, xray_scan_text, vouch_check_links, vouch_check_quote, border_check_cors and 3 more.

Has the Clawhard Studio MCP server changed its tools?

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