Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Search1API

NPM · SEARCH1API-MCP · 2 COMPONENTS · SCANNED SEP 20

Web search, news, page retrieval, sitemaps, and trending topics through Search1API.

+5 this week 93 Trust /100
Trust breakdown (7 categories)

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
  • 25 of 77 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 16 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability83
  • 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
  • Tool/resource definitions use about 495 tokens (~82/item across 6 items; 5 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 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
  • Structured output schemas are declared (100% 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
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
Install

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

# add to Claude Code
claude mcp add superagents-lab-search1api -- npx -y search1api-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "superagents-lab-search1api": {
      "command": "npx",
      "args": [
        "-y",
        "search1api-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "superagents-lab-search1api": {
      "command": "npx",
      "args": [
        "-y",
        "search1api-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add superagents-lab-search1api -- npx -y search1api-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "superagents-lab-search1api": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "search1api-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add superagents-lab-search1api --command npx --arg -y --arg search1api-mcp
# ~/.hermes/config.yaml
mcp_servers:
  superagents-lab-search1api:
    command: "npx"
    args: ["-y", "search1api-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "superagents-lab-search1api": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "search1api-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add superagents-lab-search1api -t stdio -c npx -a -y search1api-mcp
// mcp.json
{
  "mcpServers": {
    "superagents-lab-search1api": {
      "command": "npx",
      "args": [
        "-y",
        "search1api-mcp"
      ]
    }
  }
}
Changelog

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.

  • 19 Sept 26 +1
    • Security disclosure: fail → unverified functional
  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +2
    • CVE-2026-82417 no longer affects this package security
    • CVE-2026-82562 no longer affects this package security
    • Known CVEs: fail → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 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.

  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Sept 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.

Diagnostics

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 20 Sept 2026 · Analysed npm/search1api-mcp@0.6.1

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/tags/v0.6.1
Rekor log index 2701689533
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:fad0570c4b295dc7c21cbc5f4dd9469beb2438bea958d2f2bd01236775de57a6646ba05b640b3e4166aab8b1c85293ec9c5f76810e92f720e2086112d

Background: How many MCP packages publish verified provenance →

Dependencies 77 packages
Packages resolved 77
Stale 25
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~480 tokens

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 →

Tool Tokens
crawl ~41

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

NameTypeReqDescription
urlstringyesPublic HTTP or HTTPS URL to retrieve
NameTypeReqDescription
resultobjectyes

No examples provided.

news ~154

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.

NameTypeReqDescription
crawl_resultsnumberNumber of top articles to retrieve as full pages. Each successful retrieval adds 1 credit to the base 1-credit news request
exclude_sitesarrayNews domains to exclude
include_sitesarrayNews domains to include
max_resultsnumberMaximum number of articles to return
querystringyesShort, focused news query
search_servicestringNews search engine to use
time_rangestringOptional recency window; use day for breaking news
NameTypeReqDescription
resultsarrayyes

No examples provided.

search ~181

Search the live public web when the user needs current information, sources, or research. Returns citable results with id, title, URL, and text. Pass a result URL to crawl to retrieve the full page.

NameTypeReqDescription
crawl_resultsnumberNumber of top results to retrieve as full pages. Each successful page retrieval adds 1 credit to the base 1-credit search request
exclude_sitesarrayDomains to exclude from the search
include_sitesarrayDomains to include when the user explicitly scopes the search
max_resultsnumberMaximum number of results to return
querystringyesShort, focused search query
search_servicestringSearch engine to use; choose one only when it matches the user's source intent
time_rangestringOptional recency window for time-sensitive searches
NameTypeReqDescription
resultsarrayyes

No examples provided.

sitemap ~46

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

NameTypeReqDescription
urlstringyesPublic page or domain URL whose links should be discovered
NameTypeReqDescription
linksarrayyes

No examples provided.

trending ~58

List currently trending repositories or stories from GitHub or Hacker News when the user asks what is popular now.

NameTypeReqDescription
max_resultsnumberMaximum number of trending items to return
search_servicestringyesPlatform whose trending items should be returned
NameTypeReqDescription
resultsarrayyes

No examples provided.

Common questions

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, 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 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 5 tools: search, news, crawl, sitemap, trending. Their descriptions and schemas cost roughly 480 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 20 September 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.