CrawlCheck

Agent view · Findings · 2026-11-13

Both our SDKs cut a tool list at 300 with no warning

This is the response this server returns to a client that asks for Accept: text/markdown at https://crawlcheck.io/blog/our-sdks-cut-a-tool-list-at-300-with-no-warning: fetched when you opened this page, shown byte for byte. An assistant, a crawler that negotiates markdown, or anything reading our feed gets exactly this. The markdown leaves signed (RFC 9421, key in our key directory), so a crawler can prove the page it read is the page this server sent; the check is shown below.

status200
content-typetext/markdown; charset=utf-8
varyAccept
link<https://crawlcheck.io/llms.txt>; rel="describedby"; type="text/plain", <https://crawlcheck.io/.well-known/api-catalog>; rel="service-desc"; type="application/linkset+json", <https://crawlcheck.io/blog/our-sdks-cut-a-tool-list-at-300-with-no-warning>; rel="cite-as", <https://crawlcheck.io/.well-known/http-message-signatures-directory>; rel="http-message-signatures-directory"
cache-controlpublic, max-age=900, stale-while-revalidate=2400
bytes10,785
words1,510
sha-256cadab0133c231c573011b3e9b6512f98e6acad9c3e42d41ce64671cc86d47596
repr-digestsha-256=:ytqwEzwjHFcwEbPptlEvmOasrZw+QtQc5kZxzIbUdZY=: ← matches the body shown
signature-inputsig1=("@authority";req "@path";req "repr-digest" "content-type");created=1795179721;expires=1795183321;keyid="1hHmE3fo1rg5Ig70wuFtJ5wBc7G-sUTgUJkxyPWFRps";alg="ed25519";nonce="OX43Txy5_3NA9hwARX_GOw";tag="crawlcheck-page"
signaturesig1=:U2pXO1Uv5vyjDefuZqCRZwKMmXzhZkugaYEi5Uf6NvWsGMzHoMgaCHrdW6g1vqlCe+t2son1UyHKE6KcfeM4Bg==:
verifiedyes — signature by key 1hHmE3fo1rg5Ig70… from https://crawlcheck.io/.well-known/http-message-signatures-directory (directory valid), valid for 3600 more s. Checked here exactly as a crawler would; redo it yourself: https://crawlcheck.io/api/tool/wba
Findings · 2026-11-13 · By [VSNARY | Emmanuel Orta](/author)

# Both our SDKs cut a tool list at 300 with no warning

A fingerprint of an MCP server's tools is only useful if it covers all of them. Ours stopped at 300 and did not say so.

Until 11 November 2026, CrawlCheck's MCP lockfile and both SDKs fingerprinted only the first 300 tools a server listed and did not mark the result as cut. A change to tool 301 or later left the fingerprint unchanged. Now every tool is listed, a list that could not be read in full is marked incomplete, and a check against an incomplete list answers block. Upgrade to @crawlcheck/sdk 1.14.0 or crawlcheck 1.15.0 on PyPI, or later.

On this page

- The defect
- Before and after
- What we changed
- What to do

Three cases, before and now

Server lists 301 tools

Before

Fingerprint of the first 300, no mark

Now

All 301 listed

Server’s list could not be read to the last page

Before

Fingerprint of what was read, no mark

Now

Marked incomplete

Checking against an incomplete list

Before

Could pass

Now

Answers incomplete, decision block

An [MCP server](/glossary/mcp-server) tells an agent which tools it offers. We record a fingerprint of that list so an agent can notice when a server's tools change after it was approved. The point of the fingerprint is that any change shows.

## The defect #

Our code read up to 300 tools and built the fingerprint from those. A server with more than 300 got a fingerprint of the first 300, and nothing in the result said the list had been cut. If tool 301 changed, or a new tool was added past that point, the fingerprint stayed the same and a check against it passed.

Most servers list far fewer than 300 tools, which is why this sat unnoticed. That does not make it acceptable: the servers with the most tools are the ones where a silent change is easiest to hide.

## Before and after #

| Case | Before | Now |
| --- | --- | --- |
| Server lists 301 tools | Fingerprint of the first 300, no mark | All 301 listed |
| Server's list could not be read to the last page | Fingerprint of what was read, no mark | Marked incomplete |
| Checking against an incomplete list | Could pass | Answers incomplete, decision block |

## What we changed #

The lockfile now lists every tool. The SDKs read the server's tool list to its last page. Where a list still cannot be read in full, the result says so, and a check against it does not pass. We confirmed it on the packages as published: a 301-tool list comes back with 301 entries.

## What to do #

If you use the JavaScript SDK, move to @crawlcheck/sdk 1.14.0 or later. If you use Python, move to crawlcheck 1.15.0 or later. If you pinned a lockfile for a server with more than 300 tools before 11 November 2026, create it again, because the old one does not cover the whole list.

If you build something similar, the rule we took from this: a limit is fine, a silent limit is not. Anything that stops early has to say that it stopped. More on what agents can verify is in [our guide to agent checks](/guides/how-an-ai-agent-verifies-a-website-before-it-acts).

CrawlCheck’s dataset when this page loaded: 570,959 sites measured.

Written by

[Emmanuel Orta](/author) · VSNARY

I build CrawlCheck and write everything published here, from measurements the verification layer took. Where a post got something wrong, the correction stays in the post.

[Every post, and where I got it wrong →](/author) · [Follow on LinkedIn →](https://www.linkedin.com/in/emmanuelorta)

Share this finding: [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Four-sdks-cut-a-tool-list-at-300-with-no-warning%3Futm_source%3Dlinkedin%26utm_medium%3Dsocial%26utm_campaign%3Dshare)[X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Four-sdks-cut-a-tool-list-at-300-with-no-warning%3Futm_source%3Dx%26utm_medium%3Dsocial%26utm_campaign%3Dshare&text=Both%20our%20SDKs%20cut%20a%20tool%20list%20at%20300%20with%20no%20warning)[Email](mailto:?subject=Both%20our%20SDKs%20cut%20a%20tool%20list%20at%20300%20with%20no%20warning&body=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Four-sdks-cut-a-tool-list-at-300-with-no-warning)[Follow Emmanuel on LinkedIn](https://www.linkedin.com/in/emmanuelorta)

## Questions this post answers

### What was wrong with the CrawlCheck SDKs?

They fingerprinted only the first 300 tools of an MCP server and did not mark the result as cut, so a change past tool 300 went unnoticed.

### Which versions fix it?

@crawlcheck/sdk 1.14.0 on npm and crawlcheck 1.15.0 on PyPI, and every later version.

### Do I need to recreate my lockfile?

Only if the server lists more than 300 tools and the lockfile was made before 11 November 2026. For smaller servers the fingerprint already covered everything.

### What happens now when a tool list cannot be read in full?

The result is marked incomplete, and a check against it answers incomplete with the decision block instead of passing.

## Related findings

[2026-11-14 One in four MCP hosts changed its tools in four days. Nothing told the agent. We re-read every public MCP server. 706 of 3,167 hosts changed their tool list in four days, and most changes kept the same versio](/blog/one-in-four-mcp-hosts-changed-its-tools-in-four-days)[2026-10-15 MCP reliability, October 2026: 39,484 handshakes measured 98.7% of 39,484 handshakes with 6,000 registry MCP servers were answered, 8–15 October 2026, and one endpoint in five changed its](/blog/mcp-reliability-october-2026)[2026-10-21 For a week, CrawlCheck told AI agents not to pay us A new tool endpoint appeared on crawlcheck.io's registry listing. Until we confirmed it, agents asking to pay us were stopped. The](/blog/for-a-week-crawlcheck-told-agents-not-to-pay-us)

The main product

Found this on your own site? **We fix it for $100.**

Scan free to see where you stand. The fix is one site, every finding implemented and re-measured, with a sealed before and after.

[Fix it all — $100](https://buy.stripe.com/4gM00j7OjawhdLEdyR2VG0v)
[What it covers](/pricing#fix) · [scan first, it is free](/)

Free browser extension

Check this on any site you open, **without leaving the page.**

CrawlCheck for Chrome grades every site you visit A–F and shows, from your own browser, what search engines and AI assistants are actually served. Free, no account.

[Add to Chrome — free](https://chromewebstore.google.com/detail/plgjengobhbdmbgckiiaaflgiepdbcpi?utm_source=crawlcheck.io&utm_medium=post)
[What it does](/extension)

Write for the library

Measured something yourself? **Submit an article.**

Send your finding, the data and the method. A person reads every submission and replies by email; accepted articles are published under your name with a link to your study. Free to submit. Articles are accepted on merit; no one can pay to have one published.

[Submit an article](/submit-finding#send)
[How it works](/submit-finding) · a reply within about a week

Spotted a mistake or a bug on this page? [Report an error](/report-error?k=article). Confirmed errors are fixed and logged on the [corrections page](/corrections).

## Comments

Comments are read before they appear. Nothing is published automatically, and no account is needed. An AI agent with a published signing key can post without the queue: it signs the request and the signature is checked against its own domain ([how](/api/comment/signed)). Those appear at once, marked *verified*.

Send for review

Writing about this? [Facts, live figures and marks](/press) — every number on that page is dated and traceable to a scan.

[All findings](/blog) · [The dataset](/data) · [How the dataset works](/policy)

We read your site the way crawlers do, from our own network, and every report says exactly what was asked for and what came back. [Who runs this](/author) · [Press kit](/press) · [Videos](/videos) · [Evidence for disputes](/evidence) · [YouTube](https://www.youtube.com/@crawlcheck) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io)

#### How we measure, and our own machine files

CrawlCheck reads every site as itself. Its crawler-identity tests send named user-agent strings from its own network, never from an operator’s published range, so a site that verifies crawlers can tell them apart; every report says so. Results reflect what an anonymous non-browser client receives. [What we collect and how to opt out](/policy) · [how every report is timestamped](/proof) · [who runs this](/author) · [press kit](/press) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io).

**Second vantage:** the [browser extension](/extension) measures what crawlers are served from your own address and after your JavaScript runs — the half this server cannot see. From 1.0.0 it sends the domain you ask about, on one button, and anonymous usage counts you can switch off; from 1.0.3 a footer switch turns off the hostname lookup for the grade on the icon; from 1.0.4 a share switch, on by default, sends a signed Two-vantages reading (status, size, words and a hash per identity; never page text); from 1.0.16 chips send the hostnames of search results and AI citations while the chips and grade switches are on; from 1.0.17 a readings switch, on by default, sends one signed page reading a day (numbers, the hostname and the page address with the query removed; never in incognito; at most 40 a day) and only while the share and grade switches are also on. Earlier versions send nothing.

**Our own machine layer for the agentic web:** [llms.txt](/llms.txt) · [llms-full.txt](/llms-full.txt) · [agents.md](/agents.md) · [SKILL.md](/SKILL.md) · [entitymap.json](/entitymap.json) · [media kit](/.well-known/media-kit.json) · [MCP server card](/.well-known/mcp/server-card.json) · [API catalog](/.well-known/api-catalog) · [OpenAPI](/openapi.json) · [robots.txt](/robots.txt) · [sitemap.xml](/sitemap.xml) · [security.txt](/.well-known/security.txt) — every one named in robots.txt, which is exactly what we check for on yours.

**Pages:** [/](/) · [Listing check](/listing-check) · [SDK](/sdk) · [Certificates](/certificates) | **Glossary:** [Transactional query](/glossary/transactional-query) · [ARIA](/glossary/aria) · [self-claim ledger](/glossary/self-claim-ledger) · [OpenSearch description](/glossary/opensearch-description) | **Registry:** [baidu.com](/registry/baidu.com) · [dimamedia.ir](/registry/dimamedia.ir) · [ilkadimlarim.com](/registry/ilkadimlarim.com) · [nikkei.com](/registry/nikkei.com)

[Contact](/contact) · [Partnerships](/partnerships) · [Terms of service](/terms) · [Refund policy](/refunds) · [Trust center](/trust) · [Subprocessors](/subprocessors) · [Changelog](/changelog) · [Report an error](/report-error)

Same body as a file: /blog/our-sdks-cut-a-tool-list-at-300-with-no-warning.md · as data: /feed.json · what we tell agents site-wide: /llms.txt, /agents.md. To see any other site this way, from your own browser, after its JavaScript runs: the browser extension.