# DartMonitor (remote · dartmonitor.dev)

Check Dart/Flutter dependencies on pub.dev for updates and manage monitored projects.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `dartmonitor.dev`: 67/100 (this document), [markdown](https://verifymcp.io/servers/dev-dartmonitor-dart-monitor/api-mcp.md), [page](https://verifymcp.io/servers/dev-dartmonitor-dart-monitor/api-mcp)

## Channel facts

- Endpoint: `https://dartmonitor.dev/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-28.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 517 tokens (~172/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 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 DartMonitor MCP server?

DartMonitor is a hosted endpoint at https://dartmonitor.dev/api/mcp, so there is nothing to install locally. 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 --transport http dev-dartmonitor-dart-monitor 'https://dartmonitor.dev/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-dartmonitor-dart-monitor": {
      "url": "https://dartmonitor.dev/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-dartmonitor-dart-monitor": {
      "type": "http",
      "url": "https://dartmonitor.dev/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-dartmonitor-dart-monitor]
url = "https://dartmonitor.dev/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-dartmonitor-dart-monitor": {
      "type": "remote",
      "url": "https://dartmonitor.dev/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-dartmonitor-dart-monitor --url 'https://dartmonitor.dev/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-dartmonitor-dart-monitor:
    url: "https://dartmonitor.dev/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-dartmonitor-dart-monitor": {
      "Transport": "http",
      "Url": "https://dartmonitor.dev/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-dartmonitor-dart-monitor -t streamable-http -u 'https://dartmonitor.dev/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-dartmonitor-dart-monitor": {
      "type": "http",
      "url": "https://dartmonitor.dev/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-28 (score 67, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 67, +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.

### 2026-09-25 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-23 (score 65)

First indexed and scored.

## MCP tools (3)

### `check_package` (~185 tokens)

Check a pub.dev package for updates

Looks up a Dart/Flutter package on pub.dev and reports its latest published version. If currentVersion is given, also reports whether an update is available. Changelog HTML for versions newer than currentVersion is left out unless changelog is set to true - if one exists and was left out, the result says so (changelogAvailable: true), so call again with changelog: true to get it. No account needed.

Input parameters:

- `changelog` (boolean): Include changelog HTML in the response. Defaults to false; only set this once you actually need the changelog text, since it can be large.
- `currentVersion` (string): The version currently installed, e.g. "1.2.3". Omit to just fetch the latest version.
- `packageName` (string, required): The pub.dev package name, e.g. "http" or "provider"

### `check_packages` (~167 tokens)

Batch-check pub.dev packages for updates

Checks up to 100 pub.dev packages at once, e.g. every dependency in a project. Useful after reading a pubspec.yaml's dependencies/dev_dependencies by hand; prefer check_pubspec when you have the raw pubspec.yaml text. Changelog HTML is left out of each result unless changelog is set to true - if any of them have one, the response says how many (changelogsAvailable) and reminds you to call again with changelog: true. No account needed.

Input parameters:

- `changelog` (boolean): Include changelog HTML in each result. Defaults to false; only set this once you actually need the changelog text, since it can be large across a whole batch.
- `packages` (array, required): List of {name, currentVersion?} pairs to check

### `check_pubspec` (~165 tokens)

Check every dependency in a pubspec.yaml for updates

Parses a pubspec.yaml file's contents and checks all dependencies and dev_dependencies against pub.dev, reporting which ones have updates available. Changelog HTML is left out of each dependency unless changelog is set to true - if any of them have one, the response says how many (changelogsAvailable) and reminds you to call again with changelog: true. This does not save anything - pass the raw file contents, not a file path. No account needed.

Input parameters:

- `changelog` (boolean): Include changelog HTML for each dependency. Defaults to false; only set this once you actually need the changelog text, since it can be large across a whole pubspec.
- `pubspecYaml` (string, required): The full raw text contents of a pubspec.yaml file

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-dartmonitor-dart-monitor/api-mcp#diagnostics

## Score history

- 2026-09-28: 67
- 2026-09-27: 67
- 2026-09-26: 66
- 2026-09-25: 66
- 2026-09-24: 65
- 2026-09-23: 65

## Common questions

### What is the DartMonitor MCP server?

DartMonitor is an MCP server listed in the public MCP registry as dev.dartmonitor/dart-monitor. Check Dart/Flutter dependencies on pub.dev for updates and manage monitored projects. This page covers its hosted endpoint (https://dartmonitor.dev/api/mcp).

### Is the DartMonitor MCP server safe to use?

DartMonitor scores 67 out of 100 on VerifyMCP. 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 DartMonitor MCP server expose?

DartMonitor exposes 3 tools: check_package, check_packages, check_pubspec. Their descriptions and schemas cost roughly 517 tokens of context every time the server is loaded.

### Does the DartMonitor MCP server require authentication?

No. We connected to DartMonitor without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the DartMonitor MCP server still maintained?

DartMonitor is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://dartmonitor.dev/api/mcp
- Website: https://dartmonitor.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-dartmonitor-dart-monitor/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-dartmonitor-dart-monitor/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-dartmonitor-dart-monitor/api-mcp