Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Eclipse Bazaar MCP

PYPI · ECLIPSE-BAZAAR · 2 COMPONENTS

Discover agent tools by problem: every listing carries its Test Bench verdict or says it has none.

+19 this week 80 Trust /100

Last scanned (1 day ago)

Scores higher than 80% of PyPI servers

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to CYAN-ECLIPSE-TECHNOLOGIES-LLC/bazaar-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 279 tokens (~46/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +3
    • Tool safety: pass → unverified ▼ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Stability: unverified → 0.17 ▲ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.1.1 → 0.1.4 functional
    • Package version: 0.1.1 → 0.1.3 functional
  • 29 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 27 Oct 26 61

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Analysed pypi/eclipse-bazaar@0.1.4

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo CYAN-ECLIPSE-TECHNOLOGIES-LLC/bazaar-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/bazaar-mcp/.github/workflows/publish-pypi.yml@refs/tags/v0.1.4
Rekor log index 3636325641
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:1e8f02c2fc3a65a54b414da44b0b9e9d9dcd9890ce21cab560094b4e9e56f4f8

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~279 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compare_products ~40

Side-by-side comparison of 2+ product ids: status, pricing model, certification verdict and scope, platforms, categories.

NameTypeReqDescription
idsarrayyes–

No output schema declared.

No examples provided.

find_solutions ~52

Describe a problem in plain language; get ranked products with a fit explanation, status, and certification badge inline. Spec-stage products are labelled spec-stage, uncertified products say so.

NameTypeReqDescription
problemstringyes–

No output schema declared.

No examples provided.

get_certification ~57

The latest Test Bench verdict for a product, with a live scorecard summary, the certified scope, and the not_tested list. Returns an explicit NOT YET CERTIFIED answer when no verdict exists.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_product ~45

Full catalog entry for one product id: capabilities, problem statements, pricing model, platforms, tools, and the certification block including what was NOT tested.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

list_categories ~29

All catalog categories with product counts broken down by status (live / dogfood / in-development / spec).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_products ~56

Keyword search over the Bazaar catalog (names, capabilities, categories, problem statements). Every hit carries match_reasons — why it matched is never hidden. Optional category filter.

NameTypeReqDescription
categorystring––
querystringyes–

No output schema declared.

No examples provided.

Install

How do I install the Eclipse Bazaar MCP server?

Eclipse Bazaar MCP runs locally as a PyPI package, launched with uvx eclipse-bazaar. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · eclipse-bazaar

# add to Claude Code
claude mcp add cyan-eclipse-technologies-llc-bazaar -- uvx eclipse-bazaar
Common questions

What is the Eclipse Bazaar MCP server?

Eclipse Bazaar MCP is listed in the public MCP registry as io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/bazaar. Discover agent tools by problem: every listing carries its Test Bench verdict or says it has none. This page covers its PyPI package (eclipse-bazaar).

Is the Eclipse Bazaar MCP server safe to use?

Eclipse Bazaar MCP scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Eclipse Bazaar MCP server expose?

Eclipse Bazaar MCP exposes 6 tools: search_products, find_solutions, get_product, compare_products, get_certification, list_categories. Their descriptions and schemas cost roughly 279 tokens of context every time the server is loaded.

Is the Eclipse Bazaar MCP server still maintained?

Eclipse Bazaar MCP is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Eclipse Bazaar MCP server under?

Eclipse Bazaar MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.