io.nstdata/crawl
Nstdata Crawl
Is the Nstdata Crawl MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-14.
Scrape webpages, run crawls, and read Markdown and other results with Nstdata Crawl.
needs auth probed 2026-11-14 · HTTP 401 · Bearer
The server needs auth, so these tool definitions were read from the publisher's open-source package npm:@nstdata-ai/mcp-server, started in a container with placeholder values and the network off, on 2026-11-14. Tool definitions do not depend on the token, so this is what an authorized user loads, unless the server hides tools by plan or role.
Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token","error_description":"Missing Authorization header"}- Endpoint
- https://mcp.nstdata.io/crawl (streamable-http)
- Host
- mcp.nstdata.io
- Of a 1M window
- 0.6 % of a 1M context window
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcp.nstdata.io/crawl registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server mcp.nstdata.io, PKCE S256, grants authorization_code, refresh_token.
Scopes crawl:use.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/nstdata-ai/nstdata-mcp-server
- Registry
- active, updated 2026-11-13 · registry entry
Compare this server with others.
More servers
Servers that mention crawl.
- Arclan MCP Registry ai.arclan/registry · alive
- Web Search API for all your agents and LLMs ai.blopus/search · needs auth
- SEOcrawl AI ai.seocrawl/mcp · needs auth
- Crawlie app.crawlie/crawlie · needs auth
- Site SEO & AI Crawler Audit app.openkrill/site-check · alive
- ai.smithery/luminati-io-brightdata-mcp · not found
- AI Visibility Audit — Can AI crawlers read and cite your site? app.rowb.ai-visibility/audit · alive
- Spider Cloud cloud.spider/mcp · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.