
Not Human Search
Find MCP servers, agent tools, and agentic-web resources across thousands of indexed sites before you wire them into Claude Code or Cursor.
Overview
Not Human Search is an MCP server for the Idea phase that searches 4,100+ agentic-web sites and offers probe tools so agents can find and vet MCP resources before use.
What is this MCP server?
- Indexes 4,100+ agentic-web sites for broad discovery coverage
- Exposes 11 MCP tools for search, lookup, and validation workflows
- check_url probes a URL before your agent depends on it
- verify_mcp validates MCP endpoints before you add them to config
- Remote streamable-http endpoint at nothumansearch.ai/mcp (v1.7.1)
- 4,100+ indexed agentic-web sites
- 11 MCP tools including check_url and verify_mcp
- Server version 1.7.1
What problem does it solve?
You waste hours chasing broken MCP links and scattered “best of” lists because nothing in your agent can search the agentic web reliably.
Who is it for?
Solo builders evaluating many MCP servers or agent tools during stack research inside Claude Code, Cursor, or Codex.
Skip if: Teams that already maintain a frozen allowlist of three trusted MCP servers and never explore new integrations.
What do I get? / Deliverables
Your agent can search a broad index, then check_url and verify_mcp candidate servers before you register them in your stack.
- Ranked discovery results from the agentic-web index
- URL probe results via check_url before integration
- MCP endpoint validation output from verify_mcp
Recommended MCP Servers
Journey fit
Discovery belongs in Idea because solo builders need to scout the agentic ecosystem before they commit architecture or dependencies. Discover is the canonical shelf for search-and-catalog tools that answer “what exists?” rather than “does it work in prod?”
How it compares
Agentic-web search MCP, not a single-purpose API wrapper or a planning methodology skill.
Common Questions / FAQ
Who is Not Human Search for?
Indie and solo builders who use Claude Code, Cursor, or similar agents and need to discover and vet MCP servers from inside the chat instead of manual browsing.
When should I use Not Human Search?
Use it in the Idea and early Build phases when you are scouting integrations, comparing remote MCP URLs, or validating that a discovered server responds before you add it to config.
How do I add Not Human Search to my agent?
Register the remote MCP URL https://nothumansearch.ai/mcp as streamable-http in your client’s MCP settings, then invoke search and validation tools from the agent session.