← Index

PixInsight Connector

io.github.mxcoppell/pixinsight-connectorv2.2.0Other

Operate PixInsight from any MCP agent. Community project, not affiliated with Pleiades Astrophoto

The current version, v2.2.0, was published to the official MCP registry on 2026-09-25. It is distributed as pixinsight-connector on npm, filed under Other by this index, and declares 7 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using PixInsight Connector in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
REVIEWstatus: PARTIALfresh until 2026-10-25 07:12 UTC
screened 2026-09-25tier: scannedgranularity: description-levelsource: registry

Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.

mcpindex.integrity.descriptionpassINFO

evidence“No malicious instructions”via static_description

Limits of this verdict
  • - Semantic screen only - the deterministic conformance probe has not run on this server
  • - Confidence is reported but not yet calibrated (v1)
  • - Screen reads the tool description, not the live behavior
  • - advisory
  • - registry description only no input schema
  • - screen model 8b

Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-09-25).

Contracts can change after screening, with no version bump. The gate pins PixInsight Connector’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Cite this record

People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.

Markdown
[Independent trust record for PixInsight Connector](https://mcpindex.ai/server/io-github-mxcoppell-pixinsight-connector) - screening verdict, registry provenance, and contract drift monitoring.
HTML
<a href="https://mcpindex.ai/server/io-github-mxcoppell-pixinsight-connector">Independent trust record for PixInsight Connector</a> - screening verdict, registry provenance, and contract drift monitoring.
Embed this badge

A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.

Markdown
[![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-mxcoppell-pixinsight-connector)](https://mcpindex.ai/server/io-github-mxcoppell-pixinsight-connector)
HTML
<a href="https://mcpindex.ai/server/io-github-mxcoppell-pixinsight-connector"><img src="https://mcpindex.ai/api/v1/badge/io-github-mxcoppell-pixinsight-connector" alt="mcpindex verdict" height="20" /></a>
Environment variables
PIXINSIGHT_BIN

Path to the PixInsight executable. When unset, the default install location for the OS is used.

PIXINSIGHT_DIR

PixInsight install root, from which the executable and its resources are derived. When unset, the default install location for the OS is used.

PIXINSIGHT_CONNECTOR_PACKS

Comma-separated tool packs to load: pack directories and .mjs files (an npm package by the path to its folder). Empty: no packs.

PIXINSIGHT_CONNECTOR_AUTOSTART

0 stops the connector from starting PixInsight when a tool call finds it not running.

PIXINSIGHT_CONNECTOR_WORKSPACE

The target folder the tools work in (session files in its agentic folder, results in its output folder). When unset, the folder the connector was started in; the set_workspace tool overrides both.

PIXINSIGHT_CONNECTOR_STATE

Where the connector's session files (scratch, bridge, logs) go, resolved against the target folder. When unset, <target>/agentic.

PIXINSIGHT_CONNECTOR_LOG

0 turns off the per-session call logs in <target>/agentic/logs.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
20
installability
25
documentation
15
stability
10
Alternatives in Other