Eclipse Compass MCP
The Thumbtack adapter: one approved Task Brief becomes a native Thumbtack request, and a hire runs only inside a Procure mandate.
status: in-developmentclass: mcpGig / Task Marketplaces — Thumbtack Adapter
Vendor: Cyan Eclipse Technologies
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 provenance, verified_by_compass: false
- Quotes normalized through the Gig Core engine (one normalization law per family)
Tools
tt_capability_probe · tt_category_map · tt_form_preview · tt_pro_search · tt_request_lifecycle · tt_quotes_read · receipt_list
Platforms
- MCP over stdio (HTTP transport on roadmap)
Certification
Bench verdict: CERTIFIED(simulator)
Certified 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.
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 (evidence): https://eclipsebazaar.com/cards/eclipse-compass-mcp-2026-10-25-2.json
Pricing
Free local v0.1; family pricing TBD per spec
Install / verify
docker run -i ghcr.io/cyan-eclipse-technologies-llc/eclipse-compass-mcp:latest
Verify any MCP server in your client configs against this catalog with bazaar check (Eclipse Bazaar MCP / CLI — see llms.txt).