Skip to main content
Glama
keenableai

Keenable MCP

by keenableai
OverviewSchemaRelated ServersScoreDiscussions
JavaScript

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

Tool

Description

search_web_pages

Live web search. Args: query (required), plus optional mode, site, published_after / published_before, acquired_after / acquired_before.

fetch_page_content

Fetch a URL and return clean markdown. Args: url (required), optional max_chars (default 50000).

Related MCP server: exa-search

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:

{
  "mcpServers": {
    "keenable": {
      "type": "streamable-http",
      "url": "https://api.keenable.ai/mcp"
    }
  }
}

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:

{
  "mcpServers": {
    "keenable": {
      "command": "npx",
      "args": ["-y", "@keenable/mcp"]
    }
  }
}

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:

{
  "mcpServers": {
    "keenable": {
      "type": "streamable-http",
      "url": "https://api.keenable.ai/mcp",
      "headers": { "X-API-Key": "YOUR_KEY" }
    }
  }
}

Stdio:

{
  "mcpServers": {
    "keenable": {
      "command": "npx",
      "args": ["-y", "@keenable/mcp"],
      "env": { "KEENABLE_API_KEY": "YOUR_KEY" }
    }
  }
}

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 as X-API-Key.

  • KEENABLE_MCP_URL — override the endpoint (defaults to https://api.keenable.ai/mcp).

Links

License

MIT

Available Tools

2 tools
fetch_page_contentA
Read-onlyIdempotent
Inspect

Fetch and extract content from a web page. Returns the page content in markdown format.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to fetch. Example: "https://example.com".
liveNoFetch live content. Defaults to false.
max_charsNoMaximum number of characters of content to return. Longer content is truncated. Defaults to 50000 when omitted.

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds that the output is markdown format, which is useful but does not disclose other behaviors like handling of JavaScript, rate limits, or error states.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with two sentences, front-loading the action and output. Every word adds value with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with three parameters and no output schema, the description covers the core function and return format. It lacks detail on error handling or content extraction specifics, but given the simplicity, it is largely complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% coverage, so the description does not need to add parameter details. It provides no additional meaning beyond the schema, maintaining the baseline score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's action: 'Fetch and extract content from a web page.' It includes the output format ('Returns the page content in markdown format.'), which differentiates it from the sibling tool 'search_web_pages' that presumably searches for pages rather than fetching a specific URL.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies that the tool is used when a specific URL is known, in contrast to 'search_web_pages,' but it does not explicitly state when to use or not use this tool, nor does it provide alternative suggestions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_web_pagesA
Read-onlyIdempotent
Inspect

Live web search over the Keenable web index. Describe the ideal page, not keywords. Use date/site filters to narrow results.

ParametersJSON Schema
NameRequiredDescriptionDefault
modeNoSearch mode: 'pro' (default) for enhanced results.
siteNoRestrict results to a specific site (e.g. "techcrunch.com").
queryYesNatural language search query. A semantically rich description of the ideal page, not just keywords.
acquired_afterNoFilter to pages acquired/indexed after this date (YYYY-MM-DD).
acquired_beforeNoFilter to pages acquired/indexed before this date (YYYY-MM-DD).
published_afterNoFilter to pages published after this date (YYYY-MM-DD).
published_beforeNoFilter to pages published before this date (YYYY-MM-DD).

TDQS

A4.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description adds the context 'live' to indicate real-time results. It does not detail response format or pagination, but the annotations cover the safety profile adequately.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description consists of two concise sentences with no wasted words. The key action 'Live web search' is front-loaded, making the purpose immediately clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While the description effectively conveys the core search behavior, it lacks details about the response (e.g., result count, sorting) and potential limitations. Given the parameter richness (7 params) and no output schema, additional context would improve completeness for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the baseline is 3. The description adds value by explaining the intent of the query parameter ('describe the ideal page, not keywords') beyond the schema's 'natural language search query', and it reinforces the use of date/site filters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Live web search over the Keenable web index', specifying the verb 'search' and the resource 'web pages'. It distinguishes from the sibling tool 'fetch_page_content' by focusing on discovery rather than retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description advises 'Describe the ideal page, not keywords' and prompts using date/site filters, offering concrete query formulation guidance. However, it does not explicitly state when to use this tool versus the sibling 'fetch_page_content', leaving the differentiation implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4/5.0
Disambiguation5/5

The two tools have clearly distinct purposes: one fetches content from a specific page, the other searches the web. There is no overlap.

Naming Consistency5/5

Both tools use a consistent verb_noun pattern in snake_case: 'fetch_page_content' and 'search_web_pages'.

Tool Count3/5

Only 2 tools, which is below the typical 3-15 range, but the domain is narrow (web search and page fetching), so it may be acceptable.

Completeness4/5

The set covers the basic workflow of searching and fetching content. Minor gaps exist (e.g., no tool to list search results separately), but the core functionality is complete.

Maintenance

ActivityMaintained
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/keenableai/keenable-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server