updated 2026-11-11 00:08 UTC

idealo MCP Server

Repository Website

Search products, compare prices, and discover deals across 6 European markets (DE, UK, FR, IT, ES, AT) directly from your AI assistant.

MCP Servers Listed MIT

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

OSSF Scorecard 4.2 / 10
Provenance None
Signed commits 100%
Last push 175d ago
Compare idealo MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: idealo MCP Server scores 38.8/100 (Grade D), ranked #1234 of 1387 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 4.2/10; 100% of recent commits are signed; last pushed 2026-05-20. Every point is earned from checkable signals — never paid placement. How scoring works →

How idealo MCP Server 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 idealo MCP Server 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.

  1. Source Signed

    github.com/idealo/mcp-server-guide, MIT, last pushed 2026-05-20. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.2/10 (scanned Nov 7, 2026). The checks that decide who can get a change released:

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

  3. Published packages None

    No registry package. idealo MCP Server is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-09-02 OSSF Scorecard: 4.2/10

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 idealo MCP Server’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 idealo MCP Server compares in MCP Servers

  1. #708 Terminal MCP Server 39.0 +0.2
  2. #709 Nslookup MCP 38.9 +0.1
  3. #710 idealo MCP Server 38.8 this agent
  4. #711 Augments MCP Server 38.8 ±0
  5. #712 PostgreSQL performance Tuner MCP Server 38.6 −0.2

Bars show each HVTrust score; the tick marks idealo MCP Server’s 38.8.

Where the 38.8 comes from

HVTrust dimensions vs the MCP Servers average

38.8 / 100 · 100.0% confidence

idealo MCP Server MCP Servers average (779 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.2 / 25
0.6 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.1 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
0.3 / 20
12.0 below avg 12.3
AdoptionLog-scaled stars · package downloads
3.4 / 20
4.2 below avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.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.
Refresh maintenance signals The repo was last pushed 175 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View MCP Servers Report missing data
9.4
Activity sub-score · out of 100
#710
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 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 →

Signals refreshed 2026-11-11 00:08 UTC · Repo last pushed 175 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
26
Forks
0
Last Push
2026-05-20
175 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
1
Rank Change
▼1
was #1233

Analysis

Activity Inputs

9.4 / 100
StarsRepository reach
8.6 / 30
FreshnessLast push recency
0.7 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
0.0 / 20

Common questions about idealo MCP Server

Public trust evidence for idealo MCP Server 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 idealo MCP Server publish package provenance?
No published build provenance is currently detected for idealo MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does idealo MCP Server have an OpenSSF Scorecard?
idealo MCP Server has an OpenSSF Scorecard score of 4.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 idealo MCP Server actively maintained?
Slowing down. Last push was 175 days ago — keep an eye on whether activity resumes.
What license does idealo MCP Server use?
idealo MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are idealo MCP Server's commits signed?
100% of the last 100 commits to idealo MCP Server 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
medium confidence
Implemented
idealo MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
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
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 idealo MCP Server'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
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-08-18
Activity Went Stale
No commits for 90 days

Maintain idealo MCP Server?

For maintainers

HVTrust scores idealo MCP Server 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 18HVTrust 2Stale 1Scorecard 1Delisted 1Listed 1MCP 1
2026-10-09
Rank Moved
Rank dropped 11 spots (#1165 → #1176)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 217 spots (#912 → #1129)
2026-09-23
HVTrust Changed
HVTrust up 15.3pts (26.5 → 41.8)
2026-09-22
Newly Listed
First tracked at rank #912
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-12
Rank Moved
Rank dropped 15 spots (#1101 → #1116)
2026-09-09
Rank Moved
Rank dropped 14 spots (#1083 → #1097)
2026-09-08
Rank Moved
Rank dropped 10 spots (#1073 → #1083)
2026-09-07
Rank Moved
Rank dropped 29 spots (#1044 → #1073)
2026-09-06
Rank Moved
Rank dropped 15 spots (#1029 → #1044)
2026-09-05
Rank Moved
Rank dropped 42 spots (#987 → #1029)
2026-09-04
Rank Moved
Rank dropped 23 spots (#964 → #987)
2026-09-03
Rank Moved
Rank dropped 62 spots (#902 → #964)
2026-09-02
Scorecard Added
OSSF Scorecard: 4.2/10
2026-09-02
Rank Moved
Rank rose 377 spots (#1279 → #902)
2026-09-02
HVTrust Changed
HVTrust up 24.9pts (18.1 → 43.0)
2026-08-31
Rank Moved
Rank dropped 12 spots (#1259 → #1271)
2026-08-30
Rank Moved
Rank dropped 14 spots (#1245 → #1259)
2026-08-29
Rank Moved
Rank dropped 16 spots (#1229 → #1245)
2026-08-28
Rank Moved
Rank dropped 14 spots (#1215 → #1229)
2026-08-27
Rank Moved
Rank dropped 15 spots (#1200 → #1215)
2026-08-26
Rank Moved
Rank dropped 42 spots (#1158 → #1200)
2026-08-18
Activity Went Stale
No commits for 90 days
2026-08-16
Rank Moved
Rank dropped 28 spots (#1126 → #1154)
GitHub → Website →

Embed Badge Badge guide for maintainers →

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