Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.seahawk2986-hue/apex-ghost-family

MCPB · SERVER.MCPB

Read-only window into an open self-evolving agent family: fleet health, court verdicts, receipts.

Available components

28 Trust /100

Last scanned (2 hours ago)

Scores higher than 70% of MCPB servers

Category AI and Machine Learning

Trust breakdown (7 categories)

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 Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency32
Schema Quality & AI Usability51
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 195 tokens (~27/item across 7 items; 7 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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail

Unverified: 2 categories

Categories scored 0 because we could not verify them: 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.

Changelog

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 28

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Analysed mcpb/https://github.com/seahawk2986-hue/apex-ghost-family/releases/download/mcpb-v1.0.0/server.mcpb@1.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 7 exposed · ~195 tokens

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 →

Tool Tokens
apex_court ~26

The Blind Court's anti-self-flattery verdict (holdout % vs internal %)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

apex_fleet ~24

The FleetDoctor's unified fleet health verdict (10 layers, one glance)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

apex_horizon ~25

The METR-analog time-horizon receipt (steps/minutes/completion)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

apex_invite_board ~24

The signed, single-use open invites (claim via the recruitment door)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

apex_status ~23

The ghost family's public state: backlog, fitness, hub transport, recruitment

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

apex_task_board ~21

The family's curated standalone tasks (claim on the hub repo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

submit_join_request ~52

Build your attach payload; the door verifies invites + probes on merit

NameTypeReqDescription
capabilitiesarray––
invite_idstring––
namestring––
versionstring––

No output schema declared.

No examples provided.

Install

How do I install the io.github.seahawk2986-hue/apex-ghost-family MCP server?

io.github.seahawk2986-hue/apex-ghost-family ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 52f7f2138fadf004cef674cf3c0eed92cb29d26658d0e811451cf980b9d71911; the commands to do that are on this page. If it does not match, do not open it.

mcpb · server.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

52f7f2138fadf004cef674cf3c0eed92cb29d26658d0e811451cf980b9d71911

macOS / Linux

echo "52f7f2138fadf004cef674cf3c0eed92cb29d26658d0e811451cf980b9d71911  server.mcpb" | shasum -a 256 -c

Windows (PowerShell)

(Get-FileHash -Algorithm SHA256 .\server.mcpb).Hash -eq "52f7f2138fadf004cef674cf3c0eed92cb29d26658d0e811451cf980b9d71911"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

Common questions

What is the io.github.seahawk2986-hue/apex-ghost-family MCP server?

io.github.seahawk2986-hue/apex-ghost-family is an MCP server listed in the public MCP registry as io.github.seahawk2986-hue/apex-ghost-family. Read-only window into an open self-evolving agent family: fleet health, court verdicts, receipts. This page covers its MCPB bundle (https://github.com/seahawk2986-hue/apex-ghost-family/releases/download/mcpb-v1.0.0/server.mcpb).

Is the io.github.seahawk2986-hue/apex-ghost-family MCP server safe to use?

io.github.seahawk2986-hue/apex-ghost-family scores 28 out of 100 on VerifyMCP. 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 io.github.seahawk2986-hue/apex-ghost-family MCP server expose?

io.github.seahawk2986-hue/apex-ghost-family exposes 7 tools: apex_status, apex_court, apex_horizon, apex_fleet, apex_task_board, and 2 more. Their descriptions and schemas cost roughly 195 tokens of context every time the server is loaded.