# 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

- Trust score: 70/100 (medium)
- Change this week: −5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- pypi · `eclipse-gig-core`: 70/100 (this document), [markdown](https://verifymcp.io/servers/cyan-eclipse-technologies-llc-gig-core/eclipse-gig-core.md), [page](https://verifymcp.io/servers/cyan-eclipse-technologies-llc-gig-core/eclipse-gig-core)

## Channel facts

- Registry: `pypi`
- Package: `eclipse-gig-core`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 71/100
  - Repository check failed: the declared repository URL redirects; it must resolve directly.
  - Cryptographically verified build provenance (signed, bound to CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-gig-core-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 987 tokens (~98/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add cyan-eclipse-technologies-llc-gig-core -- uvx eclipse-gig-core
```

### Cursor

```json
{
  "mcpServers": {
    "cyan-eclipse-technologies-llc-gig-core": {
      "command": "uvx",
      "args": [
        "eclipse-gig-core"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cyan-eclipse-technologies-llc-gig-core": {
      "command": "uvx",
      "args": [
        "eclipse-gig-core"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cyan-eclipse-technologies-llc-gig-core -- uvx eclipse-gig-core
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyan-eclipse-technologies-llc-gig-core": {
      "type": "local",
      "command": [
        "uvx",
        "eclipse-gig-core"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cyan-eclipse-technologies-llc-gig-core --command uvx --arg eclipse-gig-core
```

### Hermes

```yaml
mcp_servers:
  cyan-eclipse-technologies-llc-gig-core:
    command: "uvx"
    args: ["eclipse-gig-core"]
```

### Netclaw

```json
{
  "McpServers": {
    "cyan-eclipse-technologies-llc-gig-core": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "eclipse-gig-core"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cyan-eclipse-technologies-llc-gig-core -t stdio -c uvx -a eclipse-gig-core
```

### Other

```json
{
  "mcpServers": {
    "cyan-eclipse-technologies-llc-gig-core": {
      "command": "uvx",
      "args": [
        "eclipse-gig-core"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-29 (score 70, −5)

- [security regression] Source repository: pass → fail

### 2026-10-28 (score 75, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-27 (score 60)

First indexed and scored.

## MCP tools (10)

### `brief_create` (~200 tokens)

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.

Input parameters:

- `brief_id` (string)
- `category` (string, required)
- `ceiling_all_in` (number, required)
- `details` (object)
- `intended_platforms` (array)
- `license_required` (string, required)
- `location` (object, required)
- `photos` (array)
- `prohibited_platforms` (array)
- `safety_access` (object)
- `scope` (object, required)
- `service` (string, required)
- `timing` (object, required)
- `tip_policy` (object)

### `brief_update` (~59 tokens)

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).

Input parameters:

- `brief_id` (string, required)
- `changes` (object, required)

### `brief_approve` (~77 tokens)

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.

Input parameters:

- `approved_at` (string)
- `approver` (string)
- `brief_hash` (string, required)
- `brief_id` (string, required)
- `variant_hashes` (object)

### `brief_read` (~29 tokens)

Read a brief with its version, hash, and approval validity.

Input parameters:

- `brief_id` (string, required)

### `quote_normalize` (~196 tokens)

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.

Input parameters:

- `ceiling_all_in` (number)
- `currency` (string)
- `fees` (array)
- `fees_exposed` (boolean)
- `hour_cap` (number)
- `hourly_rate` (number)
- `job_price` (number)
- `model` (string, required)
- `owner_fee_exception` (object)
- `platform` (string, required)
- `pro` (object, required)
- `raw_quote_ref` (string)
- `tax` (number)
- `tip` (object)
- `valid_until` (string)

### `quote_read` (~41 tokens)

Read a normalized quote; optional ceiling_all_in re-runs the ceiling test.

Input parameters:

- `ceiling_all_in` (number)
- `quote_id` (string, required)

### `hire_check` (~148 tokens)

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.

Input parameters:

- `as_of` (string)
- `brief_id` (string, required)
- `mandate` (object)
- `person_confirm_token` (string)
- `quote_approval_token` (string)
- `quote_id` (string, required)

### `completion_verify` (~139 tokens)

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).

Input parameters:

- `brief_id` (string, required)
- `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)

### `review_draft` (~67 tokens)

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.

Input parameters:

- `verification_id` (string, required)

### `receipt_list` (~31 tokens)

List the append-only, hash-chained gig-core receipts and verify the chain.

Input parameters:

- `limit` (integer)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/cyan-eclipse-technologies-llc-gig-core/eclipse-gig-core#diagnostics

## Score history

- 2026-11-04: 70
- 2026-11-03: 70
- 2026-11-02: 70
- 2026-11-01: 70
- 2026-10-31: 70
- 2026-10-30: 70
- 2026-10-29: 70
- 2026-10-28: 75
- 2026-10-27: 60

## Common questions

### 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.

## Links

- PyPI project: https://pypi.org/project/eclipse-gig-core/
- Socket report: https://socket.dev/pypi/package/eclipse-gig-core
- Website: https://eclipsebazaar.com/
- Changelog RSS feed: https://verifymcp.io/servers/cyan-eclipse-technologies-llc-gig-core/eclipse-gig-core.xml
- Changelog JSON feed: https://verifymcp.io/servers/cyan-eclipse-technologies-llc-gig-core/eclipse-gig-core.json
- HTML version of this page: https://verifymcp.io/servers/cyan-eclipse-technologies-llc-gig-core/eclipse-gig-core