Is SearXNG HTTP MCP safe to use?

SearXNG HTTP MCP has an HVTrust score of 53.0/100 (Grade C), ranked #429 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for SearXNG HTTP MCP?

SearXNG HTTP MCP scores 53.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 10 GitHub stars and is categorized under MCP Servers.

SearXNG HTTP MCP

whw23/searxng_http_mcp

A zero-install, cloud-hosted SearXNG MCP server over HTTP — no local runtime required.

MCP Servers Python Grade C Listed MIT

53.0/100

Rank #429 of 1283

Compare SearXNG HTTP 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 C · 2/5 signals

Last push

2026-08-08 · 4d ago

Recent change

Rank +1

Is SearXNG HTTP MCP safe? SearXNG HTTP MCP scores 53.0/100 (Grade C), ranked #429 of 1283 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 6/10; 65% of recent commits are signed; last pushed 2026-08-08. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#143 Elasticsearch MCP Server — 53.4 (C) → #144 AirMCP — 53.2 (C) → #146 Scrivener MCP — 52.8 (C) → #147 MCP Sap Gui — 52.1 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-10

Rank Moved

Rank dropped 17 spots (#410 → #427)

2026-08-08

Newly Listed

First tracked at rank #408

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.0/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.

Compare with another agent Get email alerts for SearXNG HTTP MCP View MCP Servers Report missing data

50.3

Activity sub-score · out of 100

#145

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-08-11 2026-08-12

Activity & Reach

Stars

Forks

Last Push

2026-08-08

4 days ago

Commits (4 wk)

27?

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #429

Analysis

HVTrust Dimensions vs MCP Servers

53.0 / 100 · 100.0% confidence

SearXNG HTTP MCP MCP Servers average (761 agents)

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

10.8 / 25

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

13.6 / 17

4.8 above avg 8.8

Maintenance60% last-push freshness · 40% commit activity

14.6 / 20

2.2 above avg 12.4

AdoptionLog-scaled stars · package downloads

2.5 / 20

3.3 below avg 5.8

Activity Inputs

50.3 / 100

StarsRepository reach

6.2 / 30

FreshnessLast push recency

24.4 / 25

ActivityRecent commits

18.1 / 25

CommunityFork signal

1.4 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.0 / 10

OpenSSF Scorecard · scanned Aug 8, 2026

Signed Commits

65%

of last 100 commits verified

Code-Review 0

Binary-Artifacts 10

Security-Policy 10

Maintained 0

Dependency-Update-Tool 10

Dangerous-Workflow 0

Token-Permissions 10

Pinned-Dependencies 10

CII-Best-Practices 5

Vulnerabilities 9

License 10

Packaging 10

Branch-Protection 4

Signed-Releases -1

SAST 10

Fuzzing 0

Contributors 0

CI-Tests 10

Is SearXNG HTTP MCP safe?

Public trust evidence for SearXNG HTTP 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 SearXNG HTTP MCP publish package provenance?

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

SearXNG HTTP MCP has an OpenSSF Scorecard score of 6/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 SearXNG HTTP MCP actively maintained?

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

What license does SearXNG HTTP MCP use?

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

Are SearXNG HTTP MCP's commits signed?

65% of the last 100 commits to SearXNG HTTP 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

SearXNG HTTP 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.

Anthropic

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

Maintain SearXNG HTTP MCP?

For maintainers

HVTrust scores SearXNG HTTP 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-08-10

Rank Moved

Rank dropped 17 spots (#410 → #427)

2026-08-08

Newly Listed

First tracked at rank #408

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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