MCP Dataverse
NPM · MCP-DATAVERSE · SCANNED SEP 20
73 tools for Microsoft Dataverse: CRUD, FetchXML, metadata, audit, batch, role privileges and more.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security89
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects uuid 8.3.2, reached via @azure/msal-node > uuid. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 42 of 113 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to codeurali/mcp-dataverse). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 60 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
How do I install the MCP Dataverse server?
MCP Dataverse runs locally as an npm package, launched with npx -y mcp-dataverse. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-dataverse
claude mcp add codeurali-dataverse -- npx -y mcp-dataverse
{
"mcpServers": {
"codeurali-dataverse": {
"command": "npx",
"args": [
"-y",
"mcp-dataverse"
]
}
}
} {
"servers": {
"codeurali-dataverse": {
"command": "npx",
"args": [
"-y",
"mcp-dataverse"
]
}
}
} codex mcp add codeurali-dataverse -- npx -y mcp-dataverse
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"codeurali-dataverse": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-dataverse"
],
"enabled": true
}
}
} openclaw mcp add codeurali-dataverse --command npx --arg -y --arg mcp-dataverse
mcp_servers:
codeurali-dataverse:
command: "npx"
args: ["-y", "mcp-dataverse"] {
"McpServers": {
"codeurali-dataverse": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-dataverse"
]
}
}
} assistant mcp add codeurali-dataverse -t stdio -c npx -a -y mcp-dataverse
{
"mcpServers": {
"codeurali-dataverse": {
"command": "npx",
"args": [
"-y",
"mcp-dataverse"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 15 Aug 26 0
- Security disclosure: unverified → fail ▼ functional
- 14 Aug 26 0
- Security disclosure: fail → unverified ▼ functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- Dependency health: partial → 0.83 functional
- 5 Aug 26 0
- CVE-2026-69207 no longer affects this package ▲ security
- 4 Aug 26 0
- CVE-2026-69207 affects this package: high ▼ security
- 2 Aug 26 0
- CVE-2026-41907 affects this package: high ▼ security
- Known CVEs: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Provenance: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- The attested source repository moved: codeurali/mcp-dataverse security
- Security disclosure: fail → unverified ▼ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Licence: MIT functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/mcp-dataverse@0.5.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | codeurali/mcp-dataverse |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/codeurali/mcp-dataverse/.github/workflows/publish.yml@refs/tags/v0.5.0 |
| Rekor log index | 1175504697 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:ba95a84580a8d7db08cb7775d7f9b2e0f6d6e1aa8e3f1be6d4aba12399fec2a5982e762ece6362637bde0ba7ce529ddb4d8d1ab98fae2243201902542 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 113 packages
| Packages resolved | 113 |
|---|---|
| Deprecated | 1 |
| Stale | 41 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
What is the MCP Dataverse server?
MCP Dataverse is listed in the public MCP registry as io.github.codeurali/dataverse. 73 tools for Microsoft Dataverse: CRUD, FetchXML, metadata, audit, batch, role privileges and more. This page covers its npm package (mcp-dataverse).
Is the MCP Dataverse server safe to use?
MCP Dataverse scores 46 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Is the MCP Dataverse server still maintained?
MCP Dataverse is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the MCP Dataverse server under?
MCP Dataverse declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.