CarbonMeld MCP server
Connect an MCP client with your Premium API key: project search, full records, offer checks, CORSIA supply and buyer profiles.
What it does
Give your assistant access to CarbonMeld project records and registry facts through the Model Context Protocol (MCP). The MCP handler runs no language model: your own assistant interprets the returned data. It reads CarbonMeld records and does not issue, buy or transfer carbon credits.
Five tools
search_projects
Inputs: query, registry, min_score, claim, limit (1–25; default 10)
Search by project-name words or registry code, with optional standard, score and claim filters. Returns identifiers, country, rating, registry status, claim tags and project URL.
get_project
Inputs: id (required)
Full available project record by slug or registry code, including analysis, red flags, vintages and claims. Premium details use the shared project quota.
check_offer
Inputs: text (required); vintage, quantity, seller (optional)
Compare pasted offer text with recorded registration, vintages, quantities, claims and developer. This does not confirm ownership or availability of a specific serial number.
corsia_supply
Inputs: None
CORSIA supply by registry and phase, based on registry labels, with the highest-rated First Phase projects.
get_buyer
Inputs: name (required; company name or buyer slug)
Public retirement records for an organisation: tonnes, projects and their quality. A retirement beneficiary is not necessarily the purchaser; ambiguous names require clarification.
search_projects claim values: corsia, corsia_first, ccp, ccp_meth, removal, article6. Labels reflect the records CarbonMeld holds.
Connect your client
Use an MCP client that lets you configure a remote server URL and a static Authorization header. Client interfaces differ; this guide does not claim compatibility with a specific application.
- Generate your key from the account box with an active pass.
- Set the remote server URL below and add the Authorization header with your own key.
- Connect, let the client list the tools, then ask it to search for a project before opening its full record.
Connection settings
https://carbonmeld.com/api/v1/mcp
Authorization: Bearer cmk_YOUR_KEY_HERETransport: JSON-RPC 2.0 over HTTP POST, with JSON responses. Opening the server URL with GET returns 405; it is not a web page.
Protocol version: 2025-06-18
Example: list the tools
curl 'https://carbonmeld.com/api/v1/mcp' \
-H 'Authorization: Bearer cmk_YOUR_KEY_HERE' \
-H 'Content-Type: application/json' \
--data '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Limits and fair use
- 300 requests per day per key by default, shared by REST and MCP.
- 30 different Premium projects per day, shared across the website, PDF reports, REST and MCP. Reopening the same project that day counts once. Portfolio projects and projects unlocked for you are exempt; public-only records do not consume this project quota.
- 20 offer checks per day per account, shared with the website offer checker.
Daily counters reset at 00:00 UTC. A burst limit also applies: 120 requests per minute per IP. List and statistics requests count towards the request limit, not the Premium project quota.
get_project uses the same Premium project quota as the REST API. MCP connection and tool requests also pass through the API request limiter.
Authentication and rate errors use HTTP status codes. A tool can return isError: true inside a successful HTTP response: read the tool result. A temporary data error is not a negative finding; retry later.
Data and privacy
Your client sends tool arguments, including any offer text you paste, to CarbonMeld. Returned records go back to your client, where your assistant does the reasoning. Share only the information needed for the check and review your client's data settings. CarbonMeld records use of pass features and Premium project access.
Same key as the REST API
Use the REST guide for direct HTTP requests, list parameters and error codes.
API guide