Keenable Web Search
ai.keenablePublished by keenable.aiOfficial publisherv0.2.1Updated Nov 7, 2026
Live web search and clean-markdown page fetch over the Keenable web index.
Overview
Keenable MCP gives an assistant live web search and clean-markdown page fetching over the Keenable web index, hosted or via an npm bridge.
- What you can do
- Search the live web with query, site, date and point-in-time filters, result count and snippet length controls
- Fetch a URL and get the page back as clean markdown, optionally limited to a prompt-driven extract
- Run several narrow searches in parallel for broad research questions
- Optionally use a session ID and output format settings across calls
- When to use it
- Useful when an assistant needs current web results, documentation, news, prices or facts after its training cutoff, and when snippets are not enough and the exact page wording is needed.
- Requirements
- A remote endpoint at api.keenable.ai over Streamable HTTP, or Node.js with npx for the @keenable/mcp stdio bridge. No account is required: it is keyless by default at 1,000 requests per hour. An optional key can be supplied as the KEENABLE_API_KEY environment variable or the X-API-Key header to lift the cap.
Installation
In SourceWeft
- Open Keenable Web Search in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/ai.keenable%2Fweb-search/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"keenable-web-search": {
"type": "http",
"url": "https://api.keenable.ai/mcp-public?keenable_title=mcp-registry"
}
}
}README
Keenable MCP
MCP server for live web search and clean-markdown page fetch over the Keenable web index.
- Hosted endpoint:
https://api.keenable.ai/mcp(Streamable HTTP) - Tools:
search_web_pages,fetch_page_content - Keyless by default (1,000 requests/hour). An optional API key lifts the cap.
The server is hosted, so most clients just point at the URL. For clients (or
config paths) that only accept a stdio command there is a thin npm wrapper
(@keenable/mcp) that bridges to the same endpoint.
Tools
Use it
Remote (recommended)
Clients with remote MCP support — Cursor, Cline, VS Code, and Claude Desktop's Custom Connectors UI — connect to the URL directly:
Stdio (e.g. Claude Desktop's claude_desktop_config.json)
For clients or config paths that only accept a stdio command, run the wrapper
with npx:
That is all you need for keyless use.
API key (optional)
Keenable is keyless by default. To lift the hourly rate limit, pass a key.
Remote:
Stdio:
How the wrapper works
@keenable/mcp is a small stdio bridge: it connects to the hosted server over
Streamable HTTP and forwards every tool the server exposes. There is no
search logic in this package; the index and tools live behind
https://api.keenable.ai/mcp. Environment variables:
KEENABLE_API_KEY— optional API key, sent asX-API-Key.KEENABLE_MCP_URL— override the endpoint (defaults tohttps://api.keenable.ai/mcp?keenable_title=npm).
Development
npm test runs the unit tests and a stdio smoke test of the discovery build
(src/discovery.js): initialize must advertise the server metadata and
tools/list must return both tools. CI runs it on Node 18, 20 and 22 and on
the oldest MCP SDK the package accepts.
Releasing
The npm version lives only in package.json; the bridge reads it at runtime.
server.json (the MCP Registry manifest) must repeat it as a literal in
packages[].version, so bump both. npm run check:version compares them and
runs automatically before npm publish. The top-level server.json version
is the registry entry's own version and is bumped whenever server.json
changes.
Links
- Docs: https://docs.keenable.ai/mcp-server
- Site: https://keenable.ai
- Registry:
ai.keenable/web-search(Official MCP Registry)
License
MIT
Source: README.md at commit 7029876
Tools
0Version history
2- v0.2.1LatestNov 7, 2026
- v0.1.2Sep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts