Stork: search, scrape and docs
REMOTE · MCP.STORK.AI
Web search, page reading and library docs for agents. No key. Routed to the best measured server.
Available components
Last scanned (16 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
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. 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 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 Usability80
- 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
- Context-footprint check failed: tool/resource definitions use about 912 tokens (~114/item across 8 items; 6 tools + 2 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% 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 6 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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 →
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 +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.
- 19 Nov 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.
- 18 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “stork_docs” rewrote its description, which is the text the model reads security
- Tool “stork_find_server” rewrote its description, which is the text the model reads security
- Tool “stork_install” rewrote its description, which is the text the model reads security
- Tool “stork_repo” rewrote its description, which is the text the model reads security
- Tool “stork_scrape” rewrote its description, which is the text the model reads security
- Tool “stork_search” rewrote its description, which is the text the model reads security
- Schema quality: 138 → 114 ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Tool “stork_docs” changed its title: Look up library documentation cosmetic
- Tool “stork_find_server” changed its title: Find an MCP server cosmetic
- Tool “stork_install” changed its title: Set up an MCP server cosmetic
- Tool “stork_repo” changed its title: Ask about a GitHub repository cosmetic
- Tool “stork_scrape” changed its title: Read a web page cosmetic
- Tool “stork_search” changed its title: Search the web cosmetic
- 17 Nov 26 70
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://mcp.stork.ai/core
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.stork.ai | CN=WE1,O=Google Trust Services,C=US | 26 Sept 2026 | 25 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 644d184c682cb55a0edee5bbe780ee54 |
| SANs: mcp.stork.ai | ||||||
| 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 mcp.stork.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| stork.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.stork.ai/core | Verified | 200 | |
| http (plaintext) | http://mcp.stork.ai/core | HTTPS enforced | 301 | https://mcp.stork.ai/core |
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 →
stork_docs Look up library documentation ~131
Look up current documentation for a code library or framework. Returns the passages and code examples that fit a question. The lookup is run by a documentation provider (Context7, or the vendor's own documentation server for Microsoft, AWS and Cloudflare), which is named in the reply's `via` field.
| Name | Type | Req | Description |
|---|---|---|---|
| library | string | yes | Library or framework name, for example next.js, convex, stripe. |
| max_result_tokens | number | – | Cap on the size of the reply. Default 3000, at most 6000. |
| question | string | yes | What you need to know about it. |
No output schema declared.
No examples provided.
stork_find_server Find an MCP server ~140
Find MCP servers for a task or product (for example: Stripe payments, browser automation). Returns matching servers from Stork's directory, each with how to connect, whether its endpoint answered Stork's last check, how many tokens its tool definitions take, and what Stork's own test calls saw.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | number | – | – |
| live_only | boolean | – | Only servers whose endpoint answered the last check without an account. |
| max_tool_tokens | number | – | Only servers whose tool definitions are estimated at or under this many tokens. |
| query | string | yes | – |
| transport | string | – | – |
No output schema declared.
No examples provided.
stork_install Set up an MCP server ~136
Get the configuration for adding a named MCP server (for example Notion, Supabase, Sentry, Postgres or a browser) to a given client. Returns the config, what the user must supply (a sign-in or keys), and who publishes the server. Where a vendor publishes its own server, that one is returned.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | The user's MCP client: cursor, claude-desktop, claude-code, vscode, zed. Any other name gets the common mcpServers JSON. |
| name | string | yes | The product or job, for example Notion, Supabase, browser automation. |
No output schema declared.
No examples provided.
stork_repo Ask about a GitHub repository ~137
Answer a question about the code in a public GitHub repository: how something is implemented, where it lives, how it is used. The answer comes from DeepWiki, which has indexed the repository, and is named in the reply's `via` field. Can take 10 to 20 seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| max_result_tokens | number | – | Cap on the size of the reply. Default 3000, at most 6000. |
| question | string | yes | What you want to know about the code. |
| repo | string | yes | owner/name, for example vercel/next.js, or the repository's GitHub address. |
No output schema declared.
No examples provided.
stork_scrape Read a web page ~121
Read one public web page. Returns the page's main content as markdown for a given address. The page is fetched by a page-reading provider (Firecrawl today), which is named in the reply's `via` field. The page is third-party content.
| Name | Type | Req | Description |
|---|---|---|---|
| max_result_tokens | number | – | Cap on the size of the reply. Default 3000, at most 6000. |
| objective | string | – | Optional: what you want from the page. |
| url | string | yes | Full address of the page, starting with https://. |
No output schema declared.
No examples provided.
stork_search Search the web ~111
Search the web. Returns ranked results with titles, addresses and text snippets for a query. The search is run by a web search provider (Exa today), which is named in the reply's `via` field. Results are third-party content.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | How many results. Default 5. |
| max_result_tokens | number | – | Cap on the size of the reply. Default 3000, at most 6000. |
| query | string | yes | What to search for. |
No output schema declared.
No examples provided.
How do I install the Stork: search, scrape and docs MCP server?
Stork: search, scrape and docs is a hosted endpoint at https://mcp.stork.ai/core, 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 · mcp.stork.ai
claude mcp add --transport http ai-stork-core 'https://mcp.stork.ai/core'
What is the Stork: search, scrape and docs MCP server?
Stork: search, scrape and docs is an MCP server listed in the public MCP registry as ai.stork/core. Web search, page reading and library docs for agents. No key. Routed to the best measured server. This page covers its hosted endpoint (https://mcp.stork.ai/core).
Is the Stork: search, scrape and docs MCP server safe to use?
Stork: search, scrape and docs 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 Stork: search, scrape and docs MCP server expose?
Stork: search, scrape and docs exposes 6 tools: stork_search, stork_scrape, stork_docs, stork_repo, stork_install, stork_find_server. Their descriptions and schemas cost roughly 776 tokens of context every time the server is loaded.
Does the Stork: search, scrape and docs MCP server require authentication?
No. We connected to Stork: search, scrape and docs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Stork: search, scrape and docs MCP server still maintained?
Stork: search, scrape and docs 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 Stork: search, scrape and docs MCP server?
VerifyMCP ran 13 checks on Stork: search, scrape and docs, 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.