# 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.

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.stork.ai`: 72/100 (this document), [markdown](https://verifymcp.io/servers/ai-stork-core/core.md), [page](https://verifymcp.io/servers/ai-stork-core/core)

## Channel facts

- Endpoint: `https://mcp.stork.ai/core`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http ai-stork-core 'https://mcp.stork.ai/core'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-stork-core": {
      "url": "https://mcp.stork.ai/core"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-stork-core": {
      "type": "http",
      "url": "https://mcp.stork.ai/core"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-stork-core]
url = "https://mcp.stork.ai/core"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-stork-core": {
      "type": "remote",
      "url": "https://mcp.stork.ai/core",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-stork-core --url 'https://mcp.stork.ai/core' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-stork-core:
    url: "https://mcp.stork.ai/core"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-stork-core": {
      "Transport": "http",
      "Url": "https://mcp.stork.ai/core"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-stork-core -t streamable-http -u 'https://mcp.stork.ai/core'
```

### Other

```json
{
  "mcpServers": {
    "ai-stork-core": {
      "type": "http",
      "url": "https://mcp.stork.ai/core"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 72, +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.

### 2026-11-19 (score 71, +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.

### 2026-11-18 (score 70, 0)

- [security] 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
- [functional improvement] Schema quality: 138 → 114
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] 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

### 2026-11-17 (score 70)

First indexed and scored.

## MCP tools (6)

### `stork_search` (~111 tokens)

Search the web

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.

Input parameters:

- `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, required): What to search for.

### `stork_scrape` (~121 tokens)

Read a web page

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.

Input parameters:

- `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, required): Full address of the page, starting with https://.

### `stork_docs` (~131 tokens)

Look up library documentation

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.

Input parameters:

- `library` (string, required): 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, required): What you need to know about it.

### `stork_repo` (~137 tokens)

Ask about a GitHub repository

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.

Input parameters:

- `max_result_tokens` (number): Cap on the size of the reply. Default 3000, at most 6000.
- `question` (string, required): What you want to know about the code.
- `repo` (string, required): owner/name, for example vercel/next.js, or the repository's GitHub address.

### `stork_install` (~136 tokens)

Set up an MCP server

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.

Input parameters:

- `client` (string): The user's MCP client: cursor, claude-desktop, claude-code, vscode, zed. Any other name gets the common mcpServers JSON.
- `name` (string, required): The product or job, for example Notion, Supabase, browser automation.

### `stork_find_server` (~140 tokens)

Find an MCP server

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.

Input parameters:

- `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, required)
- `transport` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-stork-core/core#diagnostics

## Score history

- 2026-11-21: 72
- 2026-11-20: 71
- 2026-11-19: 71
- 2026-11-18: 70
- 2026-11-17: 70

## Common questions

### 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.

## Links

- Remote endpoint: https://mcp.stork.ai/core
- Repository: https://github.com/storkai/stork-mcp
- Website: https://www.stork.ai/mcp
- Changelog RSS feed: https://verifymcp.io/servers/ai-stork-core/core.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-stork-core/core/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-stork-core/core.json
- HTML version of this page: https://verifymcp.io/servers/ai-stork-core/core
