Tsa Passenger Volumes
NPM · @PIPEWORX/MCP-TSA-PASSENGER-VOLUMES · 2 COMPONENTS
tsa-passenger-volumes — daily U.S. airport checkpoint screening counts.
Available components
Last scanned (8 hours ago)
Scores higher than 58% of npm servers
Category Data and Analytics
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-tsa-passenger-volumes). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 423 tokens (~211/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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.
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.
- 5 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 3 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 78
First indexed and scored.
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-tsa-passenger-volumes@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-tsa-passenger-volumes |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-tsa-passenger-volumes/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560578689 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:4e4854ccb373f4d56dfe481749a7198bce7bcd8746c5ebf66e4b16e3499ba3c6d325e07c0d04fe5a2cac3632a090a3b51076d31ed0bb89d316fd6a5fd |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
tsa_checkpoint_stats ~180
Busiest/quietest-day stats (max, min, average, total) for TSA's daily airport checkpoint screening counts over a period — e.g. "busiest travel day of 2026" or "average daily screenings last July". Pass `year`, a `start_date`/`end_date` range, or nothing for the current year to date. Covers 2019-01-01 through roughly yesterday's date in 2026. Returns found:false (not an error) if the period has no published data yet. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | Range end, YYYY-MM-DD (inclusive). |
| start_date | string | – | Range start, YYYY-MM-DD (inclusive). |
| year | integer | – | A whole calendar year, e.g. 2024. 2019-2026. |
No output schema declared.
No examples provided.
tsa_checkpoint_volumes ~184
Daily U.S. airport checkpoint screening counts (how many travelers TSA screened nationwide each day), sourced from the TSA's own published daily figures. Pass a single `date`, a `start_date`/`end_date` range, or a `year` for the whole year; with nothing, returns the current year to date. Covers 2019-01-01 through roughly yesterday's date in 2026. Returns found:false (not an error) for a date outside that published range. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | A single day, YYYY-MM-DD. |
| end_date | string | – | Range end, YYYY-MM-DD (inclusive). |
| start_date | string | – | Range start, YYYY-MM-DD (inclusive). |
| year | integer | – | A whole calendar year, e.g. 2024. 2019-2026. |
No output schema declared.
No examples provided.
How do I install the Tsa Passenger Volumes MCP server?
Tsa Passenger Volumes runs locally as an npm package, launched with npx -y @pipeworx/mcp-tsa-passenger-volumes. 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-tsa-passenger-volumes
claude mcp add pipeworx-io-tsa-passenger-volumes -- npx -y @pipeworx/mcp-tsa-passenger-volumes
What is the Tsa Passenger Volumes MCP server?
Tsa Passenger Volumes is an MCP server listed in the public MCP registry as io.github.pipeworx-io/tsa-passenger-volumes. tsa-passenger-volumes, daily U.S. airport checkpoint screening counts. This page covers its npm package (@pipeworx/mcp-tsa-passenger-volumes).
Is the Tsa Passenger Volumes MCP server safe to use?
Tsa Passenger Volumes scores 78 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 Tsa Passenger Volumes MCP server expose?
Tsa Passenger Volumes exposes 2 tools: tsa_checkpoint_volumes, tsa_checkpoint_stats. Their descriptions and schemas cost roughly 364 tokens of context every time the server is loaded.
Is the Tsa Passenger Volumes MCP server still maintained?
Tsa Passenger Volumes 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 Tsa Passenger Volumes MCP server under?
Tsa Passenger Volumes declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.