Olostep MCP Server
NPM · OLOSTEP-MCP · 2 COMPONENTS
Live web search, scraping and crawling API for AI. Get structured, LLM-ready data from any site.
Available components
Last scanned (1 hour ago)
Scores higher than 55% of npm servers
Category Web Scraping
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 34 of 100 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (ISC).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1585 tokens (~158/item across 10 items; 10 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 10 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 29 Oct 26 +44
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 28 Oct 26 −39
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Source repository: fail → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 1.0.18 → 1.0.19 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 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 · Analysed npm/olostep-mcp@1.0.19
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 100 packages
| Packages resolved | 100 |
|---|---|
| Deprecated | 1 |
| Stale | 33 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
answers Answers ~141
Answer a factual question using web search, optionally shaped into a flat JSON object of fields, with sources and citations. Suited to bounded, factual answers such as a company's founding year or a product's current price. Lists of items on a live page, such as the latest blog posts, come back more reliably from scraping that page.
| Name | Type | Req | Description |
|---|---|---|---|
| json | – | – | Optional shape for the answer: a flat JSON object of the fields you want. Example: { "book_title": "", "author": "", "release_date": "" }. Keep it flat. Deeply nested shapes or long lists are unrelia… |
| task | string | yes | Question or task to answer using web data. |
No output schema declared.
No examples provided.
batch_scrape_urls Batch Scrape URLs ~246
Scrape a known list of URLs (up to 10,000) in one async job, for example URLs from a CSV or from search results. Waits up to `wait_for_completion_seconds` (default 45) and returns the scraped content when the batch finishes in that time. Larger batches (usually 5-8 min) return a batch_id instead, and `get_batch_results` returns their content once done.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional country code for location-specific scraping. |
| output_format | string | – | Choose format for all URLs. Default: "markdown". |
| parser | string | – | Optional parser ID for specialized extraction (e.g. @olostep/google-search). |
| urls | array | – | Array of URLs to scrape — plain URL strings, or objects with "url" and optional "custom_id". |
| urls_to_scrape | array | – | Alias for `urls`. |
| wait_before_scraping | integer | – | Wait time in milliseconds before scraping each URL. |
| wait_for_completion_seconds | integer | – | Seconds to wait for the batch to finish and return its content in this call. 0 returns the batch_id right away. |
No output schema declared.
No examples provided.
create_crawl Create Crawl ~260
Crawl a website from a start URL: follows links on the same site and scrapes each page it finds, up to `max_pages`. Suited to getting many pages from one site, such as a docs section or a blog. Waits up to `wait_for_completion_seconds` (default 45) and returns the scraped pages when the crawl finishes in that time. Larger crawls return a crawl_id instead, and `get_crawl_results` returns their pages once done. Crawls and batches are separate resources, so a crawl_id works with `get_crawl_results`, not `get_batch_results`.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional country code for location-specific crawling. |
| max_pages | integer | – | Maximum number of pages to crawl. Set to 1 to scrape only the start URL. |
| output_format | string | – | Format for scraped content. Default: "markdown". |
| parser | string | – | Optional parser ID for specialized content extraction. |
| start_url | string | – | Alias for `url`. |
| url | string | – | Starting URL for the crawl. |
| wait_for_completion_seconds | integer | – | Seconds to wait for the crawl to finish and return its pages in this call. 0 returns the crawl_id right away. |
No output schema declared.
No examples provided.
create_map Create Map ~160
List the URLs on a website without scraping their content. Suited to showing a site's pages, mapping a site, or picking a subset of URLs to scrape. `create_crawl` both discovers and scrapes pages when their content is needed too.
| Name | Type | Req | Description |
|---|---|---|---|
| exclude_url_patterns | array | – | Optional glob patterns to exclude (e.g., "/admin/**"). |
| include_url_patterns | array | – | Optional glob patterns to include (e.g., "/blog/**"). |
| search_query | string | – | Optional search query to filter URLs (e.g., "blog"). |
| top_n | integer | – | Optional limit for number of URLs returned. |
| url | string | – | Website URL to extract links from. |
| website_url | string | – | Alias for `url`. |
No output schema declared.
No examples provided.
get_batch_results Get Batch Results ~126
Retrieve the status and scraped content for a batch job. Pass the batch_id returned by batch_scrape_urls. If the batch is completed, returns the scraped content for each URL. If still in_progress, returns the current status so you can call again later.
| Name | Type | Req | Description |
|---|---|---|---|
| batch_id | string | yes | The batch_id (or id) returned from batch_scrape_urls. |
| formats | array | – | Content formats to retrieve per URL. Default: ["markdown"]. |
| items_limit | integer | – | Max number of items to retrieve content for (1-100). Default: 20. |
No output schema declared.
No examples provided.
get_crawl_results Get Crawl Results ~167
Retrieve the status and scraped pages for a crawl job started with create_crawl. While the crawl is in_progress it returns the current status, so call again after about 10 seconds. Once completed, it returns the discovered pages with their scraped content in the requested formats.
| Name | Type | Req | Description |
|---|---|---|---|
| crawl_id | string | yes | The crawl_id (or id) returned from create_crawl. |
| cursor | integer | – | Pagination cursor for list-pages. Default: 0 (first page). |
| formats | array | – | Content formats to retrieve per page. Default: ["markdown"]. |
| items_limit | integer | – | Max number of pages to retrieve content for (1-100). Default: 20. |
| search_query | string | – | Optional filter to rank/select pages by relevance to a query. |
No output schema declared.
No examples provided.
get_webpage_content Get Webpage Content ~90
Retrieve content of a webpage in markdown
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Residential country to load the request from (e.g., US, CA, GB). Optional. |
| url | string | – | The URL of the webpage to scrape. |
| url_to_scrape | string | – | Alias for `url`. |
| wait_before_scraping | integer | – | Time to wait in milliseconds before starting the scrape. |
No output schema declared.
No examples provided.
get_website_urls Get Website URLs ~64
Find URLs on a website that match a search query, ranked by relevance. Returns links only and does not scrape page content.
| Name | Type | Req | Description |
|---|---|---|---|
| search_query | string | yes | The search query to sort URLs by. |
| url | string | yes | The URL of the website to map. |
No output schema declared.
No examples provided.
scrape_website Scrape Website ~275
Extract content from a single URL. Supports multiple formats and JavaScript rendering.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional country code (e.g., US, GB, CA) for location-specific scraping. |
| llm_extract | object | – | Defines what to pull when output_format is "json". Provide a `schema` (a JSON-schema object of the fields you want, e.g. { "type": "object", "properties": { "title": { "type": "string" } } }) and/or… |
| output_format | string | – | Output format. "markdown" (default), "html", and "text" need no extra config. "json" returns STRUCTURED data and requires either a `parser` OR an `llm_extract` schema describing the fields to pull. D… |
| parser | string | – | Optional parser ID for specialized extraction (e.g., "@olostep/amazon-it-product"). |
| url | string | – | The URL of the website you want to scrape. |
| url_to_scrape | string | – | Alias for `url`. |
| wait_before_scraping | integer | – | Wait time in milliseconds before scraping (0-10000). Useful for dynamic content. |
No output schema declared.
No examples provided.
search_web Search Web ~56
Search the web for a given query and return structured results (non-AI, parser-based).
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional country code for localized results (e.g., US, GB). |
| query | string | yes | Search query |
No output schema declared.
No examples provided.
How do I install the Olostep MCP Server server?
Olostep MCP Server runs locally as an npm package, launched with npx -y olostep-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · olostep-mcp
claude mcp add olostep-olostep-mcp-server -- npx -y olostep-mcp
What is the Olostep MCP Server server?
Olostep MCP Server is listed in the public MCP registry as io.github.olostep/olostep-mcp-server. Live web search, scraping and crawling API for AI. Get structured, LLM-ready data from any site. This page covers its npm package (olostep-mcp).
Is the Olostep MCP Server server safe to use?
Olostep MCP Server scores 77 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 Olostep MCP Server server expose?
Olostep MCP Server exposes 10 tools: create_map, create_crawl, get_crawl_results, batch_scrape_urls, get_batch_results, and 5 more. Their descriptions and schemas cost roughly 1,585 tokens of context every time the server is loaded.
Is the Olostep MCP Server server still maintained?
Olostep MCP Server 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.
What licence is the Olostep MCP Server server under?
Olostep MCP Server declares the ISC licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.