Serpapi MCP

SerpApi MCP Server for Google and other search engine results

MCP Servers Python Grade C Listed MIT
50.9/100
Rank #737 of 1320
Compare Serpapi MCP

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-09-01 · 3d ago
Recent change
Rank +10

Is Serpapi MCP safe? Serpapi MCP scores 50.9/100 (Grade C), ranked #737 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.5/10; 63% of recent commits are signed; last pushed 2026-09-01. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-04
Rank Moved
Rank dropped 15 spots (#722 → #737)
2026-09-03
Rank Moved
Rank dropped 65 spots (#657 → #722)
2026-09-02
Scorecard Added
OSSF Scorecard: 4.5/10
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.5/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
52.9
Activity sub-score · out of 100
#376

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

Signals refreshed 2026-09-04 14:33 UTC · Repo last pushed 3 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
168
Forks
38
Last Push
2026-09-01
3 days ago
Commits (4 wk)
3?
Downloads (7d)
HN mentions (30d)
Open Issues
4
Rank Change
▼15
was #722

Analysis

HVTrust Dimensions vs MCP Servers

50.9 / 100 · 100.0% confidence

Serpapi MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.8 / 25
0.7 below avg 9.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
12.3 / 17
0.5 above avg 11.8
Maintenance60% last-push freshness · 40% commit activity
13.0 / 20
0.8 above avg 12.2
AdoptionLog-scaled stars · package downloads
5.3 / 20
0.9 below avg 6.2

Activity Inputs

52.9 / 100
StarsRepository reach
13.4 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
7.5 / 25
CommunityFork signal
7.4 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.5 / 10
OpenSSF Scorecard · scanned Sep 2, 2026
Signed Commits
63%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 8
CI-Tests 10
CII-Best-Practices 0
Code-Review 4
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Is Serpapi MCP safe?

Public trust evidence for Serpapi MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Serpapi MCP publish package provenance?
No published build provenance is currently detected for Serpapi MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Serpapi MCP have an OpenSSF Scorecard?
Serpapi MCP 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 Serpapi MCP actively maintained?
Actively maintained. The repository was pushed to within the last 3 day(s).
What license does Serpapi MCP use?
Serpapi MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Serpapi MCP's commits signed?
63% of the last 100 commits to Serpapi MCP 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
Serpapi MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
1 tags
Broad capability areas detected.
  • search
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Serpapi MCP?

For maintainers

HVTrust scores Serpapi MCP 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.

Reputation Timeline

Signal history
Rank 16Listed 1HVTrust 1Grade 1Scorecard 1
2026-09-04
Rank Moved
Rank dropped 15 spots (#722 → #737)
2026-09-03
Rank Moved
Rank dropped 65 spots (#657 → #722)
2026-09-02
Scorecard Added
OSSF Scorecard: 4.5/10
2026-09-02
Grade Changed
Trust grade D → C
2026-09-02
Rank Moved
Rank rose 571 spots (#1228 → #657)
2026-09-02
HVTrust Changed
HVTrust up 30.4pts (21.7 → 52.1)
2026-09-01
Rank Moved
Rank dropped 15 spots (#1213 → #1228)
2026-08-31
Rank Moved
Rank dropped 24 spots (#1189 → #1213)
2026-08-30
Rank Moved
Rank dropped 25 spots (#1164 → #1189)
2026-08-29
Rank Moved
Rank dropped 29 spots (#1135 → #1164)
2026-08-28
Rank Moved
Rank dropped 27 spots (#1108 → #1135)
2026-08-27
Rank Moved
Rank dropped 22 spots (#1086 → #1108)
2026-08-26
Rank Moved
Rank dropped 73 spots (#1013 → #1086)
2026-08-17
Rank Moved
Rank rose 11 spots (#1011 → #1000)
2026-08-16
Rank Moved
Rank dropped 32 spots (#979 → #1011)
2026-08-14
Rank Moved
Rank rose 12 spots (#991 → #979)
2026-08-13
Rank Moved
Rank rose 15 spots (#1006 → #991)
2026-08-12
Rank Moved
Rank rose 12 spots (#1018 → #1006)
2026-08-10
Rank Moved
Rank dropped 61 spots (#952 → #1013)
2026-08-08
Newly Listed
First tracked at rank #947

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 50.9 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/serpapi-mcp.svg)](https://hvtracker.net/agents/serpapi-mcp)
HTML:
<a href="https://hvtracker.net/agents/serpapi-mcp"><img src="https://hvtracker.net/badge/serpapi-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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