Web Scout MCP
An MCP server providing web search and content extraction capabilities. Integrates DuckDuckGo search functionality and URL content extraction into your MCP environment, enabling AI assistants to search the web and extract webpage content.
Is Web Scout MCP safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Web Scout MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Web Scout MCP scores 45.9/100 (Grade D), ranked #1040 of 1325 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 3.2/10; 26% of recent commits are signed; last pushed 2026-09-19. Every point is earned from checkable signals — never paid placement. How scoring works →
How Web Scout MCP compares in MCP Servers
- #607 Godot MCP 46.0 +0.1
- #608 FocusRelay 45.9 ±0
- #609 Web Scout MCP 45.9 this agent
- #610 Vidlens MCP 45.9 ±0
- #611 KDAN PDF 45.7 −0.2
Bars show each HVTrust score; the tick marks Web Scout MCP’s 45.9.
Where the 45.9 comes from
HVTrust dimensions vs the MCP Servers average
45.9 / 100 · 100.0% confidenceWeb Scout MCP MCP Servers average (775 agents)
Quick Trust Read
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 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
Activity & Reach
Analysis
Activity Inputs
42.8 / 100Supply Chain Trust
Common questions about Web Scout MCP
Does Web Scout MCP publish package provenance?
Does Web Scout MCP have an OpenSSF Scorecard?
Is Web Scout MCP actively maintained?
What license does Web Scout MCP use?
Are Web Scout MCP's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Web Scout 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.
Maintain Web Scout MCP?
For maintainers
HVTrust scores Web Scout 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
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/web-scout-mcp)
<a href="https://hvtracker.net/agents/web-scout-mcp"><img src="https://hvtracker.net/badge/web-scout-mcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
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