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.

fyi.carbon/carbon-fyi

REMOTE · WWW.CARBON.FYI · SCANNED SEP 22

Voluntary carbon market news and open carbon price data. Read-only, keyless.

Available components

+3 this week 80 Trust /100
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 Security63
Transport & Reachability100
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 630 tokens (~105/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
Install

How do I install the fyi.carbon/carbon-fyi MCP server?

fyi.carbon/carbon-fyi is a hosted endpoint at https://www.carbon.fyi/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 · www.carbon.fyi

# add to Claude Code
claude mcp add --transport http fyi-carbon-carbon-fyi 'https://www.carbon.fyi/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "fyi-carbon-carbon-fyi": {
      "url": "https://www.carbon.fyi/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "fyi-carbon-carbon-fyi": {
      "type": "http",
      "url": "https://www.carbon.fyi/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.fyi-carbon-carbon-fyi]
url = "https://www.carbon.fyi/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fyi-carbon-carbon-fyi": {
      "type": "remote",
      "url": "https://www.carbon.fyi/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add fyi-carbon-carbon-fyi --url 'https://www.carbon.fyi/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  fyi-carbon-carbon-fyi:
    url: "https://www.carbon.fyi/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "fyi-carbon-carbon-fyi": {
      "Transport": "http",
      "Url": "https://www.carbon.fyi/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add fyi-carbon-carbon-fyi -t streamable-http -u 'https://www.carbon.fyi/api/mcp'
// mcp.json
{
  "mcpServers": {
    "fyi-carbon-carbon-fyi": {
      "type": "http",
      "url": "https://www.carbon.fyi/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 21 Sept 26 +1

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

  • 19 Sept 26 +1

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

  • 17 Sept 26 +1

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

  • 15 Sept 26 +1

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

  • 13 Sept 26 +1

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

  • 10 Sept 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.

  • 8 Sept 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.

  • 6 Sept 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.

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 22 Sept 2026 · Probed https://www.carbon.fyi/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.carbon.fyi CN=YR2,O=Let's Encrypt,C=US 22 Sept 2026 21 Dec 2026 RSA 2048 SHA256-RSA 58b06ade3e0136d3123ad32e870bd23e3aa
SANs: www.carbon.fyi
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.carbon.fyi. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
fyi. present 24340 8 Verified
carbon.fyi. 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
Header Value
strict-transport-security max-age=63072000

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.carbon.fyi/api/mcp Verified 200
http (plaintext) http://www.carbon.fyi/api/mcp HTTPS enforced 308 https://www.carbon.fyi/api/mcp
MCP tools · 6 exposed · ~534 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_carbon_prices ~66

Current voluntary carbon credit prices from two independent sources: per-category minimum/median price and available supply across the Carbonmark marketplace catalog, and spot prices per Klima Protocol carbon class. The two are NOT comparable — read the `caveats` field on each before using either number.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_market_summary ~52

One call for orientation: how much of the archive is available, when it last updated, the story-tag breakdown (use these as `tag` values for search_news), and the current price table. Start here.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_price_history ~152

Daily-averaged historical price series. This archive exists only because carbon.fyi records it three times a day: no upstream API serves a historical carbon price series, so these observations cannot be obtained anywhere else and cannot be re-derived. Check `seriesStartsAt` in the response — the archive began on 2026-08-27, so early windows are necessarily short.

NameTypeReqDescription
daysintegerlook-back window in days (default 90)
keystringrestrict to one category or class name (exact match, as returned by get_carbon_prices); omit for all
kindstringyeswhich price source: marketplace category medians, or Klima carbon-class spot prices

No output schema declared.

No examples provided.

get_story ~65

Fetch a single story by its id, including every source that reported it. Story ids are permanent — a published story keeps its id and its public URL indefinitely — so they are safe to store.

NameTypeReqDescription
idstringyesthe story's `id`, as returned by search_news

No output schema declared.

No examples provided.

list_sources ~41

The publications, registries and integrity bodies carbon.fyi monitors. Useful for judging coverage — a topic absent from the archive may simply not be covered by these sources.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_news ~158

Search carbon.fyi's curated voluntary carbon market story archive. Each story is an editorially clustered summary of one development, written from one or more original reports, and always carries the original source name and URL. Supply at least one filter; results are newest-first. Use `get_market_summary` first if you do not know what tags or date range to ask for.

NameTypeReqDescription
limitintegermax stories to return (default 20, ceiling 50)
querystringcase-insensitive text match against headline and summary, e.g. 'Verra' or 'biochar'
sincestringonly stories first published on or after this UTC day
tagstringrestrict to one story category

No output schema declared.

No examples provided.

Common questions

What is the fyi.carbon/carbon-fyi MCP server?

fyi.carbon/carbon-fyi is an MCP server listed in the public MCP registry as fyi.carbon/carbon-fyi. Voluntary carbon market news and open carbon price data. Read-only, keyless. This page covers its hosted endpoint (https://www.carbon.fyi/api/mcp).

Is the fyi.carbon/carbon-fyi MCP server safe to use?

fyi.carbon/carbon-fyi scores 80 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 fyi.carbon/carbon-fyi MCP server expose?

fyi.carbon/carbon-fyi exposes 6 tools: search_news, get_story, get_carbon_prices, get_price_history, get_market_summary, list_sources. Their descriptions and schemas cost roughly 534 tokens of context every time the server is loaded.

Does the fyi.carbon/carbon-fyi MCP server require authentication?

No. We connected to fyi.carbon/carbon-fyi without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the fyi.carbon/carbon-fyi MCP server still maintained?

fyi.carbon/carbon-fyi is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.