Eclipse Bazaar MCP

Name: Eclipse Bazaar MCP
Author: CYAN-ECLIPSE-TECHNOLOGIES-LLC

Local

eclipsebazaar.comDeveloper Tools0Updated 2d ago

Repository Visit website

About Eclipse Bazaar MCP

Eclipse Bazaar MCP lets agents search a tested MCP marketplace by problem or keyword and inspect product records. Its distinguishing feature is that each listing reports its Test Bench verdict, certified scope, and untested areas, or explicitly says no verdict exists.

Key features

01Problem-based solution matching
02Ranked keyword search with match reasons
03Product details and comparisons
04Test Bench verdict and scope lookup
05Category counts and catalog freshness

Use cases

01Find tools for a stated problem
02Compare products and certification status
03Check what a bench verdict covers
04Review configured MCP server identities with bazaar check

MCP support

It exposes catalog search, product, comparison, certification, and category tools to MCP clients. The accompanying bazaar CLI can also classify configured MCP servers against the catalog.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config

{
  "mcpServers": {
    "cyan-eclipse-technologies-llc-bazaar": {
      "command": "uvx",
      "args": [
        "eclipse-bazaar"
      ],
      "env": {
        "BAZAAR_CATALOG": "<BAZAAR_CATALOG>"
      }
    }
  }
}

Run commanduvx eclipse-bazaar

Environment variables to set

BAZAAR_CATALOGPath to the catalog JSON the server reads. Defaults to the catalog.json bundled beside the server.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages

ocighcr.io/cyan-eclipse-technologies-llc/bazaar-mcp:0b0883a4d28e925063a4665430e6a5401da15c20stdio

pypieclipse-bazaar0.1.1stdio

Tools

Saved tool list · updated 2d ago

Parameter	Type	Required	Description
query	string	Yes
category	string	No

Details

From the project README

Eclipse Bazaar MCP

Powered by Cyan Eclipse Technologies — https://cetech.ai The agent-facing discovery layer for Eclipse Bazaar (eclipsebazaar.com) — CETech's tested MCP marketplace.

Why this exists

Agents shop by problem, not by product name. A registry listing tells an agent that a server exists; it does not say what problem the tool solves, whether anyone tested it, or what was not tested. Eclipse Bazaar's differentiator is exactly that honesty layer — every listing carries its Test Bench verdict, its certified scope, and its not-tested list, or states plainly that no verdict exists yet.

This MCP server is how agents query that catalog:

By problem — find_solutions matches a plain-language problem against problem statements + capabilities and explains the fit, with status and certification badges inline.
By keyword — search_products ranks across names, capabilities, and categories, and every hit carries match_reasons[]: the ranking is never a black box.
With receipts — get_certification returns the latest Test Bench verdict plus a live summary of the underlying scorecard (check counts, environment, date), the certified scope, and the not_tested list.
Honestly labelled — spec-stage products are status: spec and certified: false; products whose bench run is pending say "not yet certified"; The White Report MCP's verdict is CERTIFIED(live) — the 2026-10-25 live-host bench (card -11) superseded its earlier logic-level PARTIAL, and every surface is kept in sync from the newest scorecard by sync_verdicts.py.

Tools (6)

Tool	What it does
`search_products(query, category?)`	Ranked keyword search; every hit carries `match_reasons[]`.
`find_solutions(problem)`	Problem-first matching with fit explanation + status/certification badges.
`get_product(id)`	Full entry incl. certification block and what was NOT tested.
`compare_products(ids[])`	Side-by-side: status, pricing model, certification, platforms.
`get_certification(id)`	Latest bench verdict + scorecard summary + scope + not_tested; explicit "NOT YET CERTIFIED" when none exists.
`list_categories()`	Categories with counts by status.

Every response includes a data_freshness note (catalog build date + source references). Scorecard summaries are read live from ../test-bench/results/ at call time.

Catalog (v0.1.0 — 64 products, CETech only)

Seeded only from real sources — each product's bazaar-manifest.json, the latest Test Bench scorecard, the MCP product slate, and the Eclipse Mail spec. No invented products, no invented verdicts.

Product	Status	Bench verdict
Eclipse Agent Wallet MCP	in-development	CERTIFIED(sandbox)
CertBridge MCP	in-development	CERTIFIED(staging)
HostBridge MCP	in-development	CERTIFIED(simulator)
Eclipse Connect	dogfood	CERTIFIED(dogfood)
The White Report MCP	live	CERTIFIED(live)
Eclipse Apply MCP	in-development	CERTIFIED(sandbox)
Eclipse Herald MCP	in-development	CERTIFIED(local)
Eclipse Beacon MCP	in-development	CERTIFIED(local)
Eclipse Cluster MCP	in-development	CERTIFIED(simulator)
Eclipse Thread MCP	in-development	CERTIFIED(simulator)
Eclipse Constellation MCP	in-development	CERTIFIED(local)
Eclipse Deep Field MCP	in-development	CERTIFIED(local)
Eclipse Pantry MCP	in-development	CERTIFIED(simulator)
Eclipse Marquee MCP	in-development	CERTIFIED(simulator)
Eclipse Dispatch MCP	in-development	CERTIFIED(local)
Eclipse Social Core MCP	in-development	CERTIFIED(local)
Eclipse Aperture MCP	in-development	CERTIFIED(local)
Eclipse Zephyr MCP	in-development	CERTIFIED(live-read)
Eclipse Environment MCP	in-development	CERTIFIED(simulator)
Eclipse Procure MCP	in-development	CERTIFIED(simulator)
Eclipse Gig Core MCP	in-development	CERTIFIED(local)
Eclipse Compass MCP	in-development	CERTIFIED(simulator)
Eclipse Stage MCP	in-development	CERTIFIED(simulator)
Eclipse Zenith MCP	in-development	CERTIFIED(simulator)
Eclipse Muster MCP	in-development	CERTIFIED(local)
Eclipse Haven MCP	in-development	CERTIFIED(simulator)
Eclipse Orbit MCP	in-development	CERTIFIED(simulator)
Eclipse Voice Core MCP	in-development	CERTIFIED(local)
Eclipse Trunk MCP	in-development	CERTIFIED(simulator)
Eclipse Connect MCP	dogfood	CERTIFIED(dogfood-facade)
Eclipse Connect · Beyond Compare MCP	in-development	CERTIFIED(simulated)
AgentReady MCP	in-development	CERTIFIED(local)
Florida Bid Intel MCP	in-development	CERTIFIED(local)
Eclipse Bazaar MCP (this server)	in-development	CERTIFIED(local)
Eclipse Envoy MCP	in-development	CERTIFIED(local)
Eclipse Fathom MCP	in-development	CERTIFIED(local)
Eclipse Codex MCP	in-development	CERTIFIED(local)
Eclipse Ledger MCP	in-development	CERTIFIED(local)
Eclipse Till MCP	in-development	CERTIFIED(local) · Ads Rail P1 extension CERTIFIED(local/simulator), Stripe test mode only — NOT PROVEN IN STRIPE
Eclipse Book MCP	in-development	CERTIFIED(local)
Eclipse Forecast MCP	in-development	CERTIFIED(local)
Eclipse Strike MCP	in-development	CERTIFIED(local)
Eclipse Meter MCP	in-development	CERTIFIED(local)
Eclipse Tripwire MCP	in-development	CERTIFIED(local)
Eclipse Umbra MCP	in-development	CERTIFIED(local)
Eclipse Blackbox MCP	in-development	CERTIFIED(local)
Eclipse Docket MCP	in-development	CERTIFIED(local)
Eclipse Countermark MCP	in-development	CERTIFIED(local)
Eclipse Census MCP	in-development	CERTIFIED(local)
Eclipse Crosswalk MCP	in-development	CERTIFIED(local)
Eclipse Redteam MCP	in-development	CERTIFIED(local)
Eclipse Span MCP	in-development	CERTIFIED(local)
Eclipse Airtime MCP	in-development	CERTIFIED(local/simulator)
Eclipse Friction MCP	in-development	CERTIFIED(local)
Eclipse Test Bench	in-development	not certified — in-house artifact, productization in progress (slate T1)
Eclipse Stocktake	in-development	not certified — in-house artifact, productization in progress (slate T4)
Eclipse Press	in-development	not certified — in-house artifact, productization in progress (slate T3)
Herald Card Kit	in-development	not certified — in-house artifact, productization in progress (slate T7)
Eclipse BidMatrix MCP	in-development	CERTIFIED(local)
Section 508 Evidence MCP	in-development	CERTIFIED(local)
FedScope MCP	in-development	CERTIFIED(local)
Eclipse Health Check MCP	in-development	CERTIFIED(local)
Eclipse Legacy Recon MCP	in-development	CERTIFIED(local) — at the NARROWED OBSERVED SCOPE (CLAIM-SCOPE.md), scoped re-bench card -11 (30/30 checks); cards -1..-10 retained append-only (card -10 FAILED at the former universal claim)
Eclipse Steward MCP	in-development	CERTIFIED(local)
Eclipse Mail MCP	in-development	CERTIFIED(local / fixture-only)
Eclipse Proof MCP	in-development	CERTIFIED(local)
Eclipse Charter MCP	in-development	CERTIFIED(local)
Eclipse Colophon MCP	in-development	CERTIFIED(local/simulator)
Eclipse Tether MCP	in-development	CERTIFIED(simulator)
Eclipse Proving MCP	in-development	CERTIFIED(simulator)
Eclipse Wageward MCP	in-development	CERTIFIED(local)
Eclipse Covenant MCP	in-development	CERTIFIED(local/simulator)
Eclipse Meridian MCP	in-development	CERTIFIED(local, synthetic scope)
Eclipse Consent MCP	in-development	CERTIFIED(local)
Eclipse Lineage MCP	in-development	CERTIFIED(local)
Eclipse Attest MCP	in-development	CERTIFIED(local)
Eclipse Revoke MCP	in-development	CERTIFIED(local)
Eclipse Keyhold MCP	in-development	CERTIFIED(local)
Eclipse Loft MCP	in-development	CERTIFIED(simulator)
Eclipse Corona MCP	in-development	CERTIFIED(local)
Eclipse Crosslist MCP	in-development	CERTIFIED(split per facet)
Eclipse Verbatim MCP	in-development	CERTIFIED(local)
Eclipse Roll MCP	in-development	CERTIFIED(local)
Eclipse Verbatim — Executive Orders	in-development	CERTIFIED(local)
Eclipse Flood Witness	in-development	CERTIFIED(local)
Eclipse Recall Witness	in-development	CERTIFIED(local)

The `bazaar` CLI — including `bazaar check`

$ bazaar search "certificate renewal"
$ bazaar product certbridge-mcp
$ bazaar categories
$ bazaar check            # classify your configured MCP servers

bazaar check reads your MCP client configs, extracts each configured server's identity (package / image / URL / local path), and joins it locally against the published Bazaar corpus — downloaded whole and verified against its sha256 manifest first. Each entry is classified CERTIFIED (listed, Tier-2 verdict on record), LISTED (in the catalog, no verdict yet), NOT LISTED (no record — a neutral fact), or UNRESOLVABLE (no identity could be extracted, with the reason). Version pins that differ from the listed version are flagged as drift.

Privacy, by construction: config env values are never read, copied, hashed, logged, or transmitted — the parser redacts them structurally before anything else runs. There is no telemetry. The check never executes a configured server and never contacts one. (The CLI ships in the eclipse-bazaar PyPI distribution alongside the MCP server above.)

Run it

python3 server.py        # MCP over stdio, stdlib only, no dependencies
python3 smoke_test.py    # protocol + routing + honesty assertions (9 checks)

Catalog lives in catalog.json beside the server (override with $BAZAAR_CATALOG).

Verdict sync (EB-09)

Bench verdicts have ONE source of truth: the newest scorecard per tool in ../test-bench/results/ (run-sequence suffix decides — a -11 card supersedes -2). python3 sync_verdicts.py rebuilds verdict-ledger.json and checks catalog.json, product bazaar-manifest.json files, this README's table, and the storefront bench lines against it (exit 1 on drift); --apply fixes the machine-safe fields. Dogfood logs annotate live state only — they never change a bench verdict. Run it after every bench run.

Scope & roadmap

v0.1.0 (this): CETech catalog only, discovery only. No purchasing.
P2: third-party listings (the vendor catalog opens; listings pass the Test Bench gate before they can carry a badge).
Future purchase hooks (noted, not built): x402 pay-per-call for paid tools, and an Agent Wallet policy check before any charge — an agent's granted spending scope governs Bazaar purchases the same way it governs everything else.

License / attribution

A Cyan Eclipse Technologies product. The "Powered by Cyan Eclipse Technologies" attribution travels with it.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

Read the getting-started guide

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.

Eclipse Bazaar MCP

About Eclipse Bazaar MCP

Key features

Use cases

MCP support

Configuration

Tools

Details

Eclipse Bazaar MCP

Why this exists

Tools (6)

Catalog (v0.1.0 — 64 products, CETech only)

The bazaar CLI — including bazaar check

Run it

Verdict sync (EB-09)

Scope & roadmap

License / attribution

Comments

New to MCP?

What is MCP (Model Context Protocol)?

How do MCP servers differ from clients?

Should I use a local or a remote server?

How do I install a server in Claude, Cursor and others?

Are listed projects reviewed? What does “Verified” mean?

My project is listed. How do I claim it?

The `bazaar` CLI — including `bazaar check`