updated 2026-10-16 20:06 UTC

Agent Search MCP

Repository Website by lennney

Free-first Chinese and English web search MCP using zero-key sources and inspectable evidence.

MCP Servers TypeScript Listed Apache-2.0

Is Agent Search MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.5 / 10
Provenance None
Signed commits 19%
Last push 25d ago
Advisories None known
Compare Agent Search MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Agent Search MCP scores 55.0/100 (Grade C), ranked #842 of 1378 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.5/10; 19% of recent commits are signed; no published advisory affects its latest release (agent-search-mcp); last pushed 2026-09-21. Every point is earned from checkable signals — never paid placement. How scoring works →

How Agent Search MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Agent Search MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/lennney/agent-search-mcp, Apache-2.0, last pushed 2026-09-21. 19% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.5/10 (scanned Oct 14, 2026). The checks that decide who can get a change released:

    • Code Review2
    • Branch Protection3
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies4
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 3
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 2
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 4
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked, not attested

    • npm agent-search-mcp Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: agent-search-mcp 3.2.1. No published advisory affects it (OSV, checked 2026-10-16).

Changes to this chain

  • 2026-08-30 OSSF Scorecard: 4.5/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Agent Search MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Agent Search MCP compares in MCP Servers

  1. #455 Plateau Creative MCP 55.1 +0.1
  2. #456 Local Memory 55.0 ±0
  3. #457 Agent Search MCP 55.0 this agent
  4. #458 DMontgomery40 DeepSeek MCP Server 54.9 −0.1
  5. #459 Paper Distill MCP 54.8 −0.2

Bars show each HVTrust score; the tick marks Agent Search MCP’s 55.0.

Where the 55.0 comes from

HVTrust dimensions vs the MCP Servers average

55.0 / 100 · 100.0% confidence

Agent Search MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.8 / 25
2.7 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
13.2 / 17
0.9 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
10.3 / 20
2.0 below avg 12.3
AdoptionLog-scaled stars · package downloads
7.9 / 20
in line with avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-16
Rank Moved
Rank dropped 136 spots (#706 → #842)
2026-10-16
HVTrust Changed
HVTrust down 3.7pts (58.7 → 55.0)
2026-10-16
Activity Score Changed
Activity score down 12pts (50 → 39)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.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.
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
38.8
Activity sub-score · out of 100
#457
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 C 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 →

Signals refreshed 2026-10-16 20:06 UTC · Repo last pushed 25 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
111
Forks
11
Last Push
2026-09-21
25 days ago
Commits (4 wk)
0
Downloads (7d)
162
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▼136
was #706

Analysis

Activity Inputs

38.8 / 100
StarsRepository reach
12.3 / 30
FreshnessLast push recency
21.5 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
5.0 / 20

Common questions about Agent Search MCP

Agent Search MCP 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 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?
Agent Search MCP has an OpenSSF Scorecard score of 5.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 Agent Search MCP actively maintained?
Maintained. Last push was 25 days ago.
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?
19% 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
How this surface has changed

Detected changes to Agent Search MCP'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-23
Provider Added
Runtime surface grew — new detected provider dependency: Tavily
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

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
Rank 30HVTrust 6Score 3Listed 2Grade 2Scorecard 1Delisted 1MCP 1Surface 1
2026-10-16
Rank Moved
Rank dropped 136 spots (#706 → #842)
2026-10-16
HVTrust Changed
HVTrust down 3.7pts (58.7 → 55.0)
2026-10-16
Activity Score Changed
Activity score down 12pts (50 → 39)
2026-10-09
Rank Moved
Rank dropped 12 spots (#669 → #681)
2026-09-24
Rank Moved
Rank rose 45 spots (#726 → #681)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Tavily
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 141 spots (#867 → #726)
2026-09-23
HVTrust Changed
HVTrust up 29.0pts (27.5 → 56.5)
2026-09-22
Newly Listed
First tracked at rank #867
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-17
Rank Moved
Rank dropped 42 spots (#676 → #718)
2026-09-16
Rank Moved
Rank rose 190 spots (#866 → #676)
2026-09-16
HVTrust Changed
HVTrust up 5.7pts (52.1 → 57.8)
2026-09-16
Activity Score Changed
Activity score up 16pts (38 → 54)
2026-09-11
Rank Moved
Rank dropped 18 spots (#847 → #865)
2026-09-10
Rank Moved
Rank dropped 97 spots (#750 → #847)
2026-09-10
HVTrust Changed
HVTrust down 3.2pts (55.3 → 52.1)
2026-09-10
Activity Score Changed
Activity score down 10pts (48 → 39)
2026-09-09
Rank Moved
Rank dropped 54 spots (#696 → #750)
2026-09-08
Rank Moved
Rank dropped 18 spots (#678 → #696)
2026-09-07
Rank Moved
Rank dropped 80 spots (#598 → #678)
2026-09-06
Rank Moved
Rank dropped 34 spots (#564 → #598)
2026-09-05
Grade Changed
Trust grade D → C
2026-09-05
Rank Moved
Rank rose 514 spots (#1078 → #564)
2026-09-05
HVTrust Changed
HVTrust up 19.8pts (38.9 → 58.7)
2026-09-04
Rank Moved
Rank dropped 25 spots (#1053 → #1078)
2026-09-03
Rank Moved
Rank dropped 55 spots (#998 → #1053)
2026-09-02
Rank Moved
Rank dropped 45 spots (#953 → #998)
2026-09-01
Rank Moved
Rank dropped 39 spots (#914 → #953)
2026-08-31
Rank Moved
Rank dropped 33 spots (#881 → #914)
2026-08-30
Scorecard Added
OSSF Scorecard: 4.5/10
2026-08-30
Rank Moved
Rank rose 265 spots (#1146 → #881)
2026-08-30
HVTrust Changed
HVTrust up 17.4pts (21.7 → 39.1)
2026-08-29
Rank Moved
Rank dropped 31 spots (#1115 → #1146)
2026-08-28
Rank Moved
Rank dropped 25 spots (#1090 → #1115)
2026-08-27
Rank Moved
Rank dropped 19 spots (#1071 → #1090)
2026-08-26
Rank Moved
Rank dropped 87 spots (#984 → #1071)
2026-08-25
Rank Moved
Rank dropped 27 spots (#957 → #984)
2026-08-24
Rank Moved
Rank dropped 23 spots (#934 → #957)
2026-08-17
Rank Moved
Rank rose 18 spots (#956 → #938)
2026-08-16
Rank Moved
Rank dropped 26 spots (#930 → #956)
2026-08-13
Rank Moved
Rank dropped 10 spots (#918 → #928)
2026-08-12
Rank Moved
Rank rose 13 spots (#931 → #918)
2026-08-10
Rank Moved
Rank dropped 48 spots (#878 → #926)
2026-08-08
Newly Listed
First tracked at rank #871
GitHub → Website → npm: agent-search-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 55.0 Grade C
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) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON