carbon-factor-matcher
Registry code: 8b8a24068e8bf716
MCP server for intelligent emission factor matching from ELCD and ecoinvent databases. Supports carbon accounting, LCA, and ESG reporting with AI-powered semantic search and 5-dimension data quality assessment.
from a public catalogue that lists it, not from the operator
- endpoint
- https://zerocarbonlogic.com/mcp
- protocol
- streamable-http ·2024-11-05
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is carbon-factor-matcher live?
- Yes — it answered the hub's last check (checked 11m ago). It answered 98% of checks over the last 30 days.
- Is carbon-factor-matcher free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does carbon-factor-matcher have?
- 3 tools: factor_detail, factor_match, factor_search.
- Is carbon-factor-matcher safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 98.5%· all time 98.5%
last good check
of 3 tools
- down → live
- degraded → down· timeout after 20000ms
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- match an activity to emission factors
- search emission factor databases
- get emission factor details
- takes → gives
- text → data
- tools
- 3 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
factor_detail reads unknown 6h ago
Retrieve full metadata for a specific emission factor by its unique identifier. Returns emission intensity value, unit, geographic scope, applicability conditions, data source, and publication year.
{ "type": "object", "required": [ "factor_id" ], "properties": { "factor_id": { "type": "string", "description": "Unique identifier of the emission factor, as returned by factor_match or factor_search. Example: 'urn:uuid:bab6dd4e-a2ea-4fd9-a585-e8edafcb42e1'." } } }arguments 12 linesfactor_match reads unknown 6h ago
Match a natural-language description of an industrial activity or material to emission factors for carbon accounting and Life Cycle Assessment (LCA). Returns ranked candidate factors with CO2-equivalent intensity and relevance scores; the calling agent selects the best match. Keyword search over ELCD (493 European factors) + US LCI (555 US factors) + USDA LCA Commons (1,550 US agricultural factors). ecoinvent (5,601 global factors) requires a Pro license (pass source="all"). Embedding-based semantic re-ranking runs in the local Python MCP server of the same package, not in this hosted endpoint.
{ "type": "object", "required": [ "activity_data" ], "properties": { "top_k": { "type": "integer", "default": 10, "description": "Number of candidate factors to consider (1-50). Default: 10." }, "activity_data": { "type": "string", "description": "Natural-language description of the activity, material, or process to match. Examples: 'Factory in Shenzhen, 10kV industrial electricity, 2024, semiconductor fab', 'diesel combustion for freight transport, EU', 'cement production, rotary kiln'. IMPORTANT: The database is in English. If the user input is in another language, translate to English keywords before querying (e.g. 水泥→cement, 柴油→diesel, Zement→cement)." } } }arguments 17 linesfactor_search reads unknown 6h ago
Keyword search over emission factor databases. Returns matching factors with metadata including CO2-equivalent intensity (kgCO2e per unit), unit, geographic scope, source, and publication year. Supports optional category filtering (e.g. 'electricity', 'fuel', 'transport', 'chemicals'). Free tier: ELCD + US LCI + USDA. Pro tier: all databases (pass source="all").
{ "type": "object", "required": [ "query" ], "properties": { "limit": { "type": "integer", "default": 10, "description": "Maximum number of results to return (1-50). Default: 10." }, "query": { "type": "string", "description": "Search keyword — material name, industrial process, or activity type (in English). Examples: 'electricity', 'diesel', 'transport', 'cement', 'polyethylene'. IMPORTANT: The database is in English. Translate non-English terms to English before querying (e.g. 聚乙烯→polyethylene, 水泥→cement, Stahl→steel)." }, "category": { "type": "string", "description": "Optional category filter to narrow results. Common categories: 'electricity', 'fuel', 'transport', 'chemicals', 'metals', 'construction'." } } }arguments 21 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id8b8a24068e8bf716.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/8b8a24068e8bf716/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/8b8a24068e8bf716?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.