mcp-registry/com.greencalculus/api · v1.0.0
As of 2026-10-26 23:15 UTC, the Greencalculus MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Sourced carbon emission factors + audit-traced calculations an AI can cite.
Point your MCP client at this streamable-http endpoint: https://mcp.greencalculus.com
12 of 12 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
1 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.greencalculus%2Fapi/fixes
{
"name": "calculate_activity",
"description": "Turn activity data into greenhouse-gas emissions: emissions = activity × factor. Give an amount + unit and a factor key; the unit engine converts to the factor basis (MWh→kWh, tonne→kg, gallon→litre, mile→km) and returns the emissions with the working, the GHG Protocol scope, and the source. Use search_factors / lookup_factor to find the factor key.",
"inputSchema": {
"type": "object",
"required": [
"activity",
"factor_key"
],
"properties": {
"activity": {
"type": "object",
"description": "{ \"value\": <number>, \"unit\": \"<unit e.g. kWh, MWh, litres, tonne, km>\" }."
},
"factor_key": {
"type": "string",
"description": "Canonical emission-factor key."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "calculate_business_travel",
"description": "Business travel emissions (Scope 3 Cat 6), distance method: emissions = km × passengers × factor. Air factors come in with_rf / without_rf (radiative forcing) variants. Find factors via search_factors (section \"business_travel\").",
"inputSchema": {
"type": "object",
"required": [
"distance",
"factor_key"
],
"properties": {
"distance": {
"type": "object",
"description": "{ \"value\": <number>, \"unit\": \"km|mi\" }."
},
"factor_key": {
"type": "string",
"description": "Per-passenger-km travel factor key."
},
"passengers": {
"type": "number",
"description": "Optional, defaults to 1."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "calculate_electricity",
"description": "GHG Protocol Scope 2 for purchased electricity, both methods. Always returns location-based (grid-average) emissions; also returns market-based when you supply a contractual supplier_factor (e.g. a green tariff / REC = 0) or a market_factor_key (residual mix). Find grid keys via search_factors (section \"grid\").",
"inputSchema": {
"type": "object",
"required": [
"consumption",
"location_factor_key"
],
"properties": {
"consumption": {
"type": "object",
"description": "{ \"value\": <number>, \"unit\": \"kWh|MWh|GWh\" }."
},
"supplier_factor": {
"type": "object",
"description": "Optional contractual factor { value, unit } (wins over market_factor_key)."
},
"market_factor_key": {
"type": "string",
"description": "Optional: residual-mix / supplier grid factor key."
},
"location_factor_key": {
"type": "string",
"description": "Grid-average factor key, e.g. grid.gbr.electricity.location_based."
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.greencalculus/api"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.greencalculus/api"}) over MCP.
calculate_freight ~325 tokensresolve_factor ~285 tokensexplain_absence ~258 tokenscalculate_electricity ~254 tokenssearch_factors ~225 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.greencalculus%2Fapi?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.greencalculus%2Fapi?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.greencalculus%2Fapi.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.greencalculus%2Fapi.svg :target: https://glimind.com/server/mcp-registry%2Fcom.greencalculus%2Fapi?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:1cbf77777bc80f36…, first seen 2026-10-17, included at leaf 2863 of 76,031. Version history · verify what your client received.
Compare: most reliable data servers · most reliable finance servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 23:15 UTC, the Greencalculus MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Greencalculus MCP server advertises 12 tools, including calculate_activity, calculate_business_travel, calculate_electricity, calculate_embodied, calculate_freight.
Point your MCP client at this streamable-http endpoint: https://mcp.greencalculus.com
Glimind scanned all 12 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.