Besttime
NPM · @PIPEWORX/MCP-BESTTIME · 2 COMPONENTS
BestTime MCP — foot-traffic / venue busyness forecasts (besttime.app)
Available components
Last scanned (21 hours ago)
Scores higher than 72% of npm servers
Category Maps and Location
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-besttime). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 652 tokens (~217/item across 3 items; 3 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 Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 79
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 4 Nov 2026 · Analysed npm/@pipeworx/mcp-besttime@0.2.1
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-besttime |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-besttime/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3601419686 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:aff946b8cd85e9e6813ba6974380ff1e478a2c848ab1f95c56c81ce9e9a952849d69d56d17396e8f118bbb91d4260716894f502785e3b5261411512cb |
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 →
besttime_forecast ~216
How busy is <venue> by hour/day (foot-traffic forecast) — creates a busyness forecast for a public venue (restaurant, bar, gym, store, museum) by name + address. Returns the 24-hour busyness curve (0-100) for each weekday plus busy/quiet/peak hours and a venue_id for later queries. Example: besttime_forecast({ venue_name: "McDonald's", venue_address: "Ocean Ave, San Francisco", _apiKey: "pri_xxx:pub_yyy" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | BestTime keys as "privateKey:publicKey" (pri_.../pub_...) from your besttime.app account (free test account available) |
| venue_address | string | yes | Business address, e.g. "1 Market St, San Francisco, CA" (max 1024 chars) |
| venue_name | string | yes | Business name, e.g. "McDonald's", "SoulCycle" (max 256 chars) |
No output schema declared.
No examples provided.
besttime_live ~182
Is <venue> busy right now vs usual — returns live foot-traffic busyness compared to the forecasted level for this hour. Identify the venue by venue_id, or by venue_name + venue_address. Example: besttime_live({ venue_name: "Blue Bottle Coffee", venue_address: "66 Mint St, San Francisco", _apiKey: "pri_xxx:pub_yyy" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | BestTime keys as "privateKey:publicKey" (pri_.../pub_...) from besttime.app |
| venue_address | string | – | Business address (required if venue_id not given) |
| venue_id | string | – | Venue id from besttime_forecast (fastest). Alternative to venue_name+venue_address. |
| venue_name | string | – | Business name (required if venue_id not given) |
No output schema declared.
No examples provided.
besttime_query ~202
Busyness for a venue at a specific hour or day — reads an already-forecasted venue (by venue_id from besttime_forecast). Pass `hour` for a single hour, or omit it to get the whole day's curve. Example: besttime_query({ venue_id: "ven_...", day: 4, hour: 18, _apiKey: "pri_xxx:pub_yyy" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | BestTime keys as "privateKey:publicKey" (pri_.../pub_...) from besttime.app |
| day | integer | – | Day of week 0-6 (0=Monday … 6=Sunday). Defaults to 0 (Monday) if omitted. |
| hour | integer | – | Hour of day 0-23 (optional). If given, returns that hour's busyness intensity. |
| venue_id | string | yes | Venue id returned by besttime_forecast |
No output schema declared.
No examples provided.
How do I install the Besttime MCP server?
Besttime runs locally as an npm package, launched with npx -y @pipeworx/mcp-besttime. 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-besttime
claude mcp add pipeworx-io-besttime -- npx -y @pipeworx/mcp-besttime
What is the Besttime MCP server?
Besttime is an MCP server listed in the public MCP registry as io.github.pipeworx-io/besttime. BestTime MCP, foot-traffic / venue busyness forecasts (besttime.app). This page covers its npm package (@pipeworx/mcp-besttime).
Is the Besttime MCP server safe to use?
Besttime scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 Besttime MCP server expose?
Besttime exposes 3 tools: besttime_forecast, besttime_query, besttime_live. Their descriptions and schemas cost roughly 600 tokens of context every time the server is loaded.
Is the Besttime MCP server still maintained?
Besttime is still listed as active in the MCP registry. We last reached this channel on 4 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 Besttime MCP server under?
Besttime declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.