Eclipse Gig Core MCP
PYPI · ECLIPSE-GIG-CORE
One approved Task Brief, every marketplace: hash-bound briefs, all-in quotes, and a hire that runs
Available components
Last scanned (19 hours ago)
Scores higher than 65% of PyPI servers
Category E-commerce
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 hatchling.build 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 & Transparency71
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-gig-core-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability56
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 987 tokens (~98/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 29 Oct 26 −5
- Source repository: pass → fail ▼ security
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 60
First indexed and scored.
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-gig-core@0.1.0
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/eclipse-gig-core-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-gig-core-mcp/.github/workflows/publish-pypi.yml@refs/tags/v0.1.0 |
| Rekor log index | 3518629798 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:8df53be43e1ffb049c43abd45dde2d95468e87086196ebb036099f5876f4bc5e |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
brief_approve ~77
Record the owner's approval of the EXACT current brief hash, plus the per-platform variant hashes approved with it. A hash mismatch is refused.
| Name | Type | Req | Description |
|---|---|---|---|
| approved_at | string | – | – |
| approver | string | – | – |
| brief_hash | string | yes | – |
| brief_id | string | yes | – |
| variant_hashes | object | – | – |
No output schema declared.
No examples provided.
brief_create ~200
Create a canonical Task Brief: category, service, scope {statement, items[]}, ZIP-tier location, timing window, ALL-IN ceiling, tip policy, photos (EXIF-strip status recorded per photo), license_required (unknown|no|yes:<type>), safety/access block, intended/prohibited platforms, and a details bag adapters draw native form answers from. Issues the version-1 hash an approval binds to.
| Name | Type | Req | Description |
|---|---|---|---|
| brief_id | string | – | – |
| category | string | yes | – |
| ceiling_all_in | number | yes | – |
| details | object | – | – |
| intended_platforms | array | – | – |
| license_required | string | yes | – |
| location | object | yes | – |
| photos | array | – | – |
| prohibited_platforms | array | – | – |
| safety_access | object | – | – |
| scope | object | yes | – |
| service | string | yes | – |
| timing | object | yes | – |
| tip_policy | object | – | – |
No output schema declared.
No examples provided.
brief_read ~29
Read a brief with its version, hash, and approval validity.
| Name | Type | Req | Description |
|---|---|---|---|
| brief_id | string | yes | – |
No output schema declared.
No examples provided.
brief_update ~59
Create a new brief version from content-field changes. Any post-approval edit invalidates the approval and returns the brief to draft (approval binds hashes, spec 5.1).
| Name | Type | Req | Description |
|---|---|---|---|
| brief_id | string | yes | – |
| changes | object | yes | – |
No output schema declared.
No examples provided.
completion_verify ~139
Verify completion against the brief's scope statement: each scope item done/partial/not_done with owner attestation. Platform state is stored verbatim and separately; a platform-completed claim the owner does not attest opens an exception record (spec 7.2).
| Name | Type | Req | Description |
|---|---|---|---|
| brief_id | string | yes | – |
| communication | string | – | – |
| platform | string | – | – |
| platform_state | string | – | – |
| pro_display_name | string | – | – |
| quality_notes | string | – | – |
| quote_id | string | – | – |
| scope_results | array | – | – |
| timeliness | string | – | – |
| verified_at | string | – | – |
No output schema declared.
No examples provided.
hire_check ~148
Evaluate a hire against a live Procure/Agent Wallet mandate: approved brief hash, mandate presence + expiry, cap vs all-in, brief ceiling, category + platform allowlists, approval threshold (above = owner token for THIS quote), quote expiry, fee exposure. v1 person-selection always needs an owner-confirm token. Returns ALLOW / MANDATE_ALLOW_PERSON_PENDING / DENY with named reasons. Executes nothing; receipted either way.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | – |
| brief_id | string | yes | – |
| mandate | object | – | – |
| person_confirm_token | string | – | – |
| quote_approval_token | string | – | – |
| quote_id | string | yes | – |
No output schema declared.
No examples provided.
quote_normalize ~196
Normalize a quote from any platform model (lead_model, stated_budget, fixed_price, hourly) into one record: face price, itemized fees with bearers, tax, and ALL-IN total kept separate forever. Fees the platform does not expose mark the quote UNEXPOSED with no all-in. Optional ceiling_all_in runs the ceiling test.
| Name | Type | Req | Description |
|---|---|---|---|
| ceiling_all_in | number | – | – |
| currency | string | – | – |
| fees | array | – | – |
| fees_exposed | boolean | – | – |
| hour_cap | number | – | – |
| hourly_rate | number | – | – |
| job_price | number | – | – |
| model | string | yes | – |
| owner_fee_exception | object | – | – |
| platform | string | yes | – |
| pro | object | yes | – |
| raw_quote_ref | string | – | – |
| tax | number | – | – |
| tip | object | – | – |
| valid_until | string | – | – |
No output schema declared.
No examples provided.
quote_read ~41
Read a normalized quote; optional ceiling_all_in re-runs the ceiling test.
| Name | Type | Req | Description |
|---|---|---|---|
| ceiling_all_in | number | – | – |
| quote_id | string | yes | – |
No output schema declared.
No examples provided.
receipt_list ~31
List the append-only, hash-chained gig-core receipts and verify the chain.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
review_draft ~67
Draft review text from a verification record ONLY: what was hired, what was verified, and timeliness/communication/quality strictly as recorded. No sentiment the record does not carry; leverage language is refused at draft time. The draft never submits itself.
| Name | Type | Req | Description |
|---|---|---|---|
| verification_id | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Eclipse Gig Core MCP server?
Eclipse Gig Core MCP runs locally as a PyPI package, launched with uvx eclipse-gig-core. 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-gig-core
claude mcp add cyan-eclipse-technologies-llc-gig-core -- uvx eclipse-gig-core
What is the Eclipse Gig Core MCP server?
Eclipse Gig Core MCP is listed in the public MCP registry as io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/gig-core. One approved Task Brief, every marketplace: hash-bound briefs, all-in quotes, and a hire that runs. This page covers its PyPI package (eclipse-gig-core).
Is the Eclipse Gig Core MCP server safe to use?
Eclipse Gig Core MCP scores 70 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 Gig Core MCP server expose?
Eclipse Gig Core MCP exposes 10 tools: brief_create, brief_update, brief_approve, brief_read, quote_normalize, and 5 more. Their descriptions and schemas cost roughly 987 tokens of context every time the server is loaded.
Is the Eclipse Gig Core MCP server still maintained?
Eclipse Gig Core 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 Gig Core MCP server under?
Eclipse Gig Core 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.