# Dashboardbase (npm · @dashboardbase/mcp)

Validate Dashboardbase widget endpoint responses and setup files against the live contract.

- Trust score: 94/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `@dashboardbase/mcp`: 94/100 (this document), [markdown](https://verifymcp.io/servers/com-dashboardbase-mcp/dashboardbase-mcp.md), [page](https://verifymcp.io/servers/com-dashboardbase-mcp/dashboardbase-mcp)

## Channel facts

- Registry: `npm`
- Package: `@dashboardbase/mcp`
- Version: `1.0.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to dashboardbase/mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 47 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 360 tokens (~180/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add com-dashboardbase-mcp -- npx -y @dashboardbase/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-dashboardbase-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@dashboardbase/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-dashboardbase-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@dashboardbase/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-dashboardbase-mcp -- npx -y @dashboardbase/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-dashboardbase-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@dashboardbase/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-dashboardbase-mcp --command npx --arg -y --arg @dashboardbase/mcp
```

### Hermes

```yaml
mcp_servers:
  com-dashboardbase-mcp:
    command: "npx"
    args: ["-y", "@dashboardbase/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-dashboardbase-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@dashboardbase/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-dashboardbase-mcp -t stdio -c npx -a -y @dashboardbase/mcp
```

### Other

```json
{
  "mcpServers": {
    "com-dashboardbase-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@dashboardbase/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 94, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 93, −3)

- [functional] Stability: pass → 0.80

### 2026-09-17 (score 96, 0)

- [security] Stability: 0.97 → pass

### 2026-09-16 (score 96, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 95, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 94, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 93, −3)

- [functional] Stability: pass → 0.80

### 2026-09-10 (score 96, 0)

- [security] Stability: 0.97 → pass

## MCP tools (2)

### `validate_setup_file` (~123 tokens)

Validate Dashboardbase setup file

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.

Input parameters:

- `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.

Output parameters:

- `errors` (array): Problems that make the file invalid.
- `valid` (boolean): True when the setup file passes validation.
- `warnings` (array): Non-fatal advice about the file.

### `validate_widget_response` (~190 tokens)

Validate Dashboardbase widget response

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.

Input parameters:

- `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.

Output parameters:

- `errors` (array): Problems that make the response invalid.
- `valid` (boolean): True when the response passes validation.
- `widgetType` (string): The widget type the response was validated against.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-dashboardbase-mcp/dashboardbase-mcp#diagnostics

## Score history

- 2026-09-20: 94
- 2026-09-19: 94
- 2026-09-18: 93
- 2026-09-17: 96
- 2026-09-16: 96
- 2026-09-15: 95
- 2026-09-14: 95
- 2026-09-13: 94
- 2026-09-12: 94
- 2026-09-11: 93
- 2026-09-10: 96
- 2026-09-09: 96
- 2026-09-08: 95
- 2026-09-07: 95
- 2026-09-06: 94
- 2026-09-05: 94
- 2026-09-04: 93
- 2026-09-03: 96
- 2026-09-02: 96
- 2026-09-01: 95
- 2026-08-31: 95
- 2026-08-30: 94
- 2026-08-29: 94
- 2026-08-28: 93
- 2026-08-27: 93
- 2026-08-26: 92
- 2026-08-25: 91
- 2026-08-24: 91
- 2026-08-23: 90
- 2026-08-22: 90

## Common questions

### 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 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 2 tools: validate_setup_file, validate_widget_response. Their descriptions and schemas cost roughly 313 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 20 September 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.

## Links

- npm package: https://www.npmjs.com/package/@dashboardbase/mcp
- Socket report: https://socket.dev/npm/package/@dashboardbase/mcp
- Repository: https://github.com/dashboardbase/mcp
- Website: https://dashboardbase.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-dashboardbase-mcp/dashboardbase-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-dashboardbase-mcp/dashboardbase-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-dashboardbase-mcp/dashboardbase-mcp