Not Human Search
Server Details
Search the agentic web. 4,100+ sites, 11 tools incl. check_url + verify_mcp for probe-before-use.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.2/5 across 11 of 11 tools scored.
Each tool has a distinct purpose: checking URLs, searching sites, getting details, stats, top sites, categories, recent additions, monitoring, submitting, and verifying MCP servers. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (e.g., check_url, find_mcp_servers, get_site_details). No mixing of conventions.
11 tools is appropriate for the server's purpose—covering discovery, verification, submission, and monitoring without being too many or too few.
The tool set comprehensively covers the domain: search, list, filter, get details, submit, check, verify, and monitor. No obvious gaps for the stated purpose.
Available Tools
11 toolscheck_urlCheck Any URL's Agentic ReadinessInspect
On-demand agentic-readiness check for any URL. Runs the NHS 7-signal crawler live (llms.txt, ai-plugin.json, OpenAPI, structured API, MCP server, robots.txt AI rules, Schema.org) and returns a score 0-100 with per-signal breakdown. Use before calling an unfamiliar API to confirm it's agent-usable. Re-runnable without the submissions-table side-effect of submit_site — ideal for verify-before-use workflows.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Full URL or bare domain (e.g. 'stripe.com' or 'https://stripe.com'). Homepage works best — NHS probes the /.well-known/ paths, /robots.txt, /llms.txt relative to the site root. |
find_mcp_serversFind MCP ServersInspect
List sites in the index that expose a live MCP server, ranked by agentic readiness. Use this when your agent needs to discover callable MCP endpoints for a domain ('payments', 'jobs', 'search') or overall. Pairs naturally with verify_mcp for a probe-before-use workflow.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (default 10, max 20) | |
| query | No | Optional keyword to narrow results (e.g. 'payments', 'jobs', 'weather') | |
| category | No | Filter by public category (ai-tools, developer, data, finance, ecommerce, jobs, security, health, education, communication, productivity, news). Audit-only buckets may appear in /api/v1/categories as other or spam, but are not promoted as discovery inventory. Omit for all categories. |
get_site_detailsGet Site Agentic Readiness ReportInspect
Get the full agentic readiness report for a specific domain: score, category, all 7 signal checks (llms.txt, ai-plugin.json, OpenAPI, structured API, MCP server, robots.txt AI rules, Schema.org), plus any cached llms.txt content and OpenAPI summary.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain to look up (e.g. 'stripe.com'). Do not include scheme or path. |
get_statsGet Index StatsInspect
Current Not Human Search index stats: total sites, average agentic score, top category, sites added in the last 7 days, count of sites exposing an MCP server, and count scoring a perfect 100/100.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_top_sitesGet Top Scored SitesInspect
Get the highest-scored agent-ready sites in the index, optionally filtered by category. Returns sites ranked by agentic readiness score (100 = perfect agent support). Use this to discover the most agent-ready services overall or in a specific domain like 'finance' or 'developer'.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (default 10, max 50) | |
| category | No | Filter by public category (ai-tools, developer, data, finance, ecommerce, jobs, security, health, education, communication, productivity, news). Audit-only buckets may appear in /api/v1/categories as other or spam, but are not promoted as discovery inventory. Omit for all categories. |
list_categoriesList Index CategoriesInspect
List all categories in the Not Human Search index with site counts and average agentic scores. Use this to understand what kinds of agent-ready services exist before searching — counts are live, so the distribution shifts as the index grows.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
recent_additionsRecently Indexed Agent-First SitesInspect
List agent-ready sites newly added to the Not Human Search index, sorted newest first. Use this to discover what's just landed on the agentic web — new MCP servers, fresh llms.txt adopters, new OpenAPI publishers. Good for weekly agent digests or tracking ecosystem momentum.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Look back window in days (default 7, max 90) | |
| limit | No | Max results (default 10, max 50) |
register_monitorMonitor a Site's Agentic ReadinessInspect
Register an email to get alerted when the indicated domain's agentic readiness score drops. Useful for agents tracking a dependency's agent-readiness health — e.g. an agent that relies on stripe.com's MCP surface wants to know the moment it regresses. Returns an unsubscribe URL. Multiple monitors per email allowed, one per domain.
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | Email address to receive alert | ||
| domain | Yes | Domain to monitor (no scheme, e.g. 'stripe.com') |
search_agentsSearch the Agentic WebInspect
Search for websites, APIs, and services that AI agents can actually use. Results are ranked by agentic readiness score (0-100) based on llms.txt, OpenAPI specs, ai-plugin.json, structured APIs, and MCP server availability. Use this to discover payment APIs, job boards, data sources, or any web service your agent needs to call.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (default 10, max 20) | |
| query | No | Keyword query (e.g. 'payment API', 'weather data', 'job board') | |
| has_api | No | Only return sites with a documented structured API | |
| has_mcp | No | Only return sites that expose an MCP server | |
| category | No | Filter by public category (ai-tools, developer, data, finance, ecommerce, jobs, security, health, education, communication, productivity, news). Audit-only buckets may appear in /api/v1/categories as other or spam, but are not promoted as discovery inventory. | |
| min_score | No | Minimum agentic readiness score 0-100 (higher = more agent-ready) | |
| has_openapi | No | Only return sites with a published OpenAPI / Swagger spec | |
| has_llms_txt | No | Only return sites that publish an llms.txt file (LLM-first site summary) |
submit_siteSubmit a Site for IndexingInspect
Submit a URL for NHS to crawl and score. Use when you discover an agent-first tool, API, or service that isn't in the index yet. NHS will fetch the site, check its 7 agentic signals (llms.txt, ai-plugin.json, OpenAPI, structured API, MCP server, robots.txt AI rules, Schema.org), compute a score, and add it to the index. The site becomes searchable within a few seconds if the crawl succeeds.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Full URL to submit (include scheme, e.g. 'https://example.com'). Homepage is best — NHS will check /.well-known/ paths, /robots.txt, /llms.txt, etc. relative to the site root. |
verify_mcpVerify MCP EndpointInspect
Actively probe any URL to check if it is a live, spec-compliant MCP server. Sends a JSON-RPC tools/list request and verifies a valid response. Use this before depending on a third-party MCP endpoint — manifests and documentation can claim MCP support without actually serving it. Returns {verified: true/false, endpoint, note}.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Full URL of the MCP endpoint to probe (include scheme, e.g. 'https://example.com/mcp'). |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!