Dchub
NPM · @PIPEWORX/MCP-DCHUB · 2 COMPONENTS
DC Hub -- data-center site selection, power and grid intelligence. Live per-request proxy of DC…
Available components
Last scanned (3 hours ago)
Scores higher than 65% of npm servers
Category Cloud Infrastructure
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-dchub). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1074 tokens (~153/item across 7 items; 7 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "dchub_execute_plan" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 8 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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- 1 Nov 26 −9
- Known CVEs: pass → unverified ▼ security
- 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
- Security disclosure: unverified → fail ▼ functional
- Capabilities: pass → unverified ▼ functional
- Dependency health: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.10 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.1 → 0.2.2 functional
- 31 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 62
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-dchub@0.2.2
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-dchub |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-dchub/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3617488053 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:062fa0eef8c6401fb24347980ce08c7486cdb1869aa05530b7dbf2485dc3723fe25ca3b34c994799f6257e818ae8d50d04700d083ba8b1ddfeb858054 |
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 →
dchub_execute_plan ~159
Answer a multi-part data-center question in one call (DC Hub): e.g. "rank markets for a 200 MW AI campus" or "power headroom in PJM". Plans and runs the needed lookups and returns the combined result with citations. Keyless calls return a preview.
| Name | Type | Req | Description |
|---|---|---|---|
| capacity_mw | number | – | Optional target capacity in MW |
| intent | string | yes | The question, unchanged, e.g. "rank markets for a 200 MW AI campus" |
| iso | string | – | Optional grid/ISO, e.g. PJM, ERCOT |
| market | string | – | Optional market slug, e.g. northern-virginia |
| state | string | – | Optional US state code |
No output schema declared.
No examples provided.
dchub_get_grid_data ~101
Live electricity grid data for one grid (DC Hub): fuel mix and demand for US ISOs (PJM, ERCOT, CAISO, MISO, SPP, NYISO, ISO-NE), utility balancing authorities, and international grids.
| Name | Type | Req | Description |
|---|---|---|---|
| iso | string | yes | Grid code, e.g. PJM, ERCOT, CAISO |
| metric | string | – | Optional metric |
| period | string | – | Optional period |
No output schema declared.
No examples provided.
dchub_get_interconnection_queue ~120
Grid interconnection queue depth (DC Hub): queued generation GW per US ISO, how congested the queue is, and ERCOT's large-load (data-center) queue. Omit iso for an all-ISO snapshot; pass iso for per-project rows on one grid. Keyless calls return a preview.
| Name | Type | Req | Description |
|---|---|---|---|
| iso | string | – | ISO/RTO grid region, e.g. ERCOT, PJM, MISO, CAISO, SPP, NYISO, ISONE; omit for the all-ISO snapshot |
No output schema declared.
No examples provided.
dchub_get_market_intel ~103
Data-center market intelligence for one metro (DC Hub): facility count, tracked MW, status mix, top providers, pipeline and lease pricing. Market is a slug such as northern-virginia. Keyless calls return a trimmed preview.
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | yes | Market slug, e.g. northern-virginia, dallas, phoenix |
| metric | string | – | Optional metric focus |
| period | string | – | Optional period |
No output schema declared.
No examples provided.
dchub_get_news ~209
Curated data-center industry news (DC Hub) from 40+ trade sources (DCD, Data Center Knowledge, Data Center Frontier, Capacity Media, etc.), refreshed every 30 min. Filter by category (deals/permits/outages/policy/AI), source, or date range. Keyless calls return a preview.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | News topic filter, e.g. deals, permits, outages, policy, AI |
| date_from | string | – | Earliest published date, ISO-8601 (YYYY-MM-DD) |
| date_to | string | – | Latest published date, ISO-8601 (YYYY-MM-DD) |
| limit | number | – | Max results to return (1-500; default varies) |
| query | string | – | Free-text keyword, e.g. "Stargate" or "interconnection queue" |
| source | string | – | Restrict to one trade source, e.g. DCD, "Data Center Frontier" |
No output schema declared.
No examples provided.
dchub_search_facilities ~177
Find data centers and who operates them (DC Hub facility registry), filtered by city, state, country, operator or MW range. Returns name, operator, location and verification flag; MW detail needs a DC Hub key. Keyless calls return a preview.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City, e.g. Ashburn |
| country | string | – | Country code, e.g. US |
| limit | number | – | Rows to return (default 10) |
| max_capacity_mw | number | – | Maximum MW |
| min_capacity_mw | number | – | Minimum MW |
| offset | number | – | Paging offset |
| operator | string | – | Operator, e.g. Equinix |
| query | string | – | Free-text search |
| state | string | – | State code, e.g. VA |
No output schema declared.
No examples provided.
dchub_source_capacity ~151
Search data-center capacity available to buy or lease (DC Hub Capacity Source): powered land, powered shells, turnkey capacity and colocation, by size (min_kw / min_mw) and location (region, state, market).
| Name | Type | Req | Description |
|---|---|---|---|
| delivery_type | string | – | Optional delivery type |
| limit | number | – | Rows to return |
| location | string | – | Free-text location |
| market | string | – | Market slug |
| min_kw | number | – | Minimum size in kW |
| min_mw | number | – | Minimum size in MW |
| region | string | – | Region key, e.g. europe, north-america |
| state | string | – | US state code |
No output schema declared.
No examples provided.
How do I install the Dchub MCP server?
Dchub runs locally as an npm package, launched with npx -y @pipeworx/mcp-dchub. 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-dchub
claude mcp add pipeworx-io-dchub -- npx -y @pipeworx/mcp-dchub
What is the Dchub MCP server?
Dchub is an MCP server listed in the public MCP registry as io.github.pipeworx-io/dchub. DC Hub -- data-center site selection, power and grid intelligence. Live per-request proxy of DC… This page covers its npm package (@pipeworx/mcp-dchub).
Is the Dchub MCP server safe to use?
Dchub scores 80 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 Dchub MCP server expose?
Dchub exposes 7 tools: dchub_execute_plan, dchub_search_facilities, dchub_get_market_intel, dchub_get_grid_data, dchub_source_capacity, and 2 more. Their descriptions and schemas cost roughly 1,020 tokens of context every time the server is loaded.
Is the Dchub MCP server still maintained?
Dchub 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 Dchub MCP server under?
Dchub declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.