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.

Station

NPM · @SANTORI/STATION · 2 COMPONENTS

Meeting rooms for your agents. They can share context with each other and work together.

−15 this week 38 Trust /100

Last scanned (6 hours ago)

Scores higher than 12% of npm 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 Security48
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 36 of 107 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability34
  • AI-judged instruction clarity (poor).Fail
  • Tool/resource definitions use about 46 tokens (~46/item across 0 items; 0 tools + 0 resources), lean.Pass
  • Nothing to assess: this server has no tools to check for usage examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: the tool surface changed between 0.4.1 and 0.9.7: 4 tool removals, 0 breaking changes, 0 additions. See how to fix → Fail
Tool Coverage0
  • Nothing to assess: this server exposes no tools, so there are no tool definitions to check for coverage.Fail
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • Destructive-tool annotations not yet verified: our capture listed no tools, so there were no annotations to read.Unverified
  • An AI judge read all 1 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
What we tested

Checks we ran (14)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
  • Destructive annotations in Tool SafetyDestructive-tool annotations not yet verified: our capture listed no tools, so there were no annotations to read.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +1
    • Malware scan: pass → unverified ▼ security
    • Known CVEs: unverified → pass ▲ security
    • Source repository: fail → pass ▲ security
    • Security disclosure: unverified → fail ▼ functional
    • Dependency health: unverified → 0.84 ▲ functional
    • Package version: 0.9.6 → 0.9.7 functional
  • 20 Nov 26 0
    • Package version: 0.9.5 → 0.9.6 functional
  • 19 Nov 26 +4
    • Known CVEs: pass → unverified ▼ security
    • Stability: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Dependency health: 0.84 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: fail → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.9.0 → 0.9.5 functional
    • Package version: 0.9.0 → 0.9.4 functional
    • Package version: 0.9.0 → 0.9.3 functional
    • Package version: 0.9.0 → 0.9.1 functional
  • 18 Nov 26 +11
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.84 ▲ functional
    • Dependency health: unverified → 0.85 ▲ functional
    • Package version: 0.8.1 → 0.9.0 functional
    • Package version: 0.8.1 → 0.8.3 functional
    • Package version: 0.6.0 → 0.8.2 functional
  • 17 Nov 26 −26
    • Known CVEs: pass → unverified ▼ security
    • Malware scan: pass → unverified ▼ security
    • Dependency health: 0.85 → unverified ▼ functional
    • Package version: 0.7.2 → 0.8.1 functional
    • Package version: 0.7.2 → 0.8.0 functional
  • 16 Nov 26 +15
    • Stability: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Known CVEs: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: fail → unverified ▼ functional
    • Dependency health: 0.85 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.7.0 → 0.7.2 functional
    • Package version: 0.7.0 → 0.7.1 functional
  • 15 Nov 26 −20
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.07 → fail ▼ security
    • Known CVEs: unverified → pass ▲ security
    • Destructive annotations: pass → unverified ▼ functional
    • Schema quality: fail → unverified ▼ functional
    • Tool coverage: 100 → fail ▼ functional
    • Dependency health: unverified → 0.85 ▲ functional
    • Schema quality: fail → pass ▲ functional
    • Schema quality: good → poor functional
    • Package version: 0.6.0 → 0.7.0 functional
  • 14 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.85 ▲ functional
    • Package version: 0.5.0 → 0.6.0 functional
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 21 Nov 2026 · Analysed npm/@santori/station@0.9.7

Provenance No attestation

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

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 107 packages
Packages resolved 107
Stale 36
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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 →

The sandbox run completed and this package exposed no tools.

Install

How do I install the Station MCP server?

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

npm · @santori/station

# add to Claude Code
claude mcp add santorilabs-station -- npx -y @santori/station mcp
Common questions

What is the Station MCP server?

Station is an MCP server listed in the public MCP registry as io.github.santorilabs/station. Meeting rooms for your agents. They can share context with each other and work together. This page covers its npm package (@santori/station).

Is the Station MCP server safe to use?

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

Station exposes no tools. We connected to it and read its tool list, and it was empty, so it offers an MCP client nothing to call.

Is the Station MCP server still maintained?

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

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

What did VerifyMCP test on the Station MCP server?

VerifyMCP ran 14 checks on Station, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about Station: Malware scan and Destructive annotations. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.