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.

Health Statistics

REMOTE · MONIT.LY

Health statistics for AI agents: life expectancy, causes of death, health spending, WHO data.

Available components

+3 this week 78 Trust /100

Last scanned (8 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 24 Oct 2026.

Category Health and Science

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 Security74
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 517 tokens (~129/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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.

  • 24 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.

  • 22 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.

  • 20 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.

  • 17 Oct 26 +1

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

  • 15 Oct 26 +1

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

  • 13 Oct 26 +1

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

  • 12 Oct 26 +1
    • Stability: unverified → 0.07 ▲ functional
  • 10 Oct 26 71

    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/health

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 No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

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/health Verified 200
http (plaintext) http://monit.ly/api/mcp/health HTTPS enforced 308 https://monit.ly/api/mcp/health
MCP tools · 4 exposed · ~436 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
get_dataset ~42

Full metadata for one dataset: description, source, period range, dimension labels, default view and covered countries.

NameTypeReqDescription
idintegeryesDataset id from search_catalog.

No output schema declared.

No examples provided.

get_series ~191

Time series values for one country from a dataset (oldest first). Optionally pick a series by exact dimension values (from inspect_dataset) and a start period such as 2015, Q1/2015 or 01/2015.

NameTypeReqDescription
countrystring–Country, e.g. 'Poland'. Defaults to the dataset's default country.
dim1string–Optional exact value of dimension 1.
dim2string–Optional exact value of dimension 2.
dim3string–Optional exact value of dimension 3.
dim4string–Optional exact value of dimension 4.
idintegeryesDataset id from search_catalog.
max_pointsinteger–Max points, most recent kept (default 200).
period_fromstring–Optional first period to include, e.g. '2015'.

No output schema declared.

No examples provided.

inspect_dataset ~67

Show one dataset's dimensions, default series and the latest few values for a country. Use after search_catalog to check the dataset fits before pulling the full series.

NameTypeReqDescription
countrystring–Optional country, e.g. 'France'.
idintegeryesDataset id from search_catalog.

No output schema declared.

No examples provided.

search_catalog ~136

Find official health datasets (Eurostat, OECD, World Bank, IMF, WHO, national statistics offices). Use first to get dataset ids. Optional country and source filters. Returns dataset cards, not values.

NameTypeReqDescription
countrystring–Optional country name to prefer datasets covering it, e.g. 'Germany'.
limitinteger–Max results (default 8).
querystringyesWhat to find, e.g. 'unemployment rate' or 'GDP per capita'.
source_namestring–Optional source, e.g. 'Eurostat', 'OECD', 'World Bank', 'IMF'.

No output schema declared.

No examples provided.

Install

How do I install the Health Statistics MCP server?

Health Statistics is a hosted endpoint at https://monit.ly/api/mcp/health, 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-health-statistics 'https://monit.ly/api/mcp/health'
Common questions

What is the Health Statistics MCP server?

Health Statistics is an MCP server listed in the public MCP registry as io.github.ContentWriterco/health-statistics. Health statistics for AI agents: life expectancy, causes of death, health spending, WHO data. This page covers its hosted endpoint (https://monit.ly/api/mcp/health).

Is the Health Statistics MCP server safe to use?

Health Statistics scores 78 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 Health Statistics MCP server expose?

Health Statistics exposes 4 tools: search_catalog, inspect_dataset, get_dataset, get_series. Their descriptions and schemas cost roughly 436 tokens of context every time the server is loaded.

Does the Health Statistics MCP server require authentication?

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

Is the Health Statistics MCP server still maintained?

Health Statistics 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.