Is SearXNG HTTP MCP safe to use?

SearXNG HTTP MCP has an HVTrust score of 50.9/100 (Grade C), ranked #914 of 1325 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 50.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 11 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 Listed MIT

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

OSSF Scorecard 6.2 / 10

Provenance None

Signed commits 67%

Last push yesterday

Compare SearXNG HTTP MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: SearXNG HTTP MCP scores 50.9/100 (Grade C), ranked #914 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 6.2/10; 67% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How SearXNG HTTP MCP compares in MCP Servers

Bars show each HVTrust score; the tick marks SearXNG HTTP MCP’s 50.9.

Where the 50.9 comes from

HVTrust dimensions vs the MCP Servers average

50.9 / 100 · 100.0% confidence

SearXNG HTTP MCP MCP Servers average (775 agents)

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

11.1 / 25

0.8 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

13.8 / 17

1.6 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

11.9 / 20

in line with avg 12.1

AdoptionLog-scaled stars · package downloads

2.6 / 20

4.6 below avg 7.2

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintainer Checklist

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

32.9

Activity sub-score · out of 100

#520

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-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-25

yesterday

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #914

Analysis

Activity Inputs

32.9 / 100

StarsRepository reach

6.5 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

1.4 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.2 / 10

OpenSSF Scorecard · scanned Sep 24, 2026

Signed Commits

67%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 4

CI-Tests 10

CII-Best-Practices 5

Code-Review 1

Contributors 0

Dangerous-Workflow 0

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 10

SAST 9

Security-Policy 10

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 1

Common questions about SearXNG HTTP MCP

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.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 SearXNG HTTP MCP actively maintained?

Actively maintained. The repository was pushed to within the last 1 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?

67% 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

How this surface has changed

Detected changes to SearXNG HTTP 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

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

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-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

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 61 spots (#972 → #911)

2026-09-23

HVTrust Changed

HVTrust up 25.3pts (25.4 → 50.7)

2026-09-22

Newly Listed

First tracked at rank #972

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-17

Grade Changed

Trust grade D → C

2026-09-17

Rank Moved

Rank rose 340 spots (#1249 → #909)

2026-09-17

HVTrust Changed

HVTrust up 16.6pts (34.2 → 50.8)

2026-09-16

Grade Changed

Trust grade C → D

2026-09-16

Rank Moved

Rank dropped 345 spots (#904 → #1249)

2026-09-16

HVTrust Changed

HVTrust down 16.7pts (50.9 → 34.2)

2026-09-15

Rank Moved

Rank dropped 11 spots (#893 → #904)

2026-09-12

Rank Moved

Rank dropped 12 spots (#886 → #898)

2026-09-11

Grade Changed

Trust grade D → C

2026-09-11

Rank Moved

Rank rose 357 spots (#1243 → #886)

2026-09-11

HVTrust Changed

HVTrust up 16.9pts (34.3 → 51.2)

2026-09-10

Grade Changed

Trust grade C → D

2026-09-10

Rank Moved

Rank dropped 395 spots (#848 → #1243)

2026-09-10

HVTrust Changed

HVTrust down 17.7pts (52.0 → 34.3)

2026-09-09

Rank Moved

Rank dropped 15 spots (#833 → #848)

2026-09-08

Grade Changed

Trust grade D → C

2026-09-08

Rank Moved

Rank rose 381 spots (#1214 → #833)

2026-09-08

HVTrust Changed

HVTrust up 17.3pts (34.8 → 52.1)

2026-09-07

Grade Changed

Trust grade C → D

2026-09-07

Rank Moved

Rank dropped 589 spots (#625 → #1214)

2026-09-07

HVTrust Changed

HVTrust down 22.3pts (57.1 → 34.8)

2026-09-07

Activity Score Changed

Activity score down 16pts (48 → 32)

2026-09-06

Rank Moved

Rank dropped 15 spots (#610 → #625)

2026-09-05

Rank Moved

Rank dropped 76 spots (#534 → #610)

2026-09-04

Rank Moved

Rank dropped 13 spots (#521 → #534)

2026-09-03

Rank Moved

Rank rose 62 spots (#583 → #521)

2026-09-02

Rank Moved

Rank dropped 28 spots (#555 → #583)

2026-09-01

Rank Moved

Rank dropped 11 spots (#544 → #555)

2026-08-31

Rank Moved

Rank dropped 36 spots (#508 → #544)

2026-08-29

Rank Moved

Rank dropped 21 spots (#490 → #511)

2026-08-27

Rank Moved

Rank dropped 13 spots (#479 → #492)

2026-08-26

Rank Moved

Rank dropped 32 spots (#447 → #479)

2026-08-24

Rank Moved

Rank dropped 16 spots (#430 → #446)

2026-08-22

Rank Moved

Rank rose 15 spots (#448 → #433)

2026-08-19

Rank Moved

Rank dropped 13 spots (#434 → #447)

2026-08-17

Rank Moved

Rank rose 13 spots (#445 → #432)

2026-08-16

Rank Moved

Rank dropped 10 spots (#435 → #445)

2026-08-13

Rank Moved

Rank dropped 16 spots (#417 → #433)

2026-08-12

Rank Moved

Rank rose 12 spots (#429 → #417)

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