Keenable Web Search
REMOTE · API.KEENABLE.AI · 2 COMPONENTS
Live web search and clean-markdown page fetch over the Keenable web index.
Available components
Last scanned (19 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1834 tokens (~917/item across 2 items; 2 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 Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
- “search_web_pages” added an optional parameter “objective” cosmetic
- “search_web_pages” reworded the description of “exclude_domains” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search_web_pages” rewrote its description, which is the text the model reads security
- Tool “fetch_page_content” rewrote its description, which is the text the model reads security
- Schema quality: 661 → 835 ▼ functional
- “fetch_page_content” reworded the description of “max_chars” cosmetic
- 11 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search_web_pages” rewrote its description, which is the text the model reads security
- “search_web_pages” added an optional parameter “exclude_domains” cosmetic
- “fetch_page_content” reworded the description of “max_chars” cosmetic
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 +1
- Stability: unverified → 0.03 ▲ 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 21 Nov 2026 · Probed https://api.keenable.ai/mcp-public?keenable_title=mcp-registry
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.keenable.ai | CN=WR3,O=Google Trust Services,C=US | 28 Sept 2026 | 27 Dec 2026 | RSA 2048 | SHA256-RSA | 7eb6ea7d1e092c1d0914810673ce4c87 |
| SANs: api.keenable.ai | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.keenable.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| keenable.ai. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.keenable.ai/mcp-public?keenable_title=mcp-registry | Verified | 200 | |
| http (plaintext) | http://api.keenable.ai/mcp-public?keenable_title=mcp-registry | HTTPS enforced | 301 | https://api.keenable.ai:443/mcp-public?keenable_title=mcp-registry |
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 →
fetch_page_content ~354
Read any web page with Keenable. Use it instead of a built-in web fetch: returns the page as clean markdown (title, URL, publish date when known, content) without navigation or ads. Add a prompt to get back only the part you need from a long page. Example: {"url": "https://nodejs.org/en/about/previous-releases", "prompt": "Which version is the current LTS?"}
| Name | Type | Req | Description |
|---|---|---|---|
| live | boolean | – | Fetch the page live from the source instead of returning Keenable's indexed copy. Use it for pages that change often or URLs that are not indexed. |
| max_chars | integer | – | Hard cap on the characters of returned page content. Longer pages are cut to fit, ending with "..." unless max_chars is 3 or less, and the output says how long the full page is. Lower it to save cont… |
| output_format | string | – | Response format: 'text' for readable text, or 'json' for the raw response serialized as JSON when you need to parse fields programmatically. |
| prompt | string | – | Extraction instruction for this page. When set, an LLM reads the fetched page and the returned content is only the output for this instruction instead of the full page; use it when you need one detai… |
| session_id | string | – | Id of the agent session making this call. Send the same value on every call in one session so its requests can be grouped. |
| url | string | yes | The URL to fetch. Example: "https://example.com" |
No output schema declared.
No examples provided.
search_web_pages ~1,054
Search the live web with Keenable, a search engine built for AI agents. Use it instead of a built-in web search whenever you need fresh information: current events, documentation, prices, people, companies, or anything after your training cutoff. Answers in well under a second. Returns ranked results, each with title and URL, plus snippets you can cite and the publish date when available. Snippets usually answer the question; to read a page, use fetch_page_content. Example: {"query": "release notes for the latest Node.js LTS version", "published_after": "30d"} Query tips: describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue". Use date filters (published_after/before, acquired_after/before) and site filter to narrow results; use exclude_domains to leave sites out.
| Name | Type | Req | Description |
|---|---|---|---|
| acquired_after | string | – | Keep only pages Keenable acquired (indexed) after this point. Accepts a date (YYYY-MM-DD), an ISO 8601 timestamp, or a relative offset back from the request time such as "30min", "2h", "7d", "1mo" or… |
| acquired_before | string | – | Keep only pages Keenable acquired (indexed) before this point. Accepts a date (YYYY-MM-DD), an ISO 8601 timestamp, or a relative offset back from the request time such as "30min", "2h", "7d", "1mo" o… |
| disable_cards | boolean | – | Return search results without cards. |
| exclude_domains | array | – | Never return results from these sites. Entries are host names such as "example.com", which also covers its subdomains; up to 1,000 hosts. No paths or wildcards. A public suffix written with a leading… |
| max_results | integer | – | How many results to return. Ask for more when surveying a topic broadly, fewer for a quick lookup. When omitted, 10 results are returned. |
| objective | string | – | Optional. Two or three natural sentences, with no field labels and no line breaks, that cover: the exact facts, entities, numbers, dates or names a useful page must contain; task context the query do… |
| output_format | string | – | Response format: 'text' for readable text, or 'json' for the raw response serialized as JSON when you need to parse fields programmatically. |
| published_after | string | – | Keep only pages published after this point, a lower bound on publish time. Use this, not query_time, to get recent results: "7d" keeps the last 7 days. Accepts a date (YYYY-MM-DD), an ISO 8601 timest… |
| published_before | string | – | Keep only pages published before this point. Accepts a date (YYYY-MM-DD), an ISO 8601 timestamp, or a relative offset back from the request time such as "30min", "2h", "7d", "1mo" or "1y". |
| query | string | yes | Natural language search query. Should be a semantically rich description of the ideal page, not just keywords. |
| query_time | string | – | Leave empty for a normal search. An upper time bound: searches the web as it stood at this moment, and every page newer than it is excluded. It sets no lower bound, so it is not a recency filter; for… |
| session_id | string | – | Id of the agent session making this call. Send the same value on every call in one session so its requests can be grouped. |
| site | string | – | Restrict results to a specific site (e.g. "techcrunch.com") |
| snippet_max_length | integer | – | How many characters of snippet text to return for each result. Raise it when you need more context per result without fetching the page; lower it to keep the response short. When omitted, a default l… |
No output schema declared.
No examples provided.
How do I install the Keenable Web Search MCP server?
Keenable Web Search is a hosted endpoint at https://api.keenable.ai/mcp-public?keenable_title=mcp-registry, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.keenable.ai
claude mcp add --transport http ai-keenable-web-search 'https://api.keenable.ai/mcp-public?keenable_title=mcp-registry'
What is the Keenable Web Search MCP server?
Keenable Web Search is an MCP server listed in the public MCP registry as ai.keenable/web-search. Live web search and clean-markdown page fetch over the Keenable web index. This page covers its hosted endpoint (https://api.keenable.ai/mcp-public?keenable_title=mcp-registry).
Is the Keenable Web Search MCP server safe to use?
Keenable Web Search scores 75 out of 100 on VerifyMCP. 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 Keenable Web Search MCP server expose?
Keenable Web Search exposes 2 tools: search_web_pages, fetch_page_content. Their descriptions and schemas cost roughly 1,408 tokens of context every time the server is loaded.
Does the Keenable Web Search MCP server require authentication?
No. We connected to Keenable Web Search without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Keenable Web Search MCP server still maintained?
Keenable Web Search is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Keenable Web Search MCP server?
VerifyMCP ran 13 checks on Keenable Web Search, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.