ICOS carbon and greenhouse-gas observations
REMOTE · MCP.ICOS-CP.EU
ICOS atmosphere, ocean and ecosystem greenhouse-gas observations, with citation and DOI per answer
Available components
Last scanned (22 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Health and Science
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 Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2357 tokens (~214/item across 11 items; 8 tools + 3 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 52% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 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.
- 2 Nov 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.
- 31 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 70
First indexed and scored.
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 4 Nov 2026 · Probed https://mcp.icos-cp.eu/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.icos-cp.eu | CN=YE2,O=Let's Encrypt,C=US | 30 Oct 2026 | 28 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6a717f7a0399a3895171167f2300889270e |
| SANs: mcp.icos-cp.eu | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.icos-cp.eu. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| eu. | present | 35926 | 8 | Verified |
| icos-cp.eu. | present | 11930, 15112 | 13, 13 | Verified |
| mcp.icos-cp.eu. | Verified address RRset verified with the apex keys |
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://mcp.icos-cp.eu/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.icos-cp.eu/mcp | HTTPS enforced | 308 | https://mcp.icos-cp.eu/mcp |
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 →
aggregate ~391
Statistics over a WHOLE selection, computed on the server: count, mean, min, max, sum and standard deviation of one variable, overall or per station, year, month or day. Use this for any average, total, range or trend instead of reading rows. Any size: a selection over 500,000 rows is split by time on the server and merged exactly. `std` is the POPULATION standard deviation (ddof 0). `sum` adds the values as stored, which is a total only for values that are themselves totals per row: summing a RATE (umol m-2 s-1 per half-hour, gC m-2 d-1 per day) or a concentration gives no physical quantity -- for a flux total multiply the mean by the period.
| Name | Type | Req | Description |
|---|---|---|---|
| apply_qc | boolean | – | DEFAULT TRUE: drop the observations the store's recommended quality control rejects; false keeps every observation, flagged ones included |
| by | string | – | the groups: none (one result), station, a period, or both |
| cruise | – | – | cruise expocodes, a list or a string; ocean observation tables only |
| end | – | – | ISO date or datetime, EXCLUSIVE |
| height_max | – | – | – |
| height_min | – | – | – |
| id | string | yes | a variable id from search_variables |
| lat_max | – | – | – |
| lat_min | – | – | – |
| lon_max | – | – | – |
| lon_min | – | – | – |
| start | – | – | ISO date or datetime, inclusive (2025-01-01) |
| station | – | – | station ids -- a list, or one id (or several, comma-separated) as a string; CASE-SENSITIVE: HTM150 (trigram + sampling height) for atmosphere, SE-Htm for FLUXNET sites |
| Name | Type | Req | Description |
|---|---|---|---|
| by | string | yes | – |
| citation | – | yes | – |
| download_complete | boolean | – | – |
| download_url | string | yes | – |
| download_urls | – | – | – |
| groups | array | yes | one entry per group: its keys (station, period), n (finite values), and mean, min, max, sum, std over them (null when n is 0) |
| id | string | yes | – |
| n_groups | integer | yes | – |
| note | – | – | – |
| rows_used | integer | yes | – |
| unit | – | – | – |
| variable | string | yes | – |
No examples provided.
describe_variable ~94
One variable in full: names, unit, which dataset, its coverage, how its quality flag is read, licence and DOI. For a multi-dimensional variable read through zarr (access 'zarr'), its axes with their labels, the slice /query serves (prescribed) and an xarray line for any other slice.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | a variable id from search_variables |
| Name | Type | Req | Description |
|---|---|---|---|
| access | string | – | query: estimate/get_data/aggregate serve it; zarr: a multi-dimensional variable (e.g. the ONEFlux NEE cube) read with xarray -- see zarr_recipe, and `prescribed` for its /query slice |
| axes | – | – | zarr variables: each extra axis and its labels |
| dataset_title | string | yes | – |
| doi | – | – | – |
| domain | – | – | – |
| id | string | yes | – |
| license | – | – | – |
| long_name | – | – | – |
| name | string | yes | – |
| prescribed | – | – | zarr variables: the id of the preferred slice /query serves |
| quality_control | – | – | how the store's QC flag is read; apply_qc=true applies the recommended rule |
| quality_flag | – | – | – |
| query_kind | string | yes | station_time (series at stations), obs_table (ship/cruise observations) or grid (gridded product) |
| store | string | yes | – |
| time_coverage_end | – | – | – |
| time_coverage_start | – | – | – |
| unit | – | – | – |
| variants | – | – | the multi-dimensional variables this one is the PRESCRIBED slice of; their other slices are read through zarr (describe_variable on one gives the recipe) |
| vocabulary_uri | – | – | – |
| zarr_recipe | – | – | – |
No examples provided.
estimate ~213
How big a selection is -- rows, stations, time span -- without fetching it. Call this before get_data.
| Name | Type | Req | Description |
|---|---|---|---|
| apply_qc | boolean | – | DEFAULT TRUE: drop the observations the store's recommended quality control rejects; false keeps every observation, flagged ones included |
| cruise | – | – | cruise expocodes, a list or a string; ocean observation tables only |
| end | – | – | ISO date or datetime, EXCLUSIVE |
| height_max | – | – | – |
| height_min | – | – | – |
| id | string | yes | a variable id from search_variables |
| lat_max | – | – | – |
| lat_min | – | – | – |
| lon_max | – | – | – |
| lon_min | – | – | – |
| start | – | – | ISO date or datetime, inclusive (2025-01-01) |
| station | – | – | station ids -- a list, or one id (or several, comma-separated) as a string; CASE-SENSITIVE: HTM150 (trigram + sampling height) for atmosphere, SE-Htm for FLUXNET sites |
| Name | Type | Req | Description |
|---|---|---|---|
| est_bytes | – | – | – |
| exact | boolean | yes | – |
| id | string | yes | – |
| n_stations | – | – | – |
| note | – | – | – |
| rows | – | yes | rows the selection holds; None when only an upper bound is known |
| rows_at_most | – | – | – |
| time_max | – | – | – |
| time_min | – | – | – |
No examples provided.
find_stations ~186
The stations that carry a variable: id, name, position, sampling height, country, ecosystem -- near a point (sorted by distance), in a box, by name or by country. The ids are what estimate and get_data take as station=.
| Name | Type | Req | Description |
|---|---|---|---|
| country | – | – | two-letter code, e.g. SE |
| id | string | yes | a station-based variable id from search_variables |
| lat_max | – | – | – |
| lat_min | – | – | – |
| limit | integer | – | – |
| lon_max | – | – | – |
| lon_min | – | – | – |
| near_lat | – | – | search around this point, with near_lon and radius_km |
| near_lon | – | – | – |
| radius_km | number | – | – |
| text | – | – | part of a station's id or name, e.g. 'Hyltemossa', 'HTM', 'Hyy' |
| Name | Type | Req | Description |
|---|---|---|---|
| n_matches | integer | yes | – |
| stations | array | yes | – |
| variable | string | yes | – |
No examples provided.
get_citation ~197
How to cite a variable's data: the citation text, licence and DOI from its data passport, and -- for a selection (stations, a time window, a box) -- every data object it came from, in full. Data answers carry a short citation and only the COUNT of their sources; this lists them.
| Name | Type | Req | Description |
|---|---|---|---|
| end | – | – | ISO date or datetime, EXCLUSIVE |
| id | string | yes | a variable id from search_variables |
| lat_max | – | – | – |
| lat_min | – | – | – |
| lon_max | – | – | – |
| lon_min | – | – | – |
| start | – | – | ISO date or datetime, inclusive (2025-01-01) |
| station | – | – | station ids -- a list, or one id (or several, comma-separated) as a string; CASE-SENSITIVE: HTM150 (trigram + sampling height) for atmosphere, SE-Htm for FLUXNET sites |
| Name | Type | Req | Description |
|---|---|---|---|
| citation | – | – | – |
| doi | – | – | – |
| license | – | – | – |
| license_url | – | – | – |
| n_sources | – | – | how many data objects the selection came from; in a data answer their citations are listed only when there are three or fewer -- get_citation (with the same stations) lists them all |
| selection_id | – | – | stable id of this exact selection over this exact store version |
| sources | – | – | the citation of each data object the selection came from -- what to cite when there is no collection citation (near-real-time data) |
| store_version | – | – | – |
No examples provided.
get_data ~269
Observations for one variable, filtered by box, time, station, cruise, height and quality control. Returns at most max_rows rows as a table, the total, a download URL for the whole selection, and the citation the user must be given with any use of the data.
| Name | Type | Req | Description |
|---|---|---|---|
| apply_qc | boolean | – | DEFAULT TRUE: drop the observations the store's recommended quality control rejects; false keeps every observation, flagged ones included |
| cruise | – | – | cruise expocodes, a list or a string; ocean observation tables only |
| end | – | – | ISO date or datetime, EXCLUSIVE |
| height_max | – | – | – |
| height_min | – | – | – |
| id | string | yes | a variable id from search_variables |
| lat_max | – | – | – |
| lat_min | – | – | – |
| lon_max | – | – | – |
| lon_min | – | – | – |
| max_rows | integer | – | rows to return; the whole selection is at download_url |
| start | – | – | ISO date or datetime, inclusive (2025-01-01) |
| station | – | – | station ids -- a list, or one id (or several, comma-separated) as a string; CASE-SENSITIVE: HTM150 (trigram + sampling height) for atmosphere, SE-Htm for FLUXNET sites |
| Name | Type | Req | Description |
|---|---|---|---|
| citation | – | yes | – |
| columns | array | yes | – |
| download_complete | boolean | – | false when no set of links could be planned to cover the whole selection; the note says what is missing |
| download_url | string | yes | the selection as CSV when it fits one download; when it does not, the FIRST of download_urls |
| download_urls | – | – | when the selection is larger than one download (the proxy caps an answer at 500,000 rows): one CSV link per time window, together the WHOLE selection -- give the user all of them |
| id | string | yes | – |
| note | – | – | – |
| rows | array | yes | – |
| rows_returned | integer | yes | – |
| rows_total | – | yes | rows in the whole selection, when known |
| truncated | boolean | yes | – |
No examples provided.
list_datasets ~41
List the ICOS datasets: one per data store, with domain (atmosphere, ocean, ecosystem), time and space coverage, licence and DOI.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| datasets | array | yes | – |
No examples provided.
search_variables ~130
Find variable ids in the ICOS catalogue by name, quantity or unit. The ids are what estimate and get_data take. Primary measurements come before their companions (standard deviation, value counts, flags).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | – | – | atmosphere, ocean or ecosystem |
| limit | integer | – | – |
| store | – | – | limit to one store, e.g. icos-obspack.zarr |
| text | string | yes | what to look for: a gas, a quantity or a name, e.g. 'co2', 'methane', 'net ecosystem exchange', 'fCO2' |
| Name | Type | Req | Description |
|---|---|---|---|
| n_matches | integer | yes | – |
| variables | array | yes | – |
No examples provided.
How do I install the ICOS carbon and greenhouse-gas observations MCP server?
ICOS carbon and greenhouse-gas observations is a hosted endpoint at https://mcp.icos-cp.eu/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 · mcp.icos-cp.eu
claude mcp add --transport http eu-icos-cp-icos 'https://mcp.icos-cp.eu/mcp'
What is the ICOS carbon and greenhouse-gas observations MCP server?
ICOS carbon and greenhouse-gas observations is an MCP server listed in the public MCP registry as eu.icos-cp/icos. ICOS atmosphere, ocean and ecosystem greenhouse-gas observations, with citation and DOI per answer. This page covers its hosted endpoint (https://mcp.icos-cp.eu/mcp).
Is the ICOS carbon and greenhouse-gas observations MCP server safe to use?
ICOS carbon and greenhouse-gas observations scores 73 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 ICOS carbon and greenhouse-gas observations MCP server expose?
ICOS carbon and greenhouse-gas observations exposes 8 tools: list_datasets, search_variables, describe_variable, estimate, get_data, and 3 more. Their descriptions and schemas cost roughly 1,521 tokens of context every time the server is loaded.
Does the ICOS carbon and greenhouse-gas observations MCP server require authentication?
No. We connected to ICOS carbon and greenhouse-gas observations without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ICOS carbon and greenhouse-gas observations MCP server still maintained?
ICOS carbon and greenhouse-gas observations is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.