Skip to main content
Glama
enesjakozh
superagents-lab

Search1API MCP Server

by superagents-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search1API MCP Server

Glama

中文文档

The official MCP server for Search1API — web search, news, page retrieval, sitemap discovery, and trending topics in one API.

Authentication

  • OAuth-aware clients can connect to the Remote MCP URL directly, then sign in and approve access in the browser.

  • Existing integrations can continue to use an API key from the Search1API dashboard.

  • Every MCP request — including tool discovery (initialize, tools/list) — requires a credential. Unauthenticated requests draw the OAuth challenge, which is how clients trigger sign-in; pre-connect inspection is served by the static server card instead.

Related MCP server: WebSearch-MCP

Quick Start (Remote MCP)

No installation required. Configure your MCP client with the remote URL. Use OAuth when the client supports it, or provide an API key.

Authentication

Three methods are supported — use whichever your client supports:

Method

Format

OAuth 2.1

Connect to https://mcp.search1api.com/mcp without a key and follow the client sign-in flow

Authorization Header

Authorization: Bearer YOUR_SEARCH1API_KEY

URL Query Parameter (legacy)

https://mcp.search1api.com/mcp?apiKey=YOUR_SEARCH1API_KEY

Prefer OAuth or the Authorization header. Query-parameter credentials can be exposed in URLs, logs, and shell history.

Claude Desktop

{
  "mcpServers": {
    "search1api": {
      "url": "https://mcp.search1api.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_SEARCH1API_KEY"
      }
    }
  }
}

Claude.ai (Web)

Settings > Connectors > Add custom connector:

https://mcp.search1api.com/mcp?apiKey=YOUR_SEARCH1API_KEY

Cursor

Install as a Cursor plugin (recommended): this repo includes Agent Plugins plugin.json + mcp.json (portable) and .cursor-plugin/plugin.json (Cursor Marketplace metadata / logo) for Remote MCP with OAuth. Submit or install from cursor.directory / the Cursor Marketplace, then sign in when prompted.

For local testing, copy the plugin files into ~/.cursor/plugins/local/search1api (plugin.json, .cursor-plugin/, mcp.json, assets/). Do not symlink from outside that directory — Cursor rejects external symlink targets.

Or configure manually:

{
  "mcpServers": {
    "search1api": {
      "url": "https://mcp.search1api.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_SEARCH1API_KEY"
      }
    }
  }
}

VS Code

{
  "servers": {
    "search1api": {
      "type": "http",
      "url": "https://mcp.search1api.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_SEARCH1API_KEY"
      }
    }
  }
}

Claude Code

claude mcp add --transport http search1api https://mcp.search1api.com/mcp \
  --header "Authorization: Bearer YOUR_SEARCH1API_KEY"

Windsurf

{
  "mcpServers": {
    "search1api": {
      "serverUrl": "https://mcp.search1api.com/mcp?apiKey=YOUR_SEARCH1API_KEY"
    }
  }
}

Agent Skill

The Agent Skill has moved to search1api-cli. Install it with:

npm install -g search1api-cli
npx skills add superagents-lab/search1api-cli

Local Mode (stdio)

If you prefer to run the server locally, use Node.js 20 or newer with npx — no cloning required:

{
  "mcpServers": {
    "search1api": {
      "command": "npx",
      "args": ["-y", "search1api-mcp"],
      "env": {
        "SEARCH1API_KEY": "YOUR_SEARCH1API_KEY"
      }
    }
  }
}

For self-hosted HTTP deployments behind a proxy, add any internal hostnames that reach the Node.js process to the comma-separated MCP_ALLOWED_HOSTS environment variable. mcp.search1api.com and localhost addresses are allowed by default. Browser-based clients that send an Origin header must also have their trusted origin hostnames added to the comma-separated MCP_ALLOWED_ORIGINS variable. Requests from server-side MCP clients normally omit Origin and do not require an entry.

Tools

search

Search the web using Search1API. Results include a citable id/title/url structure. Pass a result URL to crawl when you need the full page.

Parameter

Required

Default

Description

query

Yes

-

Search query

max_results

No

10

Number of results

search_service

No

google

google, bing, duckduckgo, yahoo, x, reddit, github, youtube, arxiv, wechat, bilibili, imdb, wikipedia

crawl_results

No

0

Number of top results to crawl for full content; each successful crawl adds 1 credit to the base 1-credit search request

include_sites

No

[]

Sites to include

exclude_sites

No

[]

Sites to exclude

time_range

No

-

day, month, year

news

Search for news articles.

Parameter

Required

Default

Description

query

Yes

-

Search query

max_results

No

10

Number of results

search_service

No

bing

google, bing, duckduckgo, yahoo, hackernews

crawl_results

No

0

Number of top results to crawl for full content; each successful crawl adds 1 credit to the base 1-credit news request

include_sites

No

[]

Sites to include

exclude_sites

No

[]

Sites to exclude

time_range

No

-

day, month, year

crawl

Extract content from a URL.

Parameter

Required

Description

url

Yes

URL to crawl

sitemap

Get all related links from a URL.

Parameter

Required

Description

url

Yes

URL to get sitemap

trending

Get trending topics from popular platforms.

Parameter

Required

Default

Description

search_service

Yes

-

github, hackernews

max_results

No

10

Number of items

Version History

  • v0.6.1: Bug fix — MCP discovery (initialize, tools/list, resources/*, prompts/list, server/discover) requires a credential again. Serving it anonymously made clients that equate "tools listed" with "signed in" show a connected state with no way to trigger the OAuth flow; the 401 challenge now answers every unauthenticated request, restoring OAuth sign-in at connect time. Directory visibility is unchanged via the static server card and registry metadata

  • v0.6.0: MCP discovery (initialize, tools/list, resources/*, prompts/list, server/discover) is served without a credential so clients and directories can enumerate tools before signing in; tool calls still require OAuth or an API key. Stdio mode starts without SEARCH1API_KEY and serves tool metadata, refusing only at call time. Malformed requests answer as JSON-RPC instead of an HTML error page

  • v0.5.4: OAuth issuer moved to clerk.s1.dev and is configurable with OAUTH_AUTHORIZATION_SERVER; MCP server card published at /.well-known/mcp/server-card.json; OAuth discovery documents now send cache headers

  • v0.5.3: OAuth resource and tool metadata no longer require OIDC session scopes; Smithery and Glama registry badges added

  • v0.5.2: MCP Origin validation now runs before request parsing and authentication; self-hosted HTTP deployments can configure trusted browser origins with MCP_ALLOWED_ORIGINS

  • v0.5.1: Documentation, LobeHub manifest, and MCP Registry metadata synchronized; robots.txt served on the transport host

  • v0.5.0: MCP 2026-07-28 support with automatic protocol negotiation; stateless compatibility for 2025-era HTTP clients; request-level authentication

  • v0.4.0: Structured output schemas, OAuth security schemes, safety annotations, and Official MCP Registry metadata

  • v0.3.1: OAuth 2.1 support for Remote MCP; retired reasoning tool removed

  • v0.3.0: Remote MCP support via Streamable HTTP; per-session API key authentication

  • v0.2.0: Fallback .env support for LibreChat integration

  • v0.1.8: X (Twitter) and Reddit search services

  • v0.1.7: Trending tool for GitHub and Hacker News

  • v0.1.6: Wikipedia search service

  • v0.1.5: New search parameters and services (arxiv, wechat, bilibili, imdb)

  • v0.1.3: News search

  • v0.1.2: Sitemap

  • v0.1.1: Web crawling

  • v0.1.0: Initial release

License

MIT

Available Tools

5 tools
crawlRead a web pageA
Read-only
Inspect

Extract the readable title and full text from a public URL supplied by the user or returned by search.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesPublic HTTP or HTTPS URL to retrieve

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral detail by specifying that it extracts the readable title and full text, and clarifies the URL must be public. This goes beyond the annotations without contradicting them.

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?

A single, tightly written sentence that conveys the tool's purpose, input source, and output scope. Every phrase earns its place, and the core behavior is front-loaded.

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

Completeness5/5

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

For a simple, one-parameter, read-only tool with annotations and an output schema present, the description covers what the tool does, what it extracts, and where the URL comes from. Nothing essential is missing for an agent to select and invoke it correctly.

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?

Schema coverage is 100% and the single url parameter is already described as 'Public HTTP or HTTPS URL to retrieve'. The description reinforces the source of the URL but does not add significant new semantics beyond what the schema already provides. Baseline 3 is appropriate.

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?

States a specific verb ('Extract') and resource ('readable title and full text') from a public URL, making the tool's function immediately clear. It also distinguishes itself from search-related siblings by focusing on retrieving a specific existing URL rather than discovering pages.

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 gives clear context: use this when a public URL is already available, either supplied by the user or returned by search. It does not explicitly name alternatives or state when not to use it, but the scope is understandable without additional guidance.

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

newsSearch current newsA
Read-only
Inspect

Search current news when the user asks about recent events, announcements, or coverage. Returns citable article results with title, URL, snippet, and optional extracted text.

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesShort, focused news query
time_rangeNoOptional recency window; use day for breaking news
max_resultsNoMaximum number of articles to return
crawl_resultsNoNumber of top articles to retrieve as full pages. Each successful retrieval adds 1 credit to the base 1-credit news request
exclude_sitesNoNews domains to exclude
include_sitesNoNews domains to include
search_serviceNoNews search engine to usebing

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultsYes

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, and the description adds useful behavioral context: it produces citable article results and can return extracted text. It does not overpromise and no contradiction exists.

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?

Two sentences, front-loaded with the usage trigger before the return details, with no filler. Every clause earns its place.

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?

With a rich schema (100% coverage), annotations, and an output schema, the description is sufficient for a straightforward news lookup. It could be slightly more complete by pointing to a sibling for non-news trends, but nothing essential is missing.

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?

Schema description coverage is 100%, so the schema already documents all seven parameters. The description's only parameter-relevant contribution is implying that optional extracted text comes from the crawl behavior, which adds minimal extra meaning beyond the schema.

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 uses a specific verb and resource ('Search current news'), states the exact user trigger ('recent events, announcements, or coverage'), and names the return payload (citable articles with title, URL, snippet). This makes it easy to separate from sibling tools such as generic search or trending.

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?

It explicitly says to use this tool when the user asks about recent events, announcements, or coverage. It does not enumerate when-not conditions or alternative sibling tools, so it falls just short of the strongest guidance.

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

sitemapDiscover links on a siteA
Read-only
Inspect

Discover related public links from a page or domain when the user wants to explore a site's structure or available pages.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesPublic page or domain URL whose links should be discovered

Output Schema

ParametersJSON Schema
NameRequiredDescription
linksYes

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, openWorldHint=true, and destructiveHint=false, covering the safety profile. The description adds the 'public' and 'related' scope but does not disclose additional behaviors such as rate limits, breadth limits, or pagination. It adds some context without contradicting annotations.

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 a single, front-loaded sentence that combines the main action, target resource, and usage context without filler. Every clause earns its place.

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 simple one-parameter tool with an output schema and safe-read annotations, the description is largely sufficient. It clearly explains what the tool does and when to use it, though a brief note contrasting it with 'crawl' would make it fully 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?

Schema description coverage is 100%, and the url parameter is already well described in the schema. The main description only says 'from a page or domain,' which adds slight emphasis on accepted URL scope but does not meaningfully go beyond the structured parameter documentation.

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

Purpose4/5

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

The description states a specific verb ('Discover') and resource ('related public links from a page or domain') and adds the exploration use case. It is clear, though it does not explicitly differentiate itself from the sibling 'crawl' tool, which may perform a similar link-discovery function.

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 gives clear context for when to use the tool: 'when the user wants to explore a site's structure or available pages.' It does not mention exclusions or compare itself to alternatives such as 'crawl', so it stops short of full routing guidance.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev0.5.4
    • Removedfetch
  2. 6 tool updatesv0.4.0
    • Changedcrawl3 fields changed
      • changedInput schema / properties / url / description
        Previous value: -"URL to crawl"New value: +"Public HTTP or HTTPS URL to retrieve"
      • addedInput schema / properties / url / format
        Added value: +"uri"
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "properties": {
+        "id": {
+          "description": "Stable identifier for this result; for web results this is the canonical URL",
+          "type": "string"
+        },
+        "metadata": {
+          "additionalProperties": true,
+          "description": "Additional source metadata",
+          "type": "object"
+        },
+        "text": {
+          "description": "Result snippet or extracted page text when available",
+          "type": "string"
+        },
+        "title": {
+          "description": "Human-readable result title",
+          "type": "string"
+        },
+        "url": {
+          "description": "Canonical URL that clients can cite and users can open",
+          "format": "uri",
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "title",
+        "url"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}
    • Addedfetch
    • Changednews11 fields changed
      • changedInput schema / properties / crawl_results / description
        Previous value: -"Number of top results to crawl for full webpage content. Each successfully crawled page adds 1 credit to the base 1-credit news request"New value: +"Number of top articles to retrieve as full pages. Each successful retrieval adds 1 credit to the base 1-credit news request"
      • addedInput schema / properties / crawl_results / minimum
        Added value: +0
      • changedInput schema / properties / exclude_sites / description
        Previous value: -"List of sites to exclude from search. Only use when you need to explicitly filter out specific domains from results"New value: +"News domains to exclude"
      • changedInput schema / properties / include_sites / description
        Previous value: -"List of sites to include in search. Only use when you need special results from sites not available in search_service"New value: +"News domains to include"
      • changedInput schema / properties / max_results / description
        Previous value: -"Maximum number of results to return"New value: +"Maximum number of articles to return"
      • addedInput schema / properties / max_results / maximum
        Added value: +50
      • addedInput schema / properties / max_results / minimum
        Added value: +1
      • changedInput schema / properties / query / description
        Previous value: -"Search query, be simple and concise"New value: +"Short, focused news query"
      • changedInput schema / properties / search_service / description
        Previous value: -"Specify the news engine to use. Choose based on your specific needs"New value: +"News search engine to use"
      • changedInput schema / properties / time_range / description
        Previous value: -"Time range for search results, only use when specific time constraints are required"New value: +"Optional recency window; use day for breaking news"
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "properties": {
+    "results": {
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Stable identifier for this result; for web results this is the canonical URL",
+            "type": "string"
+          },
+          "metadata": {
+            "additionalProperties": true,
+            "description": "Additional source metadata",
+            "type": "object"
+          },
+          "text": {
+            "description": "Result snippet or extracted page text when available",
+            "type": "string"
+          },
+          "title": {
+            "description": "Human-readable result title",
+            "type": "string"
+          },
+          "url": {
+            "description": "Canonical URL that clients can cite and users can open",
+            "format": "uri",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "type": "object"
+}
    • Changedsearch10 fields changed
      • changedInput schema / properties / crawl_results / description
        Previous value: -"Number of top results to crawl for full webpage content. Each successfully crawled page adds 1 credit to the base 1-credit search request"New value: +"Number of top results to retrieve as full pages. Each successful page retrieval adds 1 credit to the base 1-credit search request"
      • addedInput schema / properties / crawl_results / minimum
        Added value: +0
      • changedInput schema / properties / exclude_sites / description
        Previous value: -"List of sites to exclude from search. Only use when you need to explicitly filter out specific domains from results"New value: +"Domains to exclude from the search"
      • changedInput schema / properties / include_sites / description
        Previous value: -"List of sites to include in search. Only use when you need special results from sites not available in search_service"New value: +"Domains to include when the user explicitly scopes the search"
      • addedInput schema / properties / max_results / maximum
        Added value: +50
      • addedInput schema / properties / max_results / minimum
        Added value: +1
      • changedInput schema / properties / query / description
        Previous value: -"Search query, be simple and concise"New value: +"Short, focused search query"
      • changedInput schema / properties / search_service / description
        Previous value: -"Specify the search engine to use. Choose based on your specific needs"New value: +"Search engine to use; choose one only when it matches the user's source intent"
      • changedInput schema / properties / time_range / description
        Previous value: -"Time range for search results, only use when specific time constraints are required"New value: +"Optional recency window for time-sensitive searches"
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "properties": {
+    "results": {
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Stable identifier for this result; for web results this is the canonical URL",
+            "type": "string"
+          },
+          "metadata": {
+            "additionalProperties": true,
+            "description": "Additional source metadata",
+            "type": "object"
+          },
+          "text": {
+            "description": "Result snippet or extracted page text when available",
+            "type": "string"
+          },
+          "title": {
+            "description": "Human-readable result title",
+            "type": "string"
+          },
+          "url": {
+            "description": "Canonical URL that clients can cite and users can open",
+            "format": "uri",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "type": "object"
+}
    • Changedsitemap3 fields changed
      • changedInput schema / properties / url / description
        Previous value: -"URL to get sitemap"New value: +"Public page or domain URL whose links should be discovered"
      • addedInput schema / properties / url / format
        Added value: +"uri"
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "properties": {
+    "links": {
+      "items": {
+        "format": "uri",
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "links"
+  ],
+  "type": "object"
+}
    • Changedtrending4 fields changed
      • addedInput schema / properties / max_results / maximum
        Added value: +50
      • addedInput schema / properties / max_results / minimum
        Added value: +1
      • changedInput schema / properties / search_service / description
        Previous value: -"Specify the platform to get trending topics from"New value: +"Platform whose trending items should be returned"
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "properties": {
+    "results": {
+      "items": {
+        "properties": {
+          "description": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "format": "uri",
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "type": "object"
+}
  3. 3 tool updatesv0.3.1
    • Changednews1 field changed
      • changedInput schema / properties / crawl_results / description
        Previous value: -"Number of results to crawl for full webpage content, useful when search result summaries are insufficient for complex queries"New value: +"Number of top results to crawl for full webpage content. Each successfully crawled page adds 1 credit to the base 1-credit news request"
    • Removedreasoning
    • Changedsearch1 field changed
      • changedInput schema / properties / crawl_results / description
        Previous value: -"Number of results to crawl for full webpage content, useful when search result summaries are insufficient for complex queries"New value: +"Number of top results to crawl for full webpage content. Each successfully crawled page adds 1 credit to the base 1-credit search request"
  4. 6 tool updatesv0.1.8
    • First observedcrawl
    • First observednews
    • First observedreasoning
    • First observedsearch
    • First observedsitemap
    • First observedtrending
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.1/5.0

Scored across 5 tools

Disambiguation4/5

Each tool targets a distinct need—general web search, news search, page extraction, site exploration, and trending content—but search and news/trending overlap somewhat on current/popular information. Descriptions are clear enough that an agent should usually pick the right one.

Naming Consistency4/5

All tool names are short, lowercase, single words, giving a consistent visual style. However, they mix verbs (search, crawl) with nouns/adjectives (news, sitemap, trending), so there is no uniform verb_noun or action_entity pattern.

Tool Count5/5

Five tools is a well-scoped number for a search/information-retrieval server. Each tool adds a distinct capability without bloat or redundancy.

Completeness5/5

The server covers the full search-to-content workflow: discover via search/news/trending, explore site structure via sitemap, and fetch full text via crawl. No major missing operation is evident for its stated purpose.

Maintenance

ActivityMaintained
ResponsivenessResponsive

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches