dashboardbase
NPM · @DASHBOARDBASE/MCP
Validate dashboardbase widget endpoint responses and setup files against the live contract.
Available components
Last scanned (19 hours ago)
Scores higher than 99% of npm servers
Category Developer Tools
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 Security98
- 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
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to dashboardbase/mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 21 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 512 tokens (~170/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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
- Stability: 0.97 → pass security
- 3 Nov 26 −1
- Stability: pass → 0.97 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 21 Oct 26 +1
- Stability: 0.97 → pass security
- 20 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.83 → pass security
- 15 Oct 26 −3
- Stability: pass → 0.80 functional
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/@dashboardbase/mcp@1.0.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 | dashboardbase/mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/dashboardbase/mcp/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 3245550190 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f9c59a4cd87f098ba013e2bf2bbd79130c9798d2a1dcfe2e5df589f5249dd4dec86d8ecfdbc662c278d415e6163ff91b13f96702a3fa0acfc9cf6ab88 |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
create_setup_link Create dashboardbase setup link ~134
Upload a dashboardbase setup file and get back a link that opens straight into its import preview in dashboardbase. Only call this when the user has asked for a link: the file leaves their machine, and anyone holding the link can read it for 48 hours. Validate the file with validate_setup_file first. A file carrying credential-shaped fields is refused with the offending fields listed — remove them, never work around the check.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | The full text of the setup file. Provide this or `path`. |
| path | string | – | Path to the setup file, absolute or relative to the working directory. |
| Name | Type | Req | Description |
|---|---|---|---|
| created | boolean | yes | True when the link was created. |
| errors | array | – | The fields that stopped the link being created. |
| expiresAt | string|null | – | When the link stops working (UTC). |
| reason | string | – | Why no link was created, e.g. `credentials_detected`. |
| url | string | – | The link to hand to the user. |
No examples provided.
validate_setup_file Validate dashboardbase setup file ~123
Validate a dashboardbase setup file (the declarative JSON that provisions a dashboard, usually stored at .dashboardbase/<name>.json). Returns whether the file is valid plus any errors and warnings, with the JSON path, field and line/column of each problem. Use this after writing or editing a setup file, before telling the user it is ready to import.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | The full text of the setup file. Provide this or `path`. |
| path | string | – | Path to the file to validate, absolute or relative to the working directory. |
| Name | Type | Req | Description |
|---|---|---|---|
| errors | array | yes | Problems that make the file invalid. |
| valid | boolean | yes | True when the setup file passes validation. |
| warnings | array | yes | Non-fatal advice about the file. |
No examples provided.
validate_widget_response Validate dashboardbase widget response ~190
Validate the JSON body a dashboardbase widget endpoint returns, against the widget contract. Pass the complete response body — the envelope with title, actions, data and alert — exactly as the endpoint returns it, not just the inner `data` payload. Returns whether the response is valid, the widget type it was checked against, and the path and message of each problem. Use this after building or changing an endpoint that dashboardbase will poll.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Path to the file to validate, absolute or relative to the working directory. |
| response | – | – | The full response body from the widget endpoint, including the title/actions/data/alert envelope. Accepts a JSON object or a JSON string. Provide this or `path`. |
| widgetType | string | – | Optional widget type to check against, for example "kpi", "line" or "table". Inferred from the response when omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| errors | array | yes | Problems that make the response invalid. |
| valid | boolean | yes | True when the response passes validation. |
| widgetType | string | – | The widget type the response was validated against. |
No examples provided.
How do I install the dashboardbase MCP server?
dashboardbase runs locally as an npm package, launched with npx -y @dashboardbase/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 · @dashboardbase/mcp
claude mcp add com-dashboardbase-mcp -- npx -y @dashboardbase/mcp
What is the dashboardbase MCP server?
dashboardbase is an MCP server listed in the public MCP registry as com.dashboardbase/mcp. Validate dashboardbase widget endpoint responses and setup files against the live contract. This page covers its npm package (@dashboardbase/mcp).
Is the dashboardbase MCP server safe to use?
dashboardbase scores 96 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 dashboardbase MCP server expose?
dashboardbase exposes 3 tools: validate_setup_file, validate_widget_response, create_setup_link. Their descriptions and schemas cost roughly 447 tokens of context every time the server is loaded.
Is the dashboardbase MCP server still maintained?
dashboardbase 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 dashboardbase MCP server under?
dashboardbase declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.