llms.ink
REMOTE · LLMS.INK
Any link as llms.txt; check llms.txt; see how AI crawlers read a page; draft AGENTS.md.
Available components
Last scanned (14 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Code Search and Documentation
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 Security63
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1631 tokens (~233/item across 7 items; 7 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 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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 →
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.
- 20 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “llms_txt” rewrote its description, which is the text the model reads security
- 18 Nov 26 0
- Schema quality: 206 → 230 ▼ functional
- Server version: 0.6.0 → 0.7.0 functional
- “llms_full_txt” added an optional parameter “crawl” cosmetic
- “llms_txt” added an optional parameter “crawl” cosmetic
- 17 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.
- 14 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_llms_txt” rewrote its description, which is the text the model reads security
- Schema quality: 162 → 206 ▼ functional
- Schema quality: 162 → 205 ▼ functional
- Schema quality: 649 → 891 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.5.0 → 0.6.0 functional
- Server version: 0.4.0 → 0.5.0 functional
- Server version: 0.2.0 → 0.4.0 functional
- New tool “agent_view” functional
- New tool “generate_draft” functional
- New tool “create_clip_link” functional
- “check_llms_txt” added an optional parameter “base” cosmetic
- “check_llms_txt” added an optional parameter “links” cosmetic
- “check_llms_txt” added an optional parameter “text” cosmetic
- “check_llms_txt” reworded the description of “url” cosmetic
- “check_llms_txt” made “url” optional cosmetic
- Tool “check_llms_txt” changed its title: Check a published llms.txt → Check an llms.txt cosmetic
- 13 Nov 26 66
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 21 Nov 2026 · Probed https://llms.ink/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=llms.ink | CN=WE1,O=Google Trust Services,C=US | 9 Nov 2026 | 7 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 59a54092b9ae8bca134529f6c3d0da1b |
| SANs: llms.ink, www.llms.ink, *.www.llms.ink | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of llms.ink. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ink. | DS published | 19420 | 13 | Verified |
| llms.ink. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://llms.ink/mcp | Verified | 200 | |
| http (plaintext) | http://llms.ink/mcp | Inconclusive | 405 |
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 →
agent_view What AI agents see on a page ~175
Report how AI crawlers and agents see a page: robots.txt per AI bot (search, user fetches, training) and Content-Signal, firewall blocks found by fetching with bot User-Agents, text present without JavaScript, what survives Markdown conversion, title/first paragraph/facts/noindex/canonical/sitemap, hidden instructions, and llms.txt, .md URLs, Accept: text/markdown, Link headers, ard.json. Each check is pass/warn/fail/info with a fix; robots.txt and header fixes include the changed file. Use it to tell a site owner why assistants can’t read or cite a page and what to change.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | A site or any page on it, e.g. "example.com" or "docs.example.com/guide". The scheme is optional. |
No output schema declared.
No examples provided.
check_llms_txt Check an llms.txt ~252
Check an llms.txt against the format (H1 title, blockquote summary, H2 sections of `- [name](url): notes` links) and size. Pass `url` to check the file a site publishes, including whether its first 25 links answer; or pass `text` to check a file you have (a draft, a local copy), with `base` for where it lives and `links` to also test its links. Returns a short report with each issue and its line, and the sections with their link counts.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | – | With text: the site or llms.txt link it belongs to, e.g. "example.com". Resolves relative links. |
| links | boolean | – | With text: also check that its first 25 links answer (and llms-full.txt next to base). Default false. |
| text | string | – | The llms.txt itself (up to 2 MB), instead of url. |
| url | string | – | A site, a docs section, or the llms.txt itself, e.g. "llmstxt.org" or "docs.astro.build/llms.txt". Use url or text. |
No output schema declared.
No examples provided.
create_clip_link Open a transcript passage as a clip ~188
Return a Gimmeclip selection link for 0.5–60 seconds of a public YouTube, Instagram, TikTok, X, Facebook, Bluesky, VK, LinkedIn or Weibo video. Read llms_full_txt first to choose source-video timestamps. The user opens the link to preview, adjust and create the clip. Does not render, download, or verify that the video is available. For a finished watch link use share_video on https://gimmeclip.com/mcp.
| Name | Type | Req | Description |
|---|---|---|---|
| end | number | yes | End in source-video seconds; 0.5–60 seconds after start. |
| start | number | yes | Start in source-video seconds. |
| url | string | yes | Any public http(s) link, e.g. "docs.stripe.com/payments", "github.com/honojs/hono", a PDF or a video URL. The scheme is optional. |
No output schema declared.
No examples provided.
generate_draft Draft AGENTS.md, JSON-LD, alt text or answer-first headings ~220
Draft fixes for a site or repo owner to review, each tied to its sources. kind `agents-md`: an AGENTS.md (setup, commands, layout, conventions) for a GitHub repo or docs site, every line citing its file and line. `jsonld`: WebSite/Organization/Product/SoftwareApplication JSON-LD built only from facts on the site. `alt-text`: alt text for images missing it, from image descriptions. `answers`: per H2 section, a question-shaped heading and an answer-first sentence drawn only from that section. Drafts never contain URLs, commands or numbers not in the sources. Cached 24h; counts as a new link.
| Name | Type | Req | Description |
|---|---|---|---|
| fresh | boolean | – | Ignore the 24h cache and regenerate. Default false. |
| kind | string | yes | What to draft. |
| url | string | yes | Any public http(s) link, e.g. "docs.stripe.com/payments", "github.com/honojs/hono", a PDF or a video URL. The scheme is optional. |
No output schema declared.
No examples provided.
llms_full_txt llms-full.txt for a link ~224
Get llms-full.txt for any link: the llms.txt index followed by the full Markdown of up to 20 pages it links to (or the page/document itself; for a video, its description and timestamped transcript). Can be large — prefer llms_txt when you only need to find pages. Cached 24h.
| Name | Type | Req | Description |
|---|---|---|---|
| crawl | integer | – | A channel or profile only: how many of its newest items are opened and described (0–10). Defaults: YouTube 5, GitHub 5, Instagram 4, TikTok 4, X 5. Another depth is cached apart and, when built, coun… |
| fresh | boolean | – | Ignore the 24h cache and rebuild. Default false. |
| url | string | yes | Any public http(s) link, e.g. "docs.stripe.com/payments", "github.com/honojs/hono", a PDF or a video URL. The scheme is optional. |
No output schema declared.
No examples provided.
llms_txt llms.txt for a link ~206
Get an llms.txt index for any link: title, one-line summary, and sections of the most useful links with short descriptions. Returns the site’s own llms.txt when it has one, with hidden instructions removed. Cached 24h.
| Name | Type | Req | Description |
|---|---|---|---|
| crawl | integer | – | A channel or profile only: how many of its newest items are opened and described (0–10). Defaults: YouTube 5, GitHub 5, Instagram 4, TikTok 4, X 5. Another depth is cached apart and, when built, coun… |
| fresh | boolean | – | Ignore the 24h cache and rebuild. Default false. |
| url | string | yes | Any public http(s) link, e.g. "docs.stripe.com/payments", "github.com/honojs/hono", a PDF or a video URL. The scheme is optional. |
No output schema declared.
No examples provided.
video_frame Frame of a video ~149
Get one frame of a video (YouTube, Instagram, X, TikTok, a direct .mp4 link…) as a JPEG image, to see what is on screen at a given time. Pair with llms_full_txt: the transcript is timestamped.
| Name | Type | Req | Description |
|---|---|---|---|
| t | string | – | Time in the video: seconds ("90", "90.5") or "1:30" / "1:02:03". Default "0". |
| url | string | yes | The video link, e.g. "youtube.com/watch?v=…" or "instagram.com/reel/…". The scheme is optional. |
| width | integer | – | Maximum width in pixels. Default 1280. |
No output schema declared.
No examples provided.
How do I install the llms.ink MCP server?
llms.ink is a hosted endpoint at https://llms.ink/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 · llms.ink
claude mcp add --transport http ink-llms-llms-ink 'https://llms.ink/mcp'
What is the llms.ink MCP server?
llms.ink is an MCP server listed in the public MCP registry as ink.llms/llms-ink. Any link as llms.txt; check llms.txt; see how AI crawlers read a page; draft AGENTS.md. This page covers its hosted endpoint (https://llms.ink/mcp).
Is the llms.ink MCP server safe to use?
llms.ink scores 68 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 llms.ink MCP server expose?
llms.ink exposes 7 tools: create_clip_link, llms_txt, llms_full_txt, video_frame, check_llms_txt, and 2 more. Their descriptions and schemas cost roughly 1,414 tokens of context every time the server is loaded.
Does the llms.ink MCP server require authentication?
No. We connected to llms.ink without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the llms.ink MCP server still maintained?
llms.ink 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 llms.ink MCP server?
VerifyMCP ran 12 checks on llms.ink, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about llms.ink: HTTPS. 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.