Bragproof

← Reports

@pipeworx/mcp-exoplanet-archive

Starts with no setup0.2.1npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Contacts while installing and starting: gateway.pipeworx.io

6tools listed
1host contacted
0files written
0.4 sto start
0dependencies

What it contacted

Hosts it looked up or connected to while installing and starting with no input, watched from outside its sandbox. The npm registry is left out. Says nothing about what its tools contact when called.

Starting it

npx -y @pipeworx/mcp-exoplanet-archive@0.2.1

Installing a package runs its code. Use a sandbox for anything you have not read.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

exoplanet_archive_tap query, format
ADQL TAP query. For "how many confirmed exoplanets" or any per-planet count, query `pscomppars` (one row per confirmed planet) or COUNT(DISTINCT pl_name) -- never a bare COUNT(*) FROM ps, which counts published parameter SOLUTIONS (several per planet, currently ~40k rows for ~6.5k planets) and silently over-counts by 6x. Prefer the dedicated confirmed_planet_count tool for planet-count questions.
planets query, limit
Per-solution search against the `ps` (Planetary Systems) table -- one row per published parameter SOLUTION, with several solutions per confirmed planet. Good for comparing how a planet's measured parameters changed across papers; NOT a planet count or a clean per-planet list (its row count is parameter solutions, not planets). For planet counts or one-row-per-planet listings use `composite` or `confirmed_planet_count` instead.
composite query, limit
Composite planet parameter table `pscomppars` -- one row per confirmed planet. Use this (or `confirmed_planet_count`) for "how many confirmed exoplanets" questions and for any per-planet listing; do not use `ps`/`tap` for those, since `ps` has several rows per planet.
confirmed_planet_count query
Count of confirmed exoplanets -- from the composite parameter table `pscomppars` (one row per planet), not the per-solution `ps` table. Use this for "how many confirmed exoplanets" questions. Optional filter narrows the count, e.g. "disc_year = 2023" for planets discovered that year. Returns the unit and the date of the live query.
kepler_candidates query, limit
Kepler Object of Interest (KOI) candidate table -- unconfirmed candidates, not confirmed planets. Do not use this table's row count to answer a confirmed-planet-count question.
microlensing query, limit
Microlensing event table -- detection events, not a planet count.

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Install facts

LicenseMIT
Needsnode >=18
Sourcegithub.com/pipeworx-io/mcp-exoplanet-archive
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-Sg6I74i0xPWEtRyiM4lHQYD+GlSxgknFiAx+s01XEla5qm4W8Fs/031+2sR2h36/rGexOPZ98RHEh2Lr5uL7+w==

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/@pipeworx/mcp-exoplanet-archive.svg)](https://bragproof.smaverk.com/r/%40pipeworx/mcp-exoplanet-archive)

New version out? Ask for a fresh report.