Is Search1API safe to use?

Search1API has an HVTrust score of 71.9/100 (Grade B), ranked #295 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Search1API?

Search1API scores 71.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 174 GitHub stars and is categorized under MCP Servers.

Search1API

superagents-lab/search1api-mcp

Official Search1API MCP server for web search, news, crawling, sitemaps, and trends—hosted with OAuth 2.1 or local via npm.

MCP Servers TypeScript Listed MIT

Is Search1API safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.5 / 10

Provenance Attested

Signed commits 16%

Last push 23d ago

Compare Search1API

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Search1API scores 71.9/100 (Grade B), ranked #295 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.5/10; 16% of recent commits are signed; last pushed 2026-09-03. Every point is earned from checkable signals — never paid placement. How scoring works →

How Search1API compares in MCP Servers

Bars show each HVTrust score; the tick marks Search1API’s 71.9.

Where the 71.9 comes from

HVTrust dimensions vs the MCP Servers average

71.9 / 100 · 100.0% confidence

Search1API MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

13.9 / 25

3.6 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.3 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

13.6 / 20

1.5 above avg 12.1

AdoptionLog-scaled stars · package downloads

8.4 / 20

1.2 above avg 7.2

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-09-25

Rank Moved

Rank dropped 11 spots (#285 → #296)

2026-09-24

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-24

Rank Moved

Rank dropped 10 spots (#275 → #285)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.5/10. Tighten the weakest checks to improve public safety evidence.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for Search1API View MCP Servers Report missing data

52.5

Activity sub-score · out of 100

#174

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

174

Forks

Last Push

2026-09-03

23 days ago

Commits (4 wk)

Downloads (7d)

193

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #296

Analysis

Activity Inputs

52.5 / 100

StarsRepository reach

13.5 / 30

FreshnessLast push recency

21.8 / 25

ActivityRecent commits

9.7 / 25

CommunityFork signal

7.4 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

4.5 / 10

OpenSSF Scorecard · scanned Sep 23, 2026

Signed Commits

16%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 9

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 3

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 9

Vulnerabilities 0

Common questions about Search1API

Search1API has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Search1API publish package provenance?

Yes. Search1API's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Search1API have an OpenSSF Scorecard?

Search1API has an OpenSSF Scorecard score of 4.5/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Search1API actively maintained?

Maintained. Last push was 23 days ago.

What license does Search1API use?

Search1API ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Search1API's commits signed?

15% of the last 100 commits to Search1API are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

Search1API appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Search1API's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-24

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain Search1API?

For maintainers

HVTrust scores Search1API from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-25

Rank Moved

Rank dropped 11 spots (#285 → #296)

2026-09-24

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-24

Rank Moved

Rank dropped 10 spots (#275 → #285)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 641 spots (#916 → #275)

2026-09-23

HVTrust Changed

HVTrust up 46.1pts (26.5 → 72.6)

2026-09-22

Newly Listed

First tracked at rank #916

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-11

Rank Moved

Rank rose 13 spots (#264 → #251)

2026-09-07

Rank Moved

Rank dropped 19 spots (#229 → #248)

2026-09-06

Rank Moved

Rank dropped 36 spots (#193 → #229)

2026-09-05

Rank Moved

Rank dropped 48 spots (#145 → #193)

2026-09-03

Grade Changed

Trust grade D → B

2026-09-03

Rank Moved

Rank rose 587 spots (#729 → #142)

2026-09-03

HVTrust Changed

HVTrust up 26.4pts (49.4 → 75.8)

2026-09-02

Scorecard Added

OSSF Scorecard: 4.8/10

2026-09-02

Rank Moved

Rank rose 134 spots (#863 → #729)

2026-09-02

HVTrust Changed

HVTrust up 6.8pts (42.6 → 49.4)

2026-09-01

Rank Moved

Rank dropped 37 spots (#826 → #863)

2026-08-31

Rank Moved

Rank dropped 30 spots (#796 → #826)

2026-08-30

Rank Moved

Rank dropped 27 spots (#769 → #796)

2026-08-29

Rank Moved

Rank dropped 54 spots (#715 → #769)

2026-08-28

Rank Moved

Rank dropped 30 spots (#685 → #715)

2026-08-27

Rank Moved

Rank dropped 22 spots (#663 → #685)

2026-08-26

Rank Moved

Rank dropped 86 spots (#577 → #663)

2026-08-13

Rank Moved

Rank dropped 13 spots (#550 → #563)

2026-08-10

Rank Moved

Rank dropped 21 spots (#539 → #560)

2026-08-08

Newly Listed

First tracked at rank #538

GitHub → npm: search1api-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/search1api.svg)](https://hvtracker.net/agents/search1api)
            
HTML:
            <a href="https://hvtracker.net/agents/search1api"><img src="https://hvtracker.net/badge/search1api.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON