Vendor: Cyan Eclipse Technologies · Platforms: MCP over stdio (HTTP transport on roadmap)
Certification scope
CERTIFIED(simulator) — Eclipse Bazaar Test Bench 2026-10-25, 14/15 checks pass, 1 na (U1 auth: stdio process boundary). Run by W-003 (Verity), suites/compass.py. Run 1 (eclipse-compass-mcp-2026-10-25.json, FAILED, retained per append-only history) failed on a defect in the bench suite itself, not the product: its U3 network-surface pattern substring-matched the fixture filename 'thumbtack_requests.json'; the pattern was corrected and run 2 is the standing card.
What it does
- Explicit Thumbtack category mapping: an unknown category is a named error, never a silent nearest-match
- Native request-form previews built from the approved Task Brief, with every difference classified (CATEGORY_MAP, BUDGET_FORM, FEE_FORM, LICENSE_FIELD, FORMAT_OMISSION, LOCATION_PRECISION)
- Unanswered form fields surface as diffs — answers are never invented
- Licensed categories block until the brief declares its license posture
- Pro license claims surfaced verbatim with lineage, verified_by_compass: false
- Quotes normalized through the Gig Core engine (one normalization law per family)
Tools
tt_capability_probett_category_maptt_form_previewtt_pro_searchtt_request_lifecyclett_quotes_readreceipt_list
Problems it addresses
- I want a Thumbtack request built from my approved brief without re-typing it into their forms
- Fields my brief does not answer should be flagged, not invented
Not tested
- Live Thumbtack Partner Platform calls of any kind — no partner credentials exist (owner G1 step) and v0.1 contains no live code path; categories, pros, requests, and quotes are shipped fixtures shaped like Partner Platform responses.
- Live request submission (REQUEST_API) and hire execution (HIRE_API) — not built in v0.1; Compass previews and reads fixtures only, and holds no independent hire power (the gig core hire gate evaluates mandates).
- Marketplace-side messaging scope and the pro-side surface (leads, messages, webhooks) — later phases, messaging scope [verify] per spec chapter 10.
- Trademark screen for the 'Compass' name — owed before any external launch per spec chapter 10 (N5 caution).
Bench scorecard: test-bench/results/eclipse-compass-mcp-2026-10-25-2.json
Evaluation-intake listing
This listing records the tool's place in the Bazaar's evaluation
and monitoring pipeline, with the evidence gathered so far printed above — verdict, scope,
and not-tested items included. It is not sold on this site, and its presence in the catalog
is not a claim beyond that evidence. The service behind every verdict is the bench:
what a bench run buys →