@climeqai/mcp-server
OfficialRelated Servers
Alternatives to @climeqai/mcp-server
No user-submitted related servers found.
Related Servers
AlicenseBqualityDmaintenanceMCP server enabling AI assistants to automatically perform carbon footprint modeling, product queries, and emission analysis via the Carbonstop Cloud API.810 npmMIT
carbonstop-mcpofficial
FlicenseNot gradedqualityBmaintenanceEnables AI assistants to automatically call Carbonstop Cloud API for carbon footprint modeling, product query, and emission analysis through natural language.-- AlicenseAqualityBmaintenanceEnables AI agents to query verified-emissions knowledge graphs in natural language and validate data against supported standards, with metered billing and optional verified identity.16108 npmApache 2.0
- AlicenseAqualityFmaintenanceProvides 14 MCP tools for AI agent infrastructure, enabling knowledge base queries, skill search, handoffs, blueprint validation, trust scoring, identity verification, SLA validation, and compliance checks.22MIT
- AlicenseCqualityDmaintenance27 deterministic engineering compliance and calculation tools for the built environment (data-centre PUE and EED, EPBD, NIS2, Eurocode, UAE compliance), callable by AI agents via MCP and REST API. Free tier; every result cites the governing standard.27MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants such as Claude and Cursor to discover and verify agents, negotiate offers, execute conditional settlements, and verify receipts and complete multi-agent workflows through eight MCP tools.13 PyPI1MIT
TDQS
Scored across 23 tools
Most tools target a distinct scope/input type (electricity, fuel, freight, air travel, spend, PCF, CBAM, cloud), so an agent can generally pick correctly. The main gray zones are the generic climeq_calculate_emission vs climeq_valenq_estimate vs climeq_estimate_by_classification, and climeq_calculate_pcf vs climeq_screen_pcf_ai, where the boundary depends on input format rather than purpose.
All tools share a climeq_ prefix and snake_case with a predictable verb_noun shape (list_regions, calculate_fuel, verify_dpp), which is easy to parse. Minor deviation: the valenq_* trio uses a product namespace instead of a verb, and 'screen' vs 'calculate' vs 'estimate' are semantically close.
23 tools is on the heavy side, but the domain is genuinely broad (GHG Protocol scopes 1/2/3, PCF, CBAM, cloud, DPP) and each calculation tool covers a distinct methodology. Nothing looks like filler, though a couple of the general-purpose estimation tools could be folded into the core calculate tool.
Read paths for reference data and a wide set of calculation verbs are covered, but the private-factor lifecycle is create+list only with no update/delete, and there is no visible way to read back persisted calculations or ledger entries that climeq_calculate_emission writes. These are notable gaps that would force agents into dead ends for maintenance and reporting workflows.