booklint stamp
REMOTE · BOOKLINT-STAMP.FLY.DEV
Signed timestamp receipts for a SHA-256 hash. Send only the hash; we never see the document.
Available components
Last scanned (20 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Security
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 369 tokens (~184/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 33% of tool parameters carry a description.Partial
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 3 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
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.
- 17 Oct 26 +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.
- 15 Oct 26 +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.
- 13 Oct 26 +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.
- 11 Oct 26 +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.
- 10 Oct 26 +2
- Stability: unverified → 0.13 ▲ functional
- 6 Oct 26 59
First indexed and scored.
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 18 Oct 2026 · Probed https://booklint-stamp.fly.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.fly.dev | CN=YE1,O=Let's Encrypt,C=US | 21 Aug 2026 | 19 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 688c4daf5300c51e0a5c1f6837a3a67a868 |
| SANs: *.fly.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of booklint-stamp.fly.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| fly.dev. | absent | 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 |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://booklint-stamp.fly.dev/mcp | Verified | 200 | |
| http (plaintext) | http://booklint-stamp.fly.dev/mcp | HTTPS enforced | 301 | https://booklint-stamp.fly.dev/mcp |
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 →
stamp_hash Stamp a SHA-256 hash ~125
Returns a signed receipt {sha256, stamped_at, key_id, signature, public_key_url}: a booklint-family service saw this hash at stamped_at, signed with key key_id. Send ONLY a SHA-256 hex digest (64 characters). We never see or store the document — only the hash you send. This is not legal proof, notary service, evidence, or a certificate of anything. Not advice.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Optional key. Same as the Bearer header. |
| sha256 | string | yes | 64 hex characters you computed yourself. |
No output schema declared.
No examples provided.
verify_receipt Verify a stamp receipt ~145
Checks a receipt from stamp_hash against the published public keys (same check as POST /v1/verify; pass the receipt fields as arguments). Returns valid true or false with a reason. valid true means only that this service signed that hash and time with that key. This is not legal proof, notary service, evidence, or a certificate of anything.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Optional key. Same as the Bearer header. |
| key_id | string | yes | – |
| public_key_url | string | – | – |
| sha256 | string | yes | – |
| signature | string | yes | – |
| stamped_at | string | yes | – |
| statement | string | – | – |
No output schema declared.
No examples provided.
How do I install the booklint stamp MCP server?
booklint stamp is a hosted endpoint at https://booklint-stamp.fly.dev/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.
remote · booklint-stamp.fly.dev
claude mcp add --transport http com-booklint-stamp 'https://booklint-stamp.fly.dev/mcp'
What is the booklint stamp MCP server?
booklint stamp is an MCP server listed in the public MCP registry as com.booklint/stamp. Signed timestamp receipts for a SHA-256 hash. Send only the hash; we never see the document. This page covers its hosted endpoint (https://booklint-stamp.fly.dev/mcp).
Is the booklint stamp MCP server safe to use?
booklint stamp scores 65 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 booklint stamp MCP server expose?
booklint stamp exposes 2 tools: stamp_hash, verify_receipt. Their descriptions and schemas cost roughly 270 tokens of context every time the server is loaded.
Does the booklint stamp MCP server require authentication?
No. We connected to booklint stamp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the booklint stamp MCP server still maintained?
booklint stamp is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.