dart-monitor
Registry code: 1eb07782299c19ed
Check Dart/Flutter dependencies on pub.dev for updates and manage monitored projects.
from a public catalogue that lists it, not from the operator
- endpoint
- https://dartmonitor.dev/api/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is dart-monitor live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is dart-monitor free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does dart-monitor have?
- 3 tools: check_packages, check_package, check_pubspec.
- Is dart-monitor safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.1%· all time 99.1%
last good check
of 3 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- check a dart package for updates
- check all pubspec dependencies
- check many packages at once
- takes → gives
- code, text → data
- tools
- 3 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
check_packages reads unknown 19h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "packages" ], "properties": { "packages": { "type": "array", "items": { "type": "object", "required": [ "name" ], "properties": { "name": { "type": "string" }, "currentVersion": { "type": "string" } } }, "maxItems": 100, "minItems": 1, "description": "List of {name, currentVersion?} pairs to check" }, "changelog": { "type": "boolean", "description": "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." } } }arguments 33 linescheck_package reads unknown 19h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "packageName" ], "properties": { "changelog": { "type": "boolean", "description": "Include changelog HTML in the response. Defaults to false; only set this once you actually need the changelog text, since it can be large." }, "packageName": { "type": "string", "description": "The pub.dev package name, e.g. \"http\" or \"provider\"" }, "currentVersion": { "type": "string", "description": "The version currently installed, e.g. \"1.2.3\". Omit to just fetch the latest version." } } }arguments 21 linescheck_pubspec reads unknown 19h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "pubspecYaml" ], "properties": { "changelog": { "type": "boolean", "description": "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": { "type": "string", "description": "The full raw text contents of a pubspec.yaml file" } } }arguments 17 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id1eb07782299c19ed.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/1eb07782299c19ed/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/1eb07782299c19ed?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.