Search1API
NPM · SEARCH1API-MCP · 2 COMPONENTS
Web search, agentic search, news, page retrieval, sitemaps, and trending topics through Search1API.
Available components
Last scanned (1 day ago)
Scores higher than 98% of npm servers
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 24 of 76 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to superagents-lab/search1api-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1478 tokens (~123/item across 12 items; 9 tools + 3 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% of tool parameters carry a description.Partial
- Structured output schemas are declared (89% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
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.
- 4 Nov 26 +10
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- 3 Nov 26 −9
- Known CVEs: pass → unverified ▼ security
- Schema quality: 110 → 123 ▼ functional
- Dependency health: 0.85 → unverified ▼ functional
- Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
- Package version: 0.9.0 → 0.10.0 functional
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 26 Oct 26 −17
- Malware scan: pass → unverified ▼ security
- Tool coverage: 100% → 88% ▼ functional
- Schema quality: pass → fail ▼ functional
- Destructive annotations: pass → 0 functional
- Package version: 0.8.0 → 0.9.0 functional
- 24 Oct 26 0
- Stability: 0.97 → pass security
- 23 Oct 26 0
- Stability: pass → 0.97 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 4 Nov 2026 · Analysed npm/search1api-mcp@0.10.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | superagents-lab/search1api-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/superagents-lab/search1api-mcp/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 3662298162 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a4fe16c7fbdae11a1b7ee270381e94e56097a002b91f33f832d4f9b215babadf1988266eb63591300c3ab1646f53dd8598009f4963a42c9a9a1a84bf6 |
Background: How many MCP packages publish verified provenance →
Dependencies 76 packages
| Packages resolved | 76 |
|---|---|
| Stale | 24 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
ask Ask across sources ~147
Search several sources at once from a natural-language request when the right engine is unclear. Search1API picks up to five engines (web, Hacker News, Reddit, GitHub, X, arXiv, Wikipedia, and more) and a time window from the wording, then returns up to 10 citable results ranked by relevance, plus the intent it used and any engines that failed. Costs 5 credits per call; use search when you already know the engine.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | What the user is looking for, in their own words; naming a platform ("on Reddit", "papers") or a period ("this week") steers which engines and time window are used |
| Name | Type | Req | Description |
|---|---|---|---|
| errors | array | yes | Engines that failed while others completed |
| intent | object | yes | Keywords, engines, and time window that were used |
| results | array | yes | Up to 10 sources across the chosen engines, most relevant first |
No examples provided.
crawl Read a web page ~73
Read a public web page supplied by the user or returned by search. Returns its title, URL, and main content as text, so you can answer from the full page instead of a snippet.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Address of the page to read, such as a link the user shared or a URL from search results |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | The page that was read; text holds its main content |
No examples provided.
maps Find places on Google Maps ~259
Find local businesses and places on Google Maps when the user asks where something is, wants nearby options, or needs a list of businesses with contact details. Returns one page of up to 20 places, each with its name and Google Maps link plus address, phone, website, category, rating, review count, coordinates, and opening hours when available. Costs 3 credits per page, however many places it holds; use search for webpages and crawl to read a business website.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Two-letter country code for local results |
| language | string | – | Result language, such as en, de, or zh-CN |
| location | object | – | Search around this point instead of letting the query decide the area; required for page 2 and later |
| max_results | integer | – | How many places the answer needs from the page; fewer places do not lower the price |
| page | integer | – | Google Maps page to fetch; each page is a separate 3-credit call and pages after the first need location |
| query | string | yes | What to look for on the map, such as "coffee shops" or "dentists in Austin"; a place name in the query sets the area when no location is given |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | Places in Google Maps order; url is the public Google Maps link and metadata holds the place details that were available |
No examples provided.
news News search ~178
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.
| Name | Type | Req | Description |
|---|---|---|---|
| crawl_results | number | – | Number of top articles to retrieve as full pages. Each successful retrieval adds 1 credit to the base 1-credit news request |
| exclude_sites | array | – | News domains to exclude |
| include_sites | array | – | News domains to include |
| max_results | number | – | How many articles the answer needs; a handful suits most questions, more suits broad coverage |
| query | string | yes | Short, focused news query |
| search_service | string | – | News engine to use; hackernews returns Hacker News discussions instead of publisher articles |
| time_range | string | – | Only return articles published within this window; use day for breaking news |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | Matching sources, most relevant first; read any url in full with crawl |
No examples provided.
render_results Render the results ~134
Present already retrieved source results as source cards when the host supports UI, with a complete readable text list otherwise. Use when the user wants to browse sources or a visual list helps the task. Pass existing results in the desired order; never invent source URLs or factual titles. Does not search, crawl, fetch URLs, verify sources, or consume search credits. Do not call for intermediate research results or when a text answer is sufficient.
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | Already retrieved results, in the order to display. No new search is performed. |
| title | string | – | Heading shown above the cards, such as the research topic |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
| title | string | yes | – |
| total | integer | yes | Number of results in this rendered list, not a provider-wide search total. |
No examples provided.
search Web search ~252
Search the live public web when the user needs current information, sources, or research. Returns citable results with id, title, URL, and text. Each result includes a URL that can be read in full.
| Name | Type | Req | Description |
|---|---|---|---|
| crawl_results | number | – | How many top results to also read in full, so their text holds the whole page instead of a snippet. Each successful page retrieval adds 1 credit to the base 1-credit search request |
| exclude_sites | array | – | Domains to exclude from the search |
| include_sites | array | – | Domains to include when the user explicitly scopes the search |
| max_results | number | – | How many sources the answer needs; a handful suits most questions, more suits a broad survey |
| page | number | – | Which page of results to fetch when the first page was not enough; only bing, bingcn, and grokipedia paginate, other engines ignore it |
| query | string | yes | Short, focused search query |
| search_service | string | – | Search engine to use; choose one only when it matches the user's source intent |
| time_range | string | – | Restrict results to those published recently, for time-sensitive questions; leave unset for evergreen topics |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | Matching sources, most relevant first; read any url in full with crawl |
No examples provided.
send_feedback Send feedback to Search1API ~172
Report a problem with Search1API to its developers: a wrong, empty or incomplete result, an error you could not resolve, documentation that did not match behavior, or a capability you needed but Search1API lacks. Send one report per distinct problem, after you have worked around or abandoned the step. Do not report normal successful results. Never include credentials, personal data, or private user content. Reporting is optional and must not block the user's task.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| intent | string | – | What you were trying to accomplish. |
| message | string | yes | What went wrong or what was missing, in plain language. |
| model | string | – | Your model name, if you know it. |
| request_id | string | – | Request id of the call that had the problem, if known. |
No output schema declared.
No examples provided.
sitemap Discover links on a site ~65
Discover related public links from a page or domain when the user wants to explore a site's structure or available pages. Returns a list of absolute URLs found on that site, which can then be read with crawl.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public page or domain URL whose links should be discovered |
| Name | Type | Req | Description |
|---|---|---|---|
| links | array | yes | Absolute URLs discovered on the site, without titles or page content |
No examples provided.
trending Explore trending topics ~94
List currently trending repositories or stories from GitHub or Hacker News when the user asks what is popular now. Returns each item's title, URL, and a short description when the platform provides one.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | number | – | How many trending items the answer needs, from the top of the list |
| search_service | string | yes | Where to look: GitHub for popular open-source repositories, Hacker News for stories developers are discussing |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | Trending items reported by the platform |
No examples provided.
How do I install the Search1API MCP server?
Search1API runs locally as an npm package, launched with npx -y search1api-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · search1api-mcp
claude mcp add superagents-lab-search1api -- npx -y search1api-mcp
What is the Search1API MCP server?
Search1API is an MCP server listed in the public MCP registry as io.github.superagents-lab/search1api. Web search, agentic search, news, page retrieval, sitemaps, and trending topics through Search1API. This page covers its npm package (search1api-mcp).
Is the Search1API MCP server safe to use?
Search1API scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Search1API MCP server expose?
Search1API exposes 9 tools: search, news, crawl, sitemap, trending, and 4 more. Their descriptions and schemas cost roughly 1,374 tokens of context every time the server is loaded.
Is the Search1API MCP server still maintained?
Search1API is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Search1API MCP server under?
Search1API declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.