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.

Vizier

NPM · @PIPEWORX/MCP-VIZIER · 2 COMPONENTS

VizieR MCP — CDS astronomical catalogue access.

0 this week 79 Trust /100

Last scanned (8 hours ago)

Scores higher than 62% of npm servers

Category Health and Science

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-vizier). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 6 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 346 tokens (~86/item across 4 items; 4 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 Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 62% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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.

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.

  • 29 Oct 26 79

    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 npm/@pipeworx/mcp-vizier@0.2.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 npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-vizier
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-vizier/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3560985168
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:6f9408a7c584c858ed751b76e6d1c768c5b40f02b2eec4358baae47433bd25e2ac11da12da92a4706a75ee8fb112dbcf32c3781280e3031d34b79d619

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~293 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
catalogs ~51

Search VizieR catalogue metadata.

NameTypeReqDescription
maxnumber–1-200 (default 25)
querystringyesKeywords (e.g. "Gaia DR3", "exoplanet").

No output schema declared.

No examples provided.

cone_search ~60

Cone search around (RA, Dec).

NameTypeReqDescription
catalogstringyes–
decnumberyesDec in decimal degrees.
maxnumber––
ranumberyesRA in decimal degrees.
radius_degnumberyes–

No output schema declared.

No examples provided.

object ~40

Query by object name (resolved via SIMBAD/NED).

NameTypeReqDescription
catalogstring–Optional catalogue id; default queries all.
namestringyes–

No output schema declared.

No examples provided.

query_catalog ~142

VizieR astronomical catalogue service at CDS Strasbourg — return data rows from one published catalogue, identified by its VizieR id such as "I/345/gaia2" (Gaia DR2). Takes optional column selection and a numeric constraint expression, up to 50000 rows. Answers what a published astronomy catalogue records for stars, galaxies or other objects meeting a cut.

NameTypeReqDescription
catalogstringyes–
columnsstring–Comma-sep columns to return.
constraintstring–Solr-style constraints, e.g. "Plx>20"
maxnumber–1-50000 (default 50).

No output schema declared.

No examples provided.

Install

How do I install the Vizier MCP server?

Vizier runs locally as an npm package, launched with npx -y @pipeworx/mcp-vizier. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-vizier

# add to Claude Code
claude mcp add pipeworx-io-vizier -- npx -y @pipeworx/mcp-vizier
Common questions

What is the Vizier MCP server?

Vizier is an MCP server listed in the public MCP registry as io.github.pipeworx-io/vizier. VizieR MCP, CDS astronomical catalogue access. This page covers its npm package (@pipeworx/mcp-vizier).

Is the Vizier MCP server safe to use?

Vizier scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 Vizier MCP server expose?

Vizier exposes 4 tools: catalogs, query_catalog, cone_search, object. Their descriptions and schemas cost roughly 293 tokens of context every time the server is loaded.

Is the Vizier MCP server still maintained?

Vizier is still listed as active in the MCP registry. We last reached this channel on 5 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 Vizier MCP server under?

Vizier declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.