Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Bolt Claw documentation

REMOTE · BOLTCLAW.AI

Search and read the Bolt Claw API documentation. Read-only, and no key needed.

Available components

+3 this week 87 Trust /100

Last scanned (18 hours ago)

Scores higher than 91% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Code Search and Documentation

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security97
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server, and every tool looks verifiably read-only (it declares readOnlyHint: true, starts its name with a read verb and describes no write), so an anonymous caller can read but cannot change anything. We can't see whether a tool returns data specific to one caller, so keep any per-user data behind authorisation. View diagnostics → Pass
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2653 tokens (~31/item across 83 items; 2 tools + 81 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 0
    • Resource “Webhooks” now points somewhere else: https://boltclaw.ai/docs/webhooks.md → https://boltclaw.ai/docs/api/webhooks.md security
  • 20 Nov 26 0
    • Resource “Webhooks” now points somewhere else: https://boltclaw.ai/docs/webhooks.md → https://boltclaw.ai/docs/api/webhooks.md security
  • 19 Nov 26 +1
    • Resource “Webhooks” now points somewhere else: https://boltclaw.ai/docs/webhooks.md → https://boltclaw.ai/docs/api/webhooks.md security
  • 18 Nov 26 0
    • Resource “Webhooks” now points somewhere else: https://boltclaw.ai/docs/webhooks.md → https://boltclaw.ai/docs/api/webhooks.md security
  • 17 Nov 26 +1
    • Resource “Webhooks” now points somewhere else: https://boltclaw.ai/docs/webhooks.md → https://boltclaw.ai/docs/api/webhooks.md security
  • 16 Nov 26 0
    • Resource “Webhooks” now points somewhere else: https://boltclaw.ai/docs/webhooks.md → https://boltclaw.ai/docs/api/webhooks.md security
  • 15 Nov 26 +1
    • Resource “Webhooks” now points somewhere else: https://boltclaw.ai/docs/webhooks.md → https://boltclaw.ai/docs/api/webhooks.md security
  • 14 Nov 26 0
    • Resource “Webhooks” now points somewhere else: https://boltclaw.ai/docs/webhooks.md → https://boltclaw.ai/docs/api/webhooks.md security
    • New resource “Invites inside an AI assistant” functional
    • Server version: 1.52.0 → 1.53.0 functional
    • Server version: 1.35.0 → 1.52.0 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://boltclaw.ai/docs/mcp-server

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=boltclaw.ai CN=YR1,O=Let's Encrypt,C=US 24 Oct 2026 22 Jan 2027 RSA 2048 SHA256-RSA 60127cffd8dcaa1d264eb433590318b736a
SANs: boltclaw.ai
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of boltclaw.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
boltclaw.ai. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://boltclaw.ai/docs/mcp-server Verified 200
http (plaintext) http://boltclaw.ai/docs/mcp-server HTTPS enforced 308 https://boltclaw.ai/docs/mcp-server
MCP tools · 2 exposed · ~158 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
fetch ~70

Read one documentation page in full, as markdown. The id is what `search` returns, which is the page's path without /docs/ - for example `authentication` or `api/pages`.

NameTypeReqDescription
idstringyesA page id from `search`, such as "errors" or "api/posts".

No output schema declared.

No examples provided.

search ~88

Find documentation pages about a subject. Returns an id, a title, a URL and a matching line for each hit, best first. Pass the id to `fetch` to read the page.

NameTypeReqDescription
limitinteger–How many results to return. Defaults to 8.
querystringyesWhat to look for, in a few words. Matched against titles, sections and text.

No output schema declared.

No examples provided.

Install

How do I install the Bolt Claw documentation MCP server?

Bolt Claw documentation is a hosted endpoint at https://boltclaw.ai/docs/mcp-server, 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.

remote · boltclaw.ai

# add to Claude Code
claude mcp add --transport http ai-boltclaw-docs 'https://boltclaw.ai/docs/mcp-server'
Common questions

What is the Bolt Claw documentation MCP server?

Bolt Claw documentation is an MCP server listed in the public MCP registry as ai.boltclaw/docs. Search and read the Bolt Claw API documentation. Read-only, and no key needed. This page covers its hosted endpoint (https://boltclaw.ai/docs/mcp-server).

Is the Bolt Claw documentation MCP server safe to use?

Bolt Claw documentation scores 87 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 Bolt Claw documentation MCP server expose?

Bolt Claw documentation exposes 2 tools: search, fetch. Their descriptions and schemas cost roughly 158 tokens of context every time the server is loaded.

Does the Bolt Claw documentation MCP server require authentication?

No. We connected to Bolt Claw documentation without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Bolt Claw documentation MCP server still maintained?

Bolt Claw documentation 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 Bolt Claw documentation MCP server?

VerifyMCP ran 13 checks on Bolt Claw documentation, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.