Predicthq
NPM · @PIPEWORX/MCP-PREDICTHQ · 2 COMPONENTS
PredictHQ MCP — wraps the PredictHQ Events API (predicthq.com)
Available components
Last scanned (10 hours ago)
Scores higher than 68% 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-predicthq). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 927 tokens (~309/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 Management23
- Stability observed for 7 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 +3
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Stability: unverified → 0.20 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 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-predicthq@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-predicthq |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-predicthq/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3691859997 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:607866c31153a1fd842388c8c7a8b52a9bd6d8b7ebae6fc619ae42eff65b285efe31e81933f3c1ae47762247abb50348d658c685aa3816f0d4174f3cf |
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 →
get_event ~120
Fetch a single PredictHQ event by its id, returning its title, category, rank, predicted attendance, dates, and location. Example: get_event({ id: "abcDEF123" }).
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | REQUIRED — your own PredictHQ access token. Pipeworx does not front a key for PredictHQ (14-day trial, then sales contact). Free keyless alternatives for event listings: ticketmaster, seatgeek. |
| id | string | yes | The PredictHQ event id, e.g. "abcDEF123". |
No output schema declared.
No examples provided.
nearby_events ~371
Find PredictHQ events within a radius of a geographic point (latitude/longitude). Useful for "what is happening near this venue/store/airport" demand-forecasting queries. Filter by category and active-date window; results are ranked by predicted impact. Example: nearby_events({ latitude: 40.7128, longitude: -74.006, radius: "10km", category: "concerts,sports" }).
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | REQUIRED — your own PredictHQ access token. Pipeworx does not front a key for PredictHQ (14-day trial, then sales contact). Free keyless alternatives for event listings: ticketmaster, seatgeek. |
| category | string | – | Comma-separated event categories. One or more of: concerts, sports, conferences, expos, festivals, performing-arts, community, public-holidays, observances, politics, academic, school-holidays, dayli… |
| end | string | – | Only include events active on or before this date (YYYY-MM-DD), e.g. "2026-06-30". |
| latitude | number | yes | Center latitude in decimal degrees, e.g. 40.7128. |
| limit | number | – | Max events to return (default 15, max 50). |
| longitude | number | yes | Center longitude in decimal degrees, e.g. -74.006. |
| radius | string | – | Search radius with unit, e.g. "10km", "5mi" (default "10km"). |
| start | string | – | Only include events active on or after this date (YYYY-MM-DD), e.g. "2026-06-01". |
No output schema declared.
No examples provided.
search_events ~379
Search the PredictHQ Events API for real-world events (concerts, sports, conferences, festivals, public holidays, severe weather, etc.) used for demand forecasting. Filter by free-text query, category, country, and an active-date window; results are ranked by predicted impact. Returns each event with its rank, predicted attendance, dates, and location. Example: search_events({ query: "taylor swift", country: "US", category: "concerts", start: "2026-06-01", end: "2026-12-31" }).
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | REQUIRED — your own PredictHQ access token. Pipeworx does not front a key for PredictHQ (14-day trial, then sales contact). Free keyless alternatives for event listings: ticketmaster, seatgeek. |
| category | string | – | Comma-separated event categories. One or more of: concerts, sports, conferences, expos, festivals, performing-arts, community, public-holidays, observances, politics, academic, school-holidays, dayli… |
| country | string | – | 2-letter ISO country code, e.g. "US", "GB", "AU". |
| end | string | – | Only include events active on or before this date (YYYY-MM-DD), e.g. "2026-06-30". |
| limit | number | – | Max events to return (default 15, max 50). |
| query | string | – | Free-text search across event titles/descriptions, e.g. "marathon". |
| start | string | – | Only include events active on or after this date (YYYY-MM-DD), e.g. "2026-06-01". |
No output schema declared.
No examples provided.
How do I install the Predicthq MCP server?
Predicthq runs locally as an npm package, launched with npx -y @pipeworx/mcp-predicthq. 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-predicthq
claude mcp add pipeworx-io-predicthq -- npx -y @pipeworx/mcp-predicthq
What is the Predicthq MCP server?
Predicthq is an MCP server listed in the public MCP registry as io.github.pipeworx-io/predicthq. PredictHQ MCP, wraps the PredictHQ Events API (predicthq.com). This page covers its npm package (@pipeworx/mcp-predicthq).
Is the Predicthq MCP server safe to use?
Predicthq scores 81 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 Predicthq MCP server expose?
Predicthq exposes 3 tools: search_events, nearby_events, get_event. Their descriptions and schemas cost roughly 870 tokens of context every time the server is loaded.
Is the Predicthq MCP server still maintained?
Predicthq 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 Predicthq MCP server under?
Predicthq declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.