dVeracity Semantic API MCP server
com.dveracity/semantic-mcpdveracity.comstreamable-httpv0.8.3Scanned
Validate emissions data against Open Footprint, check EU CBAM records, query verified methane data
23 tools: 17 change things and 6 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
17 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the dVeracity Semantic API MCP server can do
The dVeracity Semantic API MCP server is published by dveracity.com, a domain the MCP Registry verified. It has 23 tools. It can create or change data (17 tools: semantic_templates, credits_balance, keri_identity, ofp_models and 13 more), but cannot delete data. 6 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.
Last scanned Nov 16, 2026, version 0.8.3.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
23 tools
Changes things 17Claude Code: ask
billing_plansUse this when you need to know what each dVeracity plan includes or what the free allowance covers.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
compliance_evaluateUse this when a user wants an import record or an annual EU CBAM declaration (Reg.No findings
Why it is in this group
- The name "compliance_evaluate" says "evaluate": a word for a change.
Description, as the server wrote it Use 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-derived Rego, not the generic OFP validator. The decision is passed, denied, unevaluable, not_applicable or error; an error is a refusal, never compliance, and error.code names it (policy_not_release_eligible, policy_no_rendered_checks, policy_no_faithful_checks, policy_coverage_inconsistent, policy_hash_mismatch, policy_hash_unverified). A pass covers only the encoded checks: read coverage.note. Requires the compliance:evaluate scope; every call counts against the plan limit. For an annual CBAM declaration set entity_type to cbam_declaration and send declaration + lines.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
compliance_evaluationUse this when a user wants to retrieve or audit a previous regulatory evaluation by its id.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
compliance_policiesUse this when a user needs data checked against a regulation, for example EU CBAM, to find the approved policy to run.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use 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 published, not that no obligations exist; never invent rules. Requires compliance:read.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
compliance_policyUse this when you need the full rules, provenance and coverage of one approved regulatory policy.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use 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 structured rules still run. Do not reconstruct the Rego. Requires compliance:read.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
compliance_policy_registerUse this when a user asks which provisions of a regulation an evaluation actually checks and which it does not.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
credits_balanceDeprecated: use billing_status, which also shows plan and free allowance.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Deprecated: use billing_status, which also shows plan and free allowance. Removal planned for 0.9.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
keri_identityUse this when an organisation needs to confirm which verified legal entity and agent identity dVeracity is attributing calls to.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
ofp_entityUse this when you need one entity's fields, types, keys and relationships, for example to design a table or an API payload.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use 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).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ofp_model_provenanceUse this when a user asks which version of the Open Footprint standard they are designing against.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use this when a user asks which version of the Open Footprint standard they are designing against.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ofp_policiesUse this when a user asks which validation rules apply to a sector's emissions records.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use 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 rules are published; do not invent guardrails.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ofp_sectorUse this when you need one sector's classification, status and reference artifacts.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use this when you need one sector's classification, status and reference artifacts.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ofp_sectorsUse this when a user asks which industries Open Footprint covers or whether a sector has a reference implementation.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ofp_semantic_codeUse this when you have a source-system field and need to find where it belongs in the Open Footprint model.1 finding
Why it is in this group
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "ofp_semantic_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.
Description, as the server wrote it Use 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ofp_semanticsUse this when mapping fields from SAP, another ERP or a supplier feed onto Open Footprint.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
semantic_templatesUse this when you want to see which kinds of questions the verified emissions data can answer, before calling semantic_query.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use this when you want to see which kinds of questions the verified emissions data can answer, before calling semantic_query.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 6Show 6 read-only tools
billing_statusUse this when a call was refused for credits or plan, to tell the user exactly what is missing.No findings
Why it is in this group
- The name "billing_status" says "status": a word for reading.
Description, as the server wrote it Use 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_standardsUse this when you need to see which sustainability data standards and versions validate_data can check, before calling it.No findings
Why it is in this group
- The name "list_standards" says "list": a word for reading.
Description, as the server wrote it Use this when you need to see which sustainability data standards and versions validate_data can check, before calling it.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ofp_search_entitiesUse this when you need the Open Footprint entity for a concept such as "Scope 3 emissions", "facility" or "product footprint".No findings
Why it is in this group
- The name "ofp_search_entities" says "search": a word for reading.
Description, as the server wrote it Use 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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.No findings
Why it is in this group
- The name "ofp_validate" says "validate": a word for reading.
Description, as the server wrote it Use 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 constraints, enum membership and calculations; with a sector, its guardrails. Always read `checked` and `checks_not_run` per call, and `schema.coverage.constraintsDeclared`, rather than assuming a range check ran. Not checked: undeclared ranges, unit coherence, live referential integrity, factor provenance. Never report a payload as compliant unless sector_policy is in `checked` and policy.outcome is passed. `schemaValid` is the structural verdict; `valid` is deprecated.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
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).No findings
Why it is in this group
- The name "semantic_query" says "query": a word for reading.
Description, as the server wrote it Use 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 payment_required, tell your operator what the call needs; do not retry the same call. Prefer a specific site, company or period.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
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.No findings
Why it is in this group
- The name "validate_data" says "validate": a word for reading.
Description, as the server wrote it Use 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:37 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 17
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://api.dveracity.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://api.dveracity.com/
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 17 tools that change things (17 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.dveracity.com/mcp: tools/list returned 23 tools to an anonymous client, including semantic_templates (write), credits_balance (write), keri_identity (write), ofp_models (write), ofp_entity (write) and 12 more
Posture changes
- Nov 6, 2026
- HTTP status of an anonymous initialize: 401 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 17
- Protocol version: none to 2025-06-18
- WWW-Authenticate on 401: yes to not observed
- resource_metadata in WWW-Authenticate: https://api.dveracity.com/.well-known/oauth-protected-resource/mcp to none
- Client ID metadata documents: no to yes
Findings
Matches of fixed checks, with the text they matched.
The server marks "ofp_semantic_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 removed, 4 changed.−2 removed~4 changedView diff
- Removed:billing_purchase
- Removed:billing_subscribe
- Changed:billing_plansChanges thingstitledescription
- Changed:ofp_validateOnly readsdescription
- Changed:semantic_queryOnly readsdescription
- Changed:validate_dataOnly readsdescription
PostureRemote posture changed. HTTP status of an anonymous initialize: 401 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 17 (and 4 more).View diff
- HTTP status of an anonymous initialize: 401 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 17
- Protocol version: none to 2025-06-18
- WWW-Authenticate on 401: yes to not observed
- resource_metadata in WWW-Authenticate: https://api.dveracity.com/.well-known/oauth-protected-resource/mcp to none
- Client ID metadata documents: no to yes
Tools25 changed.~25 changedView diff
- Changed:billing_plansChanges thingsdescriptioninputSchemaannotations
- Changed:billing_purchaseCan't be undonedescriptioninputSchemaannotations
- Changed:billing_statusOnly readsdescriptioninputSchemaannotations
- Changed:billing_subscribeChanges thingsdescriptioninputSchemaannotations
- Changed:compliance_evaluateChanges thingsdescriptioninputSchemaannotations
- Changed:compliance_evaluationChanges thingsdescriptioninputSchemaannotations
- Changed:compliance_policiesChanges thingsdescriptioninputSchemaannotations
- Changed:compliance_policyChanges thingsdescriptioninputSchemaannotations
- Changed:compliance_policy_registerChanges thingsdescriptioninputSchemaannotations
- Changed:credits_balanceChanges thingsdescriptioninputSchemaannotations
- Changed:keri_identityChanges thingsdescriptioninputSchemaannotations
- Changed:list_standardsOnly readsdescriptioninputSchemaannotations
- Changed:ofp_entityChanges thingsdescriptioninputSchemaannotations
- Changed:ofp_model_provenanceChanges thingsdescriptioninputSchemaannotations
- Changed:ofp_modelsChanges thingsdescriptioninputSchemaannotations
- Changed:ofp_policiesChanges thingsdescriptioninputSchemaannotations
- Changed:ofp_search_entitiesOnly readsdescriptioninputSchemaannotations
- Changed:ofp_sectorChanges thingsdescriptioninputSchemaannotations
- Changed:ofp_sectorsChanges thingsdescriptioninputSchemaannotations
- Changed:ofp_semantic_codeChanges thingsdescriptioninputSchemaannotations
- Changed:ofp_semanticsChanges thingsdescriptioninputSchemaannotations
- Changed:ofp_validateOnly readsdescriptioninputSchemaannotations
- Changed:semantic_queryOnly readsdescriptioninputSchemaannotations
- Changed:semantic_templatesChanges thingsdescriptioninputSchemaannotations
- Changed:validate_dataOnly readsdescriptioninputSchemaannotations
Tools25 changed.~25 changedView diff
- Changed:billing_plansChanges thingstitledescriptionannotations
- Changed:billing_purchaseCan't be undonetitledescriptionannotations
- Changed:billing_statusOnly readstitledescriptionannotations
- Changed:billing_subscribeChanges thingstitledescriptionannotations
- Changed:compliance_evaluateChanges thingstitledescriptionannotations
- Changed:compliance_evaluationChanges thingstitledescriptionannotations
- Changed:compliance_policiesChanges thingstitledescriptionannotations
- Changed:compliance_policyChanges thingstitledescriptionannotations
- Changed:compliance_policy_registerChanges thingstitledescriptionannotations
- Changed:credits_balanceChanges thingstitledescriptionannotations
- Changed:keri_identityChanges thingstitledescriptionannotations
- Changed:list_standardsOnly readstitledescriptionannotations
- Changed:ofp_entityChanges thingstitledescriptionannotations
- Changed:ofp_model_provenanceChanges thingstitledescriptionannotations
- Changed:ofp_modelsChanges thingstitledescriptionannotations
- Changed:ofp_policiesChanges thingstitledescriptionannotations
- Changed:ofp_search_entitiesOnly readstitledescriptionannotations
- Changed:ofp_sectorChanges thingstitledescriptionannotations
- Changed:ofp_sectorsChanges thingstitledescriptionannotations
- Changed:ofp_semantic_codeChanges thingstitledescriptionannotations
- Changed:ofp_semanticsChanges thingstitledescriptionannotations
- Changed:ofp_validateOnly readstitledescriptionannotations
- Changed:semantic_queryOnly readstitledescriptionannotations
- Changed:semantic_templatesChanges thingstitledescriptionannotations
- Changed:validate_dataOnly readstitledescriptionannotations
Install
Pinned to version 0.8.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http semantic https://api.dveracity.com/mcpclaude mcp add --transport http semantic https://api.dveracity.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__semantic__semantic_query",
"mcp__semantic__list_standards",
"mcp__semantic__validate_data",
"mcp__semantic__ofp_search_entities",
"mcp__semantic__ofp_validate",
"mcp__semantic__billing_status"
],
"ask": [
"mcp__semantic__semantic_templates",
"mcp__semantic__credits_balance",
"mcp__semantic__keri_identity",
"mcp__semantic__ofp_models",
"mcp__semantic__ofp_entity",
"mcp__semantic__ofp_sectors",
"mcp__semantic__ofp_sector",
"mcp__semantic__ofp_policies",
"mcp__semantic__compliance_policies",
"mcp__semantic__compliance_policy",
"mcp__semantic__compliance_evaluate",
"mcp__semantic__compliance_evaluation",
"mcp__semantic__compliance_policy_register",
"mcp__semantic__ofp_semantics",
"mcp__semantic__ofp_semantic_code",
"mcp__semantic__ofp_model_provenance",
"mcp__semantic__billing_plans"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as semantic. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.dveracity/semantic-mcp/verify?hash=886f2f6d0b7457bf0777cee7944148cfca1d6045dd1cfad57d76df3d2233a856" | jq -e '.changed == false'Pinned hash 886f2f6d0b74, from Nov 16, 2026, 11:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.dveracity/semantic-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.dveracity/semantic-mcp)Source: MCP Registry · repository. Synced Nov 3, 2026, 03:17 UTC.
dVeracity Semantic API MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the dVeracity Semantic API MCP server safe?
- No scan can promise that. What its definitions show: 23 tools, 17 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the dVeracity Semantic API MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the dVeracity Semantic API MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the dVeracity Semantic API MCP server have?
- 23 tools: 17 write, 6 read. semantic_templates, credits_balance, keri_identity, ofp_models, ofp_entity, ofp_sectors, ofp_sector, ofp_policies and 15 more.
Does the dVeracity Semantic API MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the dVeracity Semantic API MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the dVeracity Semantic API MCP server changed its tools?
- Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.