updated 2026-08-12 05:02 UTC

Agent Search MCP

lennney/agent-search-mcp

Free-first web search MCP with zero-key English and Chinese sources and compact evidence.

MCP Servers TypeScript Grade D Listed Apache-2.0
22.9/100
Rank #930 of 1283
Compare Agent Search MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

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

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade D · 1/5 signals
Last push
2026-08-11 · 1d ago
Recent change
Rank +1

Is Agent Search MCP safe? Agent Search MCP scores 22.9/100 (Grade D), ranked #930 of 1283 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 11% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#466 NotebookLM MCP — 23.0 (D) → #467 Prometheus MCP Server — 22.9 (D) → #469 Happy Platform MCP — 22.8 (D) → #470 Mailtrap — 22.8 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 48 spots (#878 → #926)
2026-08-08
Newly Listed
First tracked at rank #871
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
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 Agent Search MCP View MCP Servers Report missing data
66.5
Activity sub-score · out of 100
#468
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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
104
Forks
8
Last Push
2026-08-11
yesterday
Commits (4 wk)
219
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
▲1
was #931

Analysis

HVTrust Dimensions vs MCP Servers

22.9 / 100 · 40.0% confidence

Agent Search MCP MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
0.6 / 25
4.4 below avg 5.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.5 below avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.8
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
7.5 above avg 12.4
AdoptionLog-scaled stars · package downloads
4.9 / 20
0.9 below avg 5.8

Activity Inputs

66.5 / 100
StarsRepository reach
12.1 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
4.4 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
11%
of last 100 commits verified

Is Agent Search MCP safe?

Public trust evidence for Agent Search 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 Agent Search MCP publish package provenance?
No published build provenance is currently detected for Agent Search 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 Agent Search MCP have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Agent Search MCP. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Agent Search MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Agent Search MCP use?
Agent Search MCP ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Agent Search MCP's commits signed?
11% of the last 100 commits to Agent Search 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
Agent Search 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
None detected
No clear plugin system or broad tool 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

Maintain Agent Search MCP?

For maintainers

HVTrust scores Agent Search 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Listed 1Rank 1
2026-08-10
Rank Moved
Rank dropped 48 spots (#878 → #926)
2026-08-08
Newly Listed
First tracked at rank #871
GitHub → npm: agent-search-mcp

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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