Eclipse Social Core MCP
PYPI · ECLIPSE-SOCIAL-CORE
One canonical, hash-bound package behind every Eclipse social adapter. It publishes nothing itself
Available components
Last scanned (21 hours ago)
Scores higher than 64% of PyPI servers
Category Marketing and SEO
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-social-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 1112 tokens (~74/item across 15 items; 15 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "adapter_kill_switch" implies "kill" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 15 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.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +10
- Source repository: pass → fail ▼ security
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 58
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-social-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-social-core-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-social-core-mcp/.github/workflows/publish-pypi.yml@refs/tags/v0.1.0 |
| Rekor log index | 3517873792 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:09efbb8bf98596c6949758ee82ce3c3042d4a88046b19548866d3c17caeb6eee |
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 →
account_inventory ~34
All registered accounts with declared + effective mode matrices, last probe, and kill-switch state. No credential values exist in this system.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
account_set ~146
Register/update an authorized account: platform, adapter, owner, role, declared capability modes (capability -> mode), and the latest capability probe {status: ok|failed, at, terms_version}. A FAILED probe downgrades effective modes automatically (write modes collapse to prep; reads flagged). Evaluation only — no platform is contacted, no credentials are held.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | yes | – |
| account_type | string | – | – |
| adapter | string | – | – |
| connection_state | string | – | – |
| modes | object | – | – |
| owner | string | – | – |
| platform | string | – | – |
| probe | object | – | – |
| role | string | – | – |
No output schema declared.
No examples provided.
adapt_preview ~114
Build one native variant for an adapter profile (aperture_feed, aperture_reel, aperture_story, prism_shorts, zephyr, wire): media geometry, copy under the surface's limit, the surface's working link placement, platform-required disclosure labels, element order — plus the classified adaptation diff. The variant is hash-bound at build.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | – | – |
| adapter | string | yes | – |
| canonical_id | string | yes | – |
| mode | string | – | – |
| schedule | object | – | – |
No output schema declared.
No examples provided.
adaptation_diff ~70
The classified diff for a built variant (MEDIA_CROP, TEXT_REWRITE, LINK_PLACEMENT, ORDER, DISCLOSURE, METADATA, FORMAT_OMISSION, ...). Substantive changes — numbers, claims, CTA — are flagged, never silent.
| Name | Type | Req | Description |
|---|---|---|---|
| variant_id | string | yes | – |
No output schema declared.
No examples provided.
adapter_kill_switch ~63
Independently disable one capability scope: family | adapter | account. Write capabilities freeze first; drafts and receipts remain readable.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | – | – |
| adapter | string | – | – |
| on | boolean | – | – |
| scope | string | yes | – |
No output schema declared.
No examples provided.
approval_check ~47
Verify a variant's approval is still valid: recompute the hash from current fields and compare with the approved hash. Any post-approval change = invalid.
| Name | Type | Req | Description |
|---|---|---|---|
| variant_id | string | yes | – |
No output schema declared.
No examples provided.
approval_pack ~51
The review artifact (SS3.2 tool 6): canonical item + every native variant + diffs + destination/account + schedule. This is the object the owner approves.
| Name | Type | Req | Description |
|---|---|---|---|
| canonical_id | string | yes | – |
No output schema declared.
No examples provided.
approve_variant ~43
Record the owner's approval of one variant, bound to the exact canonical hash and exact variant hash.
| Name | Type | Req | Description |
|---|---|---|---|
| approver | string | yes | – |
| variant_id | string | yes | – |
No output schema declared.
No examples provided.
content_get ~29
One canonical content record in full, hash + approval state included.
| Name | Type | Req | Description |
|---|---|---|---|
| canonical_id | string | yes | – |
No output schema declared.
No examples provided.
content_ingest ~88
Ingest a canonical content object (SS3.1): masters + provenance, copy, claims WITH sources, rights per asset, accessibility assets, disclosure record, intended/prohibited surfaces, schedule. Validates and issues the SHA-256 content hash; re-ingesting changed content bumps the version. Missing rights/claims-sources/alt-text are named blockers.
| Name | Type | Req | Description |
|---|---|---|---|
| content | object | yes | – |
No output schema declared.
No examples provided.
engagement_log ~131
Append one executed or owner-completed engagement action to the append-only log (timestamp, account, adapter/mode, target, action, full comment text, why, result, cap context, stop state).
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| action | string | yes | – |
| adapter | string | – | – |
| comment_text | string | – | – |
| mode | string | – | – |
| result | string | – | – |
| stop_or_warning | string | – | – |
| target_account | string | – | – |
| target_url | string | – | – |
| ts | integer | – | – |
| why | string | – | – |
No output schema declared.
No examples provided.
engagement_report ~35
Daily-report view over the engagement log: every action, totals vs the week's caps, stop state.
| Name | Type | Req | Description |
|---|---|---|---|
| week | integer | – | – |
No output schema declared.
No examples provided.
policy_check ~171
Engagement policy evaluator — the house playbook as data (SS5). action: like | comment | report_stop | reset. Enforces week-1 caps (15 likes / 5 comments per day) and week-2+ caps (30/10), the 2-likes-per-target cap, no links / no self-promo / no hashtag stuffing / <=1 emoji in comments, no duplicate comments, and stop-signal finality. EVERY check is receipted, ALLOW and DENY alike.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | – | – |
| action | string | yes | – |
| adapter | string | – | – |
| comment_text | string | – | – |
| counts | object | – | – |
| owner_reset | boolean | – | – |
| signal | string | – | – |
| week | integer | – | – |
No output schema declared.
No examples provided.
receipt_list ~22
The append-only, hash-chained receipt ledger, with chain verification.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
variant_revise ~68
Revise a variant's copy/hashtags/schedule/destination/link/disclosures/order/media. HASH LAW: the hash recomputes; an approval bound to the old hash is invalidated and the variant returns to review.
| Name | Type | Req | Description |
|---|---|---|---|
| changes | object | yes | – |
| variant_id | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Eclipse Social Core MCP server?
Eclipse Social Core MCP runs locally as a PyPI package, launched with uvx eclipse-social-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-social-core
claude mcp add cyan-eclipse-technologies-llc-social-core -- uvx eclipse-social-core
What is the Eclipse Social Core MCP server?
Eclipse Social Core MCP is listed in the public MCP registry as io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/social-core. One canonical, hash-bound package behind every Eclipse social adapter. It publishes nothing itself. This page covers its PyPI package (eclipse-social-core).
Is the Eclipse Social Core MCP server safe to use?
Eclipse Social Core MCP scores 68 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 Social Core MCP server expose?
Eclipse Social Core MCP exposes 15 tools: account_set, account_inventory, content_ingest, content_get, adapt_preview, and 10 more. Their descriptions and schemas cost roughly 1,112 tokens of context every time the server is loaded.
Is the Eclipse Social Core MCP server still maintained?
Eclipse Social 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 Social Core MCP server under?
Eclipse Social 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.