updated 2026-11-10 04:07 UTC

A2asearch MCP

Repository

MCP server for searching AI agents, MCP servers, CLI tools and agent skills via A2ASearch

MCP Servers JavaScript Listed MIT

Is A2asearch MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.9 / 10
Provenance None
Signed commits 4%
Last push 14d ago
Advisories None known
Compare A2asearch MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: A2asearch MCP scores 54.0/100 (Grade C), ranked #880 of 1374 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 4.9/10; 4% of recent commits are signed; no published advisory affects its latest release (a2asearch-mcp); last pushed 2026-10-27. Every point is earned from checkable signals — never paid placement. How scoring works →

How A2asearch 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 A2asearch 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/tadas-github/a2asearch-mcp, MIT, last pushed 2026-10-27. 4% 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 4.9/10 (scanned Oct 14, 2026, refresh pending). The checks that decide who can get a change released:

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

  3. Published packages Linked, not attested

    • npm a2asearch-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: a2asearch-mcp 1.1.6. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-08-30 OSSF Scorecard: 1.4/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 A2asearch 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 A2asearch MCP compares in MCP Servers

  1. #484 Fanout MCP 54.3 +0.3
  2. #485 Plumb MCP 54.1 +0.1
  3. #486 A2asearch MCP 54.0 this agent
  4. #487 JS Reverse MCP 54.0 ±0
  5. #488 RPG Maker MV Ultimate MCP 54.0 ±0

Bars show each HVTrust score; the tick marks A2asearch MCP’s 54.0.

Where the 54.0 comes from

HVTrust dimensions vs the MCP Servers average

54.0 / 100 · 100.0% confidence

A2asearch MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.3 / 25
4.5 below avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
12.7 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
13.0 / 20
0.8 above avg 12.2
AdoptionLog-scaled stars · package downloads
6.2 / 20
1.4 below avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-04
Rank Moved
Rank rose 39 spots (#911 → #872)
2026-10-27
Rank Moved
Rank rose 37 spots (#925 → #888)
2026-10-22
Rank Moved
Rank dropped 45 spots (#872 → #917)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.9/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
View MCP Servers Report missing data
37.2
Activity sub-score · out of 100
#486
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-11-10 04:07 UTC · Repo last pushed 14 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
21
Forks
0
Last Push
2026-10-27
14 days ago
Commits (4 wk)
2
Downloads (7d)
172
npm
HN mentions (30d)
—
Open Issues
2
Rank Change
▲1
was #881

Analysis

Activity Inputs

37.2 / 100
StarsRepository reach
8.1 / 30
FreshnessLast push recency
23.1 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
0.0 / 20

Common questions about A2asearch MCP

Public trust evidence for A2asearch 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 A2asearch MCP publish package provenance?
No published build provenance is currently detected for A2asearch 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 A2asearch MCP have an OpenSSF Scorecard?
A2asearch MCP has an OpenSSF Scorecard score of 4.9/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 A2asearch MCP actively maintained?
Maintained. Last push was 14 days ago.
What license does A2asearch MCP use?
A2asearch MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are A2asearch MCP's commits signed?
3% of the last 100 commits to A2asearch 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
A2asearch MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency 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 A2asearch 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-10-13
Activity Resumed
Activity resumed
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain A2asearch MCP?

For maintainers

HVTrust scores A2asearch 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 23HVTrust 5Scorecard 1Delisted 1Listed 1MCP 1Score 1Fresh 1Grade 1
2026-11-04
Rank Moved
Rank rose 39 spots (#911 → #872)
2026-10-27
Rank Moved
Rank rose 37 spots (#925 → #888)
2026-10-22
Rank Moved
Rank dropped 45 spots (#872 → #917)
2026-10-21
Rank Moved
Rank rose 17 spots (#889 → #872)
2026-10-18
Rank Moved
Rank dropped 11 spots (#885 → #896)
2026-10-14
Grade Changed
Trust grade D → C
2026-10-14
Rank Moved
Rank rose 200 spots (#1064 → #864)
2026-10-14
HVTrust Changed
HVTrust up 6.8pts (47.1 → 53.9)
2026-10-13
Activity Resumed
Activity resumed
2026-10-13
Rank Moved
Rank rose 231 spots (#1295 → #1064)
2026-10-13
HVTrust Changed
HVTrust up 13.2pts (33.9 → 47.1)
2026-10-13
Activity Score Changed
Activity score up 29pts (8 → 37)
2026-10-09
Rank Moved
Rank dropped 11 spots (#1273 → #1284)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 62 spots (#1318 → #1256)
2026-09-23
HVTrust Changed
HVTrust up 22.3pts (11.5 → 33.8)
2026-09-22
Newly Listed
First tracked at rank #1318
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Rank Moved
Rank rose 26 spots (#1252 → #1226)
2026-09-09
Rank Moved
Rank dropped 10 spots (#1222 → #1232)
2026-09-08
Rank Moved
Rank dropped 13 spots (#1209 → #1222)
2026-09-07
Rank Moved
Rank dropped 24 spots (#1185 → #1209)
2026-09-06
Rank Moved
Rank dropped 19 spots (#1166 → #1185)
2026-09-05
Rank Moved
Rank dropped 31 spots (#1135 → #1166)
2026-09-04
Rank Moved
Rank dropped 16 spots (#1119 → #1135)
2026-09-03
Rank Moved
Rank rose 100 spots (#1219 → #1119)
2026-09-03
HVTrust Changed
HVTrust up 11.6pts (24.0 → 35.6)
2026-09-02
Rank Moved
Rank dropped 33 spots (#1186 → #1219)
2026-09-01
Rank Moved
Rank dropped 41 spots (#1145 → #1186)
2026-08-31
Rank Moved
Rank dropped 31 spots (#1114 → #1145)
2026-08-30
Scorecard Added
OSSF Scorecard: 1.4/10
2026-08-30
Rank Moved
Rank rose 175 spots (#1289 → #1114)
2026-08-30
HVTrust Changed
HVTrust up 8.3pts (15.8 → 24.1)
2026-08-26
Rank Moved
Rank dropped 21 spots (#1250 → #1271)
2026-08-16
Rank Moved
Rank dropped 24 spots (#1219 → #1243)
GitHub → npm: a2asearch-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 54.0 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/a2asearch-mcp.svg)](https://hvtracker.net/agents/a2asearch-mcp)
HTML:
<a href="https://hvtracker.net/agents/a2asearch-mcp"><img src="https://hvtracker.net/badge/a2asearch-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