Validate emissions data against Open Footprint, check EU CBAM records, query verified methane data
Connect Remote server
claude mcp add --transport http semantic-mcp https://api.dveracity.com/mcp
{
"mcpServers": {
"semantic-mcp": {
"url": "https://api.dveracity.com/mcp"
}
}
}
{
"servers": {
"semantic-mcp": {
"type": "http",
"url": "https://api.dveracity.com/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://api.dveracity.com/mcp
Tools 23 found in our last check
semantic_queryUse this when a user asks a specific question about verified oil-and-gas emissions data, for example methane emissions for a site, company or period (PPDM, OGMP 2.0). Call semantic_templates first to see what the data can answer. Do not use for general climate questions. On paym…
semantic_templatesUse this when you want to see which kinds of questions the verified emissions data can answer, before calling semantic_query.
credits_balanceDeprecated: use billing_status, which also shows plan and free allowance. Removal planned for 0.9.
list_standardsUse this when you need to see which sustainability data standards and versions validate_data can check, before calling it.
validate_dataUse this when a user wants a payload checked against a standard other than Open Footprint; call list_standards first to see which are supported. For Open Footprint payloads use ofp_validate. Only masterData or referenceData; call list_standards first.
keri_identityUse this when an organisation needs to confirm which verified legal entity and agent identity dVeracity is attributing calls to. Only relevant when vLEI identity is configured.
ofp_modelsUse this when a user is building an app, database or integration on the Open Footprint standard and needs to know what the model covers. Start here before any other ofp_ tool. The response summary carries the served counts.
ofp_search_entitiesUse this when you need the Open Footprint entity for a concept such as "Scope 3 emissions", "facility" or "product footprint". Do not use for emission factors or calculations. Matches entity names, descriptions and field names; use ofp_entity for the full definition.
ofp_entityUse this when you need one entity's fields, types, keys and relationships, for example to design a table or an API payload. Pass domain when known: ambiguous names fail rather than guessing (ofp_models reports ambiguousNameCount).
ofp_sectorsUse this when a user asks which industries Open Footprint covers or whether a sector has a reference implementation. implemented means a reference implementation exists; planned or placeholder means nothing is published.
ofp_sectorUse this when you need one sector's classification, status and reference artifacts.
ofp_policiesUse this when a user asks which validation rules apply to a sector's emissions records. Do not use for regulations; use compliance_policies. inputs lists the e-ledger fields each policy reads (e.g. co2e_kg, direction), not canonical Open Footprint names. published:false means no…
compliance_policiesUse this when a user needs data checked against a regulation, for example EU CBAM, to find the approved policy to run. Do not use for Open Footprint sector rules; use ofp_policies. Returns only APPROVED policies; drafts and rejected never appear. An empty list means none publish…
compliance_policyUse this when you need the full rules, provenance and coverage of one approved regulatory policy. Returns Rego only when the source was retained; otherwise rego_unavailable: source_not_retained. A policy without Rego is not loaded into the engine; enforcement says whether its st…
compliance_evaluateUse this when a user wants an import record or an annual EU CBAM declaration (Reg. (EU) 2023/956) checked against an approved policy before filing. Do not use for carbon-footprint calculations or for regulations compliance_policies does not list. Runs the policy's regulation-der…
compliance_evaluationUse this when a user wants to retrieve or audit a previous regulatory evaluation by its id. Only the caller who ran it can read it; another account's id answers not found. Requires compliance:read.
compliance_policy_registerUse this when a user asks which provisions of a regulation an evaluation actually checks and which it does not. Shows which provisions are encoded and which are not: a pass on the encoded checks is not compliance with excluded provisions. Requires the compliance:read scope.
ofp_validateUse this when a user wants an emissions or footprint record (JSON) checked against the Open Footprint model or a sector's guardrails before storing, exchanging or reporting it. Do not use for general data-quality questions without a payload. Checks structure, declared constraint…
ofp_semanticsUse this when mapping fields from SAP, another ERP or a supplier feed onto Open Footprint. A high fieldCount is a generic fallback; pass maxFieldCount (10 is a good start) for codes specific enough to align on.
ofp_semantic_codeUse this when you have a source-system field and need to find where it belongs in the Open Footprint model. Codes carried by more than ten fields are generic classifications; aligning to one asserts less than it appears.
ofp_model_provenanceUse this when a user asks which version of the Open Footprint standard they are designing against.
billing_plansUse this when you need to know what each dVeracity plan includes or what the free allowance covers. Show dVeracity plans, what each plan includes and the free-tier allowance.
billing_statusUse this when a call was refused for credits or plan, to tell the user exactly what is missing. Use it after a 402 to tell your human exactly what is missing.
Details
| Endpoint | https://api.dveracity.com/mcp (Streamable HTTP) |
| Package | @dveracity/[email protected] (NPM, stdio) |
| First published | 3 Nov 2026 |
| Last updated | 3 Nov 2026 |
| Registry name | com.dveracity/semantic-mcp |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
