Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Monitly

REMOTE · MONIT.LY

Official statistics for AI agents: Eurostat, World Bank, OECD, IMF and WHO data for 150+ countries.

Available components

+3 this week 82 Trust /100

Last scanned (13 hours ago)

Scores higher than 88% of remote servers

Reachable. Last reached 24 Oct 2026.

Category Data and Analytics

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security83
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1393 tokens (~66/item across 21 items; 21 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety94
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 3 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_sql" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 22 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
Changelog

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.

  • 22 Oct 26 +1

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

  • 20 Oct 26 +1

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

  • 18 Oct 26 +1

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

  • 16 Oct 26 +1

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

  • 14 Oct 26 +1

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

  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 13. That category is still filling its 30-day observation window: 2 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.

  • 10 Oct 26 +1
    • Stability: unverified → 0.07 ▲ functional
  • 8 Oct 26 75

    First indexed and scored.

Diagnostics

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 24 Oct 2026 · Probed https://monit.ly/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=monit.ly CN=WE1,O=Google Trust Services,C=US 2 Oct 2026 31 Dec 2026 ECDSA 256 ECDSA-SHA256 ba03a241ddabe18513dcef8ddc96343a
SANs: monit.ly, *.monit.ly
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of monit.ly. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ly. present 62311 8 Verified
monit.ly. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

Protected resource metadata

Retrieved No
Problem no_resource_metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://monit.ly/api/mcp Verified 200
http (plaintext) http://monit.ly/api/mcp HTTPS enforced 308 https://monit.ly/api/mcp
MCP tools · 21 exposed · ~1,251 tokens

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 →

Tool Tokens
add_to_watchlist ~54

Follow a dataset by id (from search_catalog). The user gets alerts when it updates. Respects the plan's watchlist limit.

NameTypeReqDescription
dataset_idintegeryesDataset id (main.id) from search_catalog.

No output schema declared.

No examples provided.

add_watchlist_batch ~48

Follow up to 100 datasets in one call. Skips duplicates and stops at the plan limit (reported in skipped_limit).

NameTypeReqDescription
dataset_idsarrayyesDataset ids (main.id).

No output schema declared.

No examples provided.

create_api_key ~56

Create a REST API key (mon_…) for /api endpoints. The raw key is returned once. Limit: 3 (Essential) / 10 (Pro).

NameTypeReqDescription
namestring–Label (max 100 chars).

No output schema declared.

No examples provided.

create_mcp_key ~48

Create another MCP key (mcpk_…), e.g. for a second client. The raw key is returned once.

NameTypeReqDescription
namestring–Label (max 100 chars).

No output schema declared.

No examples provided.

delete_api_key ~43

Revoke a REST API key by id. The last remaining key cannot be deleted.

NameTypeReqDescription
key_idstringyesKey id (uuid) from the list call.

No output schema declared.

No examples provided.

delete_mcp_key ~47

Revoke an MCP key by id. The key used for the current session cannot be revoked here.

NameTypeReqDescription
key_idstringyesKey id (uuid) from the list call.

No output schema declared.

No examples provided.

execute_sql ~61

Run a read-only SELECT (or WITH … SELECT) against tables main and data only. Use after search_catalog + inspect_dataset to pull the time series for a known data.id / main_id.

NameTypeReqDescription
querystringyesSQL SELECT against main / data only.

No output schema declared.

No examples provided.

export_dataset ~97

Return a CSV download URL for a dataset, optionally filtered by countries and dimension values (dim1…dim8 from inspect_dataset).

NameTypeReqDescription
countriesarray–Country names, e.g. ['Poland','Germany'].
dataset_idintegeryesDataset id (main.id) from search_catalog.
dimensionsobject–Dimension filters, e.g. {"dim1": ["Annual"], "dim2": ["Percentage"]}.

No output schema declared.

No examples provided.

get_dataset ~39

Get one dataset metadata row from main by id (includes dimensions, default_view, geos).

NameTypeReqDescription
idintegeryesDataset id (main.id).

No output schema declared.

No examples provided.

get_plan ~36

Current plan of the key owner: name, status, period end and limits (API/day, MCP/month, watchlist, API keys).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_usage ~29

MCP queries this billing period, REST API requests today and watchlist slots — used, limit, remaining.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

inspect_dataset ~88

Peek one dataset by main.id: default slice, whether a country is in the series, dataId, and the last few values. Uses indexed main_id lookup — do not scan the data table yourself for discovery.

NameTypeReqDescription
countrystring–Optional country to resolve in the format header (e.g. 'Germany').
idintegeryesDataset id (main.id) from search_catalog.

No output schema declared.

No examples provided.

list_api_keys ~32

Active REST API keys (mon_…) of the account: id, name, prefix, created/last used.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_mcp_keys ~30

Active MCP keys (mcpk_…). The key used for this session is marked current=true.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_plans ~26

List Monitly plans (Essential, Pro, Enterprise) with prices and limits.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_watchlist ~60

Datasets the user follows (watchlist) with source, latest period and alert status. Paginate with limit/offset.

NameTypeReqDescription
limitinteger–Max rows (default 20).
offsetinteger–Pagination offset (default 0).

No output schema declared.

No examples provided.

remove_from_watchlist ~34

Unfollow a dataset by id.

NameTypeReqDescription
dataset_idintegeryesDataset id (main.id) from search_catalog.

No output schema declared.

No examples provided.

search_catalog ~161

Find statistical datasets in the catalog (Eurostat, World Bank, OECD, etc.). Index-backed hybrid search (name/code + embeddings). Optional country and source_name filters. Use this instead of SELECT … FROM main ILIKE. Returns compact cards, not series values.

NameTypeReqDescription
countrystring–Optional country name to prefer datasets that include this geo (e.g. 'Germany').
limitinteger–Max cards (default 8, max 16).
querystringyesWhat to find, e.g. 'GDP annual current prices' or 'unemployment rate'.
source_namestring–Optional source filter, e.g. 'Eurostat', 'World Bank' (World Development Indicators), 'OECD', 'IMF'.

No output schema declared.

No examples provided.

search_datasets ~96

Alias of search_catalog. Find statistical datasets by query, optional country and source_name.

NameTypeReqDescription
countrystring–Optional country name (e.g. 'Germany').
limitinteger–Max cards (default 8, max 16).
querystringyesWhat to find, e.g. 'GDP annual current prices'.
source_namestring–Optional source filter, e.g. 'Eurostat'.

No output schema declared.

No examples provided.

set_notification_preferences ~119

action='get' returns e-mail/Slack alert settings. action='set' changes email_notifications / slack_notifications, or turns alerts for one followed dataset on/off (dataset_id + dataset_notifications).

NameTypeReqDescription
actionstringyes'get' or 'set'.
dataset_idinteger–Followed dataset to change.
dataset_notificationsboolean–Alerts for that dataset on/off.
email_notificationsboolean–E-mail alerts for followed datasets.
slack_notificationsboolean–Slack alerts (webhook is configured in Settings).

No output schema declared.

No examples provided.

upgrade_plan ~47

Create a Stripe Checkout session for the Pro plan and return checkout_url. Open it in the browser for the user to pay.

NameTypeReqDescription
plan_idstring–Target plan (default 'pro').

No output schema declared.

No examples provided.

Install

How do I install the Monitly MCP server?

Monitly is a hosted endpoint at https://monit.ly/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.

remote · monit.ly

# add to Claude Code
claude mcp add --transport http contentwriterco-monitly 'https://monit.ly/api/mcp'
Common questions

What is the Monitly MCP server?

Monitly is an MCP server listed in the public MCP registry as io.github.ContentWriterco/monitly. Official statistics for AI agents: Eurostat, World Bank, OECD, IMF and WHO data for 150+ countries. This page covers its hosted endpoint (https://monit.ly/api/mcp).

Is the Monitly MCP server safe to use?

Monitly scores 82 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 Monitly MCP server expose?

Monitly exposes 21 tools: search_catalog, search_datasets, inspect_dataset, get_dataset, execute_sql, and 16 more. Their descriptions and schemas cost roughly 1,251 tokens of context every time the server is loaded.

Does the Monitly MCP server require authentication?

Yes. Monitly asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Monitly MCP server still maintained?

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