Skip to content

DartMonitor

by dartmonitor.dev · remote · no sign-in to list tools · v0.1.0 · published by dev.dartmonitor

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

Changes · 3
CompareRegistry entry

3 tools: 3 change things.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http dart-monitor https://dartmonitor.dev/api/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Changes things 3Claude Code: ask
  • check_packageLooks up a Dart/Flutter package on pub.dev and reports its latest published version.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • check_packagesChecks up to 100 pub.dev packages at once, e.g.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • check_pubspecParses a pubspec.yaml file's contents and checks all dependencies and dev_dependencies against pub.dev, reporting which ones have updates available.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http dart-monitor https://dartmonitor.dev/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__dart-monitor__check_package",
      "mcp__dart-monitor__check_packages",
      "mcp__dart-monitor__check_pubspec"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as dart-monitor. Review it before you use it.