b59.link
REMOTE · B59.LINK
Short links, QR codes and page-view trackers for AI agents, with click stats and email-code sign-up.
Available components
Last scanned (5 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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 Security74
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability76
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1020 tokens (~113/item across 9 items; 9 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; 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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 28 Oct 26 +34
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 94 functional
- First check of Schema quality: good functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 27 Oct 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 26 Oct 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
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 5 Nov 2026 · Probed https://b59.link/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=b59.link | CN=YE1,O=Let's Encrypt,C=US | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 54ac2c0bcb05c9d89b5503b64dc965bd9cf |
| SANs: b59.link, www.b59.link | ||||||
| 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 b59.link. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| link. | present | 16766 | 13 | Verified |
| b59.link. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://b59.link/api/mcp | Verified | 200 | |
| http (plaintext) | http://b59.link/api/mcp | HTTPS enforced | 301 | https://b59.link/api/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 →
auth Sign in to b59.link ~142
Sign in to b59.link to own what you create (and for 300 requests/minute on the REST API). Pass api_key to get a session key straight away. Or pass email to have a 6-digit code emailed, then call again with email and otp to get a session key (new emails are signed up and also get their api_key). Send the session key as the HTTP header 'Authorization: Bearer <session_key>'.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | The account's 256-character API key. |
| string | – | Email to send a one-time code to. | |
| otp | string | – | The 6-digit code from the email. |
No output schema declared.
No examples provided.
create_tracker Create a page-view tracker ~114
Create a free page-view tracker for a website. Returns the tag image URL and ready-to-paste snippets for the site's pages, plus the stats URL where views, visitors, pages and referrers are shown. When signed in, the tracker belongs to the account; otherwise keep the manage_token to claim it later.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Optional display name for the tracker. |
| site_url | string | yes | The site's address, e.g. example.com. Views are only counted on this domain and its subdomains. |
No output schema declared.
No examples provided.
generate_qr Make a tracked QR code ~71
Generate a trackable QR code for a URL. Creates a b59.link short URL at the same time so scans are counted. Returns the short URL, a stats URL, and the QR code as a base64-encoded PNG.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL to generate a QR code for. |
No output schema declared.
No examples provided.
get_stats_url Find a stats page ~93
Get the stats page URL for anything b59.link tracks: a slug or short URL, the destination URL of a short link or QR code, a tracker id or tag URL, or any page URL / domain that has a tracker tag. Stats themselves are viewed on b59.link; this returns where.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Slug, short URL, page URL, domain, tracker id or tag URL. |
No output schema declared.
No examples provided.
get_watch_report Get a printed-link watch report ~79
Get the state of every link in a printed-link watch: working, dead, moved, deactivated page, redirect changed or certificate expiring, what changed since the first check, the latest redirect chain and the last 30 days.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The watch's slug or its page_url (b59.link/w/<slug>). |
No output schema declared.
No examples provided.
lookup_url Look up an existing short link ~57
Check whether a URL already has a b59.link short URL. Handles variations: http/https, www prefix, trailing slash. Returns the existing short URL and QR code if found.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL to look up. |
No output schema declared.
No examples provided.
make_qr_image Make a QR code image ~158
Make a QR code image for any text (URL, Wi-Fi string, phone, email, plain text) without creating a short link. Supports colors, size and SVG. Returns the image plus a permanent image URL that can be embedded with <img src>. Use generate_qr instead when scans should be counted.
| Name | Type | Req | Description |
|---|---|---|---|
| bg | string | – | Background hex color, e.g. ffffff. |
| data | string | yes | Text to encode (max 1500 chars). |
| fg | string | – | Foreground hex color, e.g. 000000. |
| format | string | – | Image format (default png). |
| size | integer | – | Width/height in pixels, 64-1200 (default 300). |
No output schema declared.
No examples provided.
shorten_url Shorten a URL ~83
Shorten a long URL and get a memorable b59.link short URL. Optionally specify a custom slug. Returns the short URL and a stats URL.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | – | Optional custom slug (letters, digits, hyphens, underscores, max 100 chars). A random slug is used if omitted. |
| url | string | yes | The URL to shorten. |
No output schema declared.
No examples provided.
watch_printed_links Watch printed links ~176
Watch up to 25 printed links (QR codes on menus, short links on flyers, posters, packaging, cards). Checks each one now and then once a day, and records the whole redirect chain. A link is flagged when it dies (fails twice, 6 hours apart), lands somewhere new, lands on a QR or short-link vendor's 'deactivated' page or a parked domain, changes how it redirects, or its certificate expires within 14 days. Returns the first results, page_url (a result page to hand to the person; shareable) and manage_url (private: edit, re-check, delete). No key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Optional address for alerts; nothing is sent to it until it is confirmed with a code on the result page. | |
| links | array | yes | – |
No output schema declared.
No examples provided.
How do I install the b59.link MCP server?
b59.link is a hosted endpoint at https://b59.link/api/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 · b59.link
claude mcp add --transport http link-b59-b59-link 'https://b59.link/api/mcp'
What is the b59.link MCP server?
b59.link is an MCP server listed in the public MCP registry as link.b59/b59-link. Short links, QR codes and page-view trackers for AI agents, with click stats and email-code sign-up. This page covers its hosted endpoint (https://b59.link/api/mcp).
Is the b59.link MCP server safe to use?
b59.link scores 72 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 b59.link MCP server expose?
b59.link exposes 9 tools: auth, shorten_url, generate_qr, create_tracker, get_stats_url, and 4 more. Their descriptions and schemas cost roughly 973 tokens of context every time the server is loaded.
Does the b59.link MCP server require authentication?
No. We connected to b59.link without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the b59.link MCP server still maintained?
b59.link is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.