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

REMOTE · MCP.SEARCH1API.COM · 2 COMPONENTS · SCANNED SEP 20

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

0 this week 36 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security91
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
  • Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.

Install

How do I install the Search1API MCP server?

Search1API is a hosted endpoint at https://mcp.search1api.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.search1api.com

# add to Claude Code
claude mcp add --transport http superagents-lab-search1api 'https://mcp.search1api.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "superagents-lab-search1api": {
      "url": "https://mcp.search1api.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "superagents-lab-search1api": {
      "type": "http",
      "url": "https://mcp.search1api.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.superagents-lab-search1api]
url = "https://mcp.search1api.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "superagents-lab-search1api": {
      "type": "remote",
      "url": "https://mcp.search1api.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add superagents-lab-search1api --url 'https://mcp.search1api.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  superagents-lab-search1api:
    url: "https://mcp.search1api.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "superagents-lab-search1api": {
      "Transport": "http",
      "Url": "https://mcp.search1api.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add superagents-lab-search1api -t streamable-http -u 'https://mcp.search1api.com/mcp'
// mcp.json
{
  "mcpServers": {
    "superagents-lab-search1api": {
      "type": "http",
      "url": "https://mcp.search1api.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 3 Sept 26 −46
    • Endpoint reachability: reachable → behind authorisation security
    • Tool safety: pass → unverified security
    • Stability: 0.20 → unverified security
    • Transport: pass → unverified security
    • Authorization: The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. security
    • Capabilities: pass → unverified functional
    • Schema quality: 100 → unverified functional
    • Tool coverage: 100 → unverified functional
  • 1 Sept 26 +1

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

  • 30 Aug 26 +1

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

  • 28 Aug 26 +1
    • Stability: unverified → 0.03 functional
  • 27 Aug 26 +43
    • Injection markers: unverified → pass security
    • Transport: unverified → pass security
    • First check of Judged manipulation: pass security
    • Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. security
    • Tool coverage: unverified → 100 functional
    • Schema quality: unverified → 100 functional
    • MCP protocol: unverified → pass functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 100 functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: good functional
    • First check of Schema quality: pass functional
    • First check of Destructive annotations: pass functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 1 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 · Probed https://mcp.search1api.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.search1api.com CN=YR2,O=Let's Encrypt,C=US 27 Aug 2026 25 Nov 2026 RSA 4096 SHA256-RSA 5123cb32bdcfd048b90193747698231374e
SANs: mcp.search1api.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of mcp.search1api.com. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
search1api.com. present 2371 13 Verified
mcp.search1api.com. Verified address RRset verified with the apex keys
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On connection
HTTP status 401

WWW-Authenticate challenge Bearer resource_metadata="https://mcp.search1api.com/.well-known/oauth-protected-resource/mcp"

Bearer resource_metadata="https://mcp.search1api.com/.well-known/oauth-protected-resource/mcp"
Header Value
www-authenticate Bearer resource_metadata="https://mcp.search1api.com/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

Document https://mcp.search1api.com/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://mcp.search1api.com/mcp
Authorisation server https://clerk.s1.dev

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.search1api.com/mcp Auth required 401
http (plaintext) http://mcp.search1api.com/mcp HTTPS enforced 301 https://mcp.search1api.com/mcp
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 hosted endpoint (https://mcp.search1api.com/mcp).

Is the Search1API MCP server safe to use?

Search1API scores 36 out of 100 on VerifyMCP. 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.

Does the Search1API MCP server require authentication?

Yes. Search1API asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

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.