Eclipse Health Check MCP

io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLCPublished by GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLCv0.1.0Updated Oct 26, 2026

Scan an MCP server or agent configuration for security posture — evidence-bound findings

The publisher's own server: check.tattoo: tattoo size and placement guide

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Scans an MCP server or agent configuration and reports security-posture findings, each tied to supporting evidence.

What you can do
  • Scan an MCP server or agent configuration for security posture.
  • Return findings that are bound to the evidence behind them.
When to use it
Useful when you want a second opinion on the security posture of an MCP server or agent configuration before trusting or deploying it.
Requirements
Runs as a local process over stdio on a desktop machine; no packages, environment variables, headers or authentication are declared.
Before you install
No tool list, README or instructions are published, so the exact checks, what configuration data it reads, and whether anything leaves the machine cannot be verified from the listing. Review the source before pointing it at sensitive configuration.

Installation

In SourceWeft

  1. Open Eclipse Health Check MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestOct 26, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Check integrations