Skip to main content

eclipse-gig-core

mcp-name: io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/gig-core

What this is: the MCP server for Eclipse Gig Core — the shared core of Cyan Eclipse Technologies' Eclipse gig adapter family. One canonical, owner-approved Task Brief becomes a native request, offer round, booking, or prep pack on each task marketplace, according to what that platform actually sanctions.

What this is not: phase G0 is fixtures and evaluation only. No live platform call exists in this code, no hire is executed, no review is submitted, and no payment moves. Hiring happens only inside an Eclipse Procure / Agent Wallet mandate, evaluated — never executed — by this core.

Run it

$ pip install eclipse-gig-core
$ eclipse-gig-core           # MCP over stdio, Python stdlib only

MCP client config:

{ "mcpServers": { "eclipse-gig-core": { "command": "uvx", "args": ["eclipse-gig-core"] } } }

Tools (10)

brief_create · brief_update · brief_approve · brief_read · quote_normalize · quote_read · hire_check · completion_verify · review_draft · receipt_list

Honest scope

  • The Task Brief is versioned and SHA-256 hash-bound; any post-approval edit invalidates the approval. Quotes normalize every platform model (lead, stated-budget, fixed-price, hourly) to face price and itemized fees — forever separate — plus one all-in total; a quote whose fees are unexposed cannot be hireable under a ceiling.
  • The hire gate returns ALLOW / DENY with named reasons, receipted either way; in v1, selecting a person requires an owner-confirm token even when a mandate allows the money.
  • State persists in data/state.json beside the server (override with ECLIPSE_GIG_CORE_STATE).
  • Certified (local) by the Eclipse Test Bench at v0.1.0; the listing status in the Eclipse Bazaar catalog is in-development.

Powered by Cyan Eclipse Technologies LLC (cetech.ai) — a Veteran-Owned Small Business. MIT licensed.

Metadata

Release files for eclipse-gig-core 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for eclipse-gig-core 0.1.0
File Size Uploaded Provenance
eclipse_gig_core-0.1.0.tar.gz 34.6 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for eclipse-gig-core 0.1.0
File Interpreter ABI Platform
eclipse_gig_core-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 50.2 kB

Release files / eclipse_gig_core-0.1.0.tar.gz

Download URL eclipse_gig_core-0.1.0.tar.gz
Size 34.6 kB
Tags Source
SHA-256 checksum
How to use checksums
8df53be43e1ffb049c43abd45dde2d95468e87086196ebb036099f5876f4bc5e
BLAKE2b-256 checksum
How to use checksums
495f595968d7f6ebfd49d29d4d172d90b15f1a7e9a9a211148e2713ec2ee8ad1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

Release files / eclipse_gig_core-0.1.0-py3-none-any.whl

Download URL eclipse_gig_core-0.1.0-py3-none-any.whl
Size 15.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a7b49c89b46cc2bcb702dae8ddf679e77994efa0a2340633af562dd6eaa01b4b
BLAKE2b-256 checksum
How to use checksums
f3df1069e37982a2920f9ff35abb4caaf4d766ef8ef23724831fe36dcbb3727e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

Security for eclipse-gig-core 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for eclipse_gig_core-0.1.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page