Neo X402 Mcp
Give your agent eight remote web tools—search, scrape, screenshots, SEO, docs, crypto, and code helpers—without wiring each API yourself.
Overview
Neo x402 MCP is an MCP server for the Build phase that exposes eight remote web intelligence tools including search, scrape, screenshot, and SEO via streamable HTTP.
What is this MCP server?
- 8-tool AI web intelligence suite: search, scrape, screenshot, SEO, docs, crypto, code
- Remote streamable-http MCP at https://neo.docly.work/mcp
- Registry version 1.2.0; no local npm package required for remote use
- Consolidates competitor and page intelligence for agent-driven validation and build tasks
- 8 tools in the advertised suite
- Remote URL: https://neo.docly.work/mcp (streamable-http)
What problem does it solve?
Agents lack one registered endpoint for search, scraping, screenshots, and SEO checks, forcing builders to integrate many APIs by hand.
Who is it for?
Indie builders who want a single remote MCP for page intelligence, SEO snapshots, and doc lookups while shipping web products.
Skip if: Teams blocked from hosted remotes or needing deep custom crawlers with full data residency on-prem only.
What do I get? / Deliverables
After you add the remote MCP URL, your assistant can call eight unified web tools during research, prototyping, and integration work.
- Access to 8 documented web intelligence MCP tools
- Agent-driven search, scrape, screenshot, and SEO workflows without local server install
Recommended MCP Servers
Journey fit
The suite supports research and implementation tasks (scraping, SEO, docs) while you build integrations; it is not primarily a grow-phase analytics dashboard. Remote HTTP MCP bundles external web intelligence as agent-callable tools—classic integrations layer for builders validating pages and gathering context.
How it compares
Hosted eight-tool web MCP remote, not a self-hosted single-purpose scraper skill.
Common Questions / FAQ
Who is Neo x402 MCP for?
Solo builders and agent users who need search, scrape, screenshot, SEO, docs, crypto, and code helpers through one streamable-http MCP endpoint.
When should I use Neo x402 MCP?
Use it during Validate and Build when you want agents to gather web evidence, audit pages, or support integrations without maintaining eight separate API clients.
How do I add Neo x402 MCP to my agent?
Register the remote MCP server URL https://neo.docly.work/mcp as streamable-http in Claude Code, Cursor, or another client that supports hosted MCP remotes.