Is Web Researcher MCP safe to use?

Web Researcher MCP has an HVTrust score of 64.7/100 (Grade C), ranked #543 of 1374 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Web Researcher MCP?

Web Researcher MCP scores 64.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 77 GitHub stars and is categorized under MCP Servers.

Web Researcher MCP

Repository

Website

Search the web and primary sources, read full pages, and check every citation. MCP server for Claude, Cursor, Codex and more. Runs on your machine.

MCP Servers Go Listed MIT

Is Web Researcher MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 8.2 / 10

Provenance None

Signed commits 69%

Last push today

Compare Web Researcher MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Web Researcher MCP scores 64.7/100 (Grade C), ranked #543 of 1374 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 8.2/10; 69% of recent commits are signed; last pushed 2026-11-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Web Researcher 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.

Raise the OSSF Scorecard from 8.2 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Branch-Protection 3 +1.6 → 66.3 B · #281 of 778
Sign every commit69% signed today +1.5 → 66.2 B · #283 of 778

Already done? Suggest a correction Add the trust badge

Chain of custody

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

Source Partly signed

github.com/zoharbabin/web-researcher-mcp, MIT, last pushed 2026-11-10. 69% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Strong

OpenSSF Scorecard rates the repository's practices 8.2/10 (scanned Nov 9, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection3
- Signed Releases8
- Dangerous Workflow10
- Token Permissions10
- Pinned Dependencies10
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 10

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 10

SAST 10

Security-Policy 10

Signed-Releases 8

Token-Permissions 10

Vulnerabilities 10
Published packages None

Distributed as the container image ghcr.io/zoharbabin/web-researcher-mcp:1.47.1; HVTracker doesn't check that registry's source link yet.

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Web Researcher MCP.

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Web Researcher 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 Web Researcher MCP compares in MCP Servers

Bars show each HVTrust score; the tick marks Web Researcher MCP’s 64.7.

Where the 64.7 comes from

HVTrust dimensions vs the MCP Servers average

64.7 / 100 · 100.0% confidence

Web Researcher MCP MCP Servers average (778 agents)

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

13.7 / 25

2.9 above 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

15.5 / 17

3.2 above avg 12.3

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

7.8 above avg 12.2

AdoptionLog-scaled stars · package downloads

4.5 / 20

3.1 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-08

Rank Moved

Rank rose 16 spots (#559 → #543)

2026-11-04

Rank Moved

Rank dropped 14 spots (#553 → #567)

2026-11-03

Rank Moved

Rank rose 14 spots (#567 → #553)

Maintainer Checklist

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent View MCP Servers Report missing data

67.1

Activity sub-score · out of 100

#309

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 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 →

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars

Forks

Last Push

2026-11-10

today

Commits (4 wk)

111

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼3

was #540

Analysis

Activity Inputs

67.1 / 100

StarsRepository reach

11.4 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

5.7 / 20

Common questions about Web Researcher MCP

Web Researcher 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 Web Researcher MCP publish package provenance?

No published build provenance is currently detected for Web Researcher 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 Web Researcher MCP have an OpenSSF Scorecard?

Web Researcher MCP has an OpenSSF Scorecard score of 8.2/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 Web Researcher MCP actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Web Researcher MCP use?

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

Are Web Researcher MCP's commits signed?

69% of the last 100 commits to Web Researcher 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

Web Researcher MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

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

How this surface has changed

Detected changes to Web Researcher 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-26

Provider Removed

Runtime surface shrank — no longer detected: Google Gemini

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini, Tavily

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Web Researcher MCP?

For maintainers

HVTrust scores Web Researcher 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

2026-11-08

Rank Moved

Rank rose 16 spots (#559 → #543)

2026-11-04

Rank Moved

Rank dropped 14 spots (#553 → #567)

2026-11-03

Rank Moved

Rank rose 14 spots (#567 → #553)

2026-10-31

Rank Moved

Rank dropped 15 spots (#545 → #560)

2026-10-29

Rank Moved

Rank dropped 14 spots (#533 → #547)

2026-10-26

Provider Removed

Runtime surface shrank — no longer detected: Google Gemini

2026-10-26

Rank Moved

Rank rose 23 spots (#551 → #528)

2026-10-21

Rank Moved

Rank rose 27 spots (#584 → #557)

2026-10-15

Rank Moved

Rank dropped 58 spots (#512 → #570)

2026-10-14

Rank Moved

Rank rose 13 spots (#525 → #512)

2026-10-13

Rank Moved

Rank rose 33 spots (#558 → #525)

2026-10-11

Rank Moved

Rank rose 66 spots (#620 → #554)

2026-10-09

Rank Moved

Rank dropped 12 spots (#605 → #617)

2026-10-08

Rank Moved

Rank dropped 11 spots (#594 → #605)

2026-10-02

Rank Moved

Rank dropped 15 spots (#560 → #575)

2026-10-01

Rank Moved

Rank dropped 26 spots (#534 → #560)

2026-09-28

Rank Moved

Rank rose 42 spots (#590 → #548)

2026-09-24

Rank Moved

Rank dropped 51 spots (#534 → #585)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini, 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 75 spots (#609 → #534)

2026-09-23

HVTrust Changed

HVTrust up 29.5pts (33.5 → 63.0)

2026-09-22

Newly Listed

First tracked at rank #609

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Grade Changed

Trust grade D → C

2026-09-20

Rank Moved

Rank rose 598 spots (#1128 → #530)

2026-09-20

HVTrust Changed

HVTrust up 21.0pts (41.8 → 62.8)

2026-09-19

Grade Changed

Trust grade C → D

2026-09-19

Rank Moved

Rank dropped 621 spots (#507 → #1128)

2026-09-19

HVTrust Changed

HVTrust down 21.6pts (63.4 → 41.8)

2026-09-18

Rank Moved

Rank dropped 27 spots (#480 → #507)

2026-09-17

Grade Changed

Trust grade D → C

2026-09-17

Rank Moved

Rank rose 621 spots (#1101 → #480)

2026-09-17

HVTrust Changed

HVTrust up 21.3pts (43.0 → 64.3)

2026-09-16

Grade Changed

Trust grade C → D

2026-09-16

Rank Moved

Rank dropped 632 spots (#469 → #1101)

2026-09-16

HVTrust Changed

HVTrust down 21.6pts (64.6 → 43.0)

2026-09-11

Grade Changed

Trust grade D → C

2026-09-11

Rank Moved

Rank rose 626 spots (#1094 → #468)

2026-09-11

HVTrust Changed

HVTrust up 21.6pts (42.9 → 64.5)

2026-09-10

Grade Changed

Trust grade C → D

2026-09-10

Rank Moved

Rank dropped 641 spots (#453 → #1094)

2026-09-10

HVTrust Changed

HVTrust down 21.7pts (64.6 → 42.9)

2026-09-08

Rank Moved

Rank dropped 10 spots (#440 → #450)

2026-09-07

Rank Moved

Rank dropped 21 spots (#419 → #440)

2026-09-06

Rank Moved

Rank dropped 21 spots (#398 → #419)

2026-09-05

Rank Moved

Rank dropped 66 spots (#332 → #398)

2026-09-04

Grade Changed

Trust grade B → C

2026-09-04

Rank Moved

Rank dropped 15 spots (#317 → #332)

2026-09-03

Grade Changed

Trust grade C → B

2026-09-03

Rank Moved

Rank rose 24 spots (#341 → #317)

2026-09-01

Rank Moved

Rank rose 84 spots (#416 → #332)

2026-09-01

HVTrust Changed

HVTrust up 4.2pts (59.6 → 63.8)

2026-08-31

Rank Moved

Rank dropped 28 spots (#388 → #416)

2026-08-30

Rank Moved

Rank rose 16 spots (#404 → #388)

2026-08-29

Rank Moved

Rank dropped 16 spots (#388 → #404)

2026-08-27

Rank Moved

Rank dropped 10 spots (#377 → #387)

2026-08-26

Rank Moved

Rank dropped 37 spots (#340 → #377)

2026-08-24

Rank Moved

Rank dropped 16 spots (#326 → #342)

2026-08-22

Rank Moved

Rank rose 18 spots (#344 → #326)

2026-08-19

Rank Moved

Rank dropped 15 spots (#328 → #343)

2026-08-17

Rank Moved

Rank rose 23 spots (#354 → #331)

2026-08-13

Rank Moved

Rank dropped 19 spots (#324 → #343)

GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/web-researcher-mcp.svg)](https://hvtracker.net/agents/web-researcher-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/web-researcher-mcp"><img src="https://hvtracker.net/badge/web-researcher-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.4 · Raw JSON

Web Researcher MCP

How Web Researcher MCP could raise its score

Chain of custody

Source Partly signed

Review and release Strong

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Web Researcher MCP compares in MCP Servers

Where the 64.7 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Web Researcher MCP

AI agent surface

Maintain Web Researcher MCP?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers