Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Yuva

MCPB · YUVA.MCPB · 2 COMPONENTS

Customer support inbox: search, read, triage and draft replies to e-mail and chat.

Available components

remote · {yuva_host} 0 mcpb · yuva.mcpb 6
+1 this week 6 Trust /100

Last scanned (1 hour ago)

Scores higher than 21% of MCPB servers

Category CRM and Sales

Trust breakdown (7 categories)

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 Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this bundle is larger than we will inspect (50 MiB to download, 100,000 files or 256 MiB unpacked), so we did not read it. This is a limit on our side, not a finding about the bundle.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this bundle is larger than we will inspect (50 MiB to download, 100,000 files or 256 MiB unpacked), so we did not read it. This is a limit on our side, not a finding about the bundle.Unverified
Provenance & Transparency29
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Build provenance not yet verified. View diagnostics → Unverified
  • License not yet determined.Unverified
  • Maintenance history not yet determined.Unverified
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Stability & Change Management0
  • Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Tool Coverage0
  • Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Tool Safety0
  • Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Capabilities0
  • Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

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.

  • 18 Oct 26 0
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. 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
    • 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
    • Package version: 0.0.20 → 0.0.22 functional
    • Package version: 0.0.20 → 0.0.21 functional
  • 17 Oct 26 0
    • Stability: Stability not yet verified: our sandbox could not run this package, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan. security
    • Tool coverage: Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess. functional
    • Schema quality: Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake. functional
    • Package version: 0.0.17 → 0.0.20 functional
    • Package version: 0.0.17 → 0.0.18 functional
  • 16 Oct 26 0
    • Stability: Stability not yet verified: our sandbox could not run this package, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan. security
    • Tool coverage: Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess. functional
    • Schema quality: Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake. functional
    • Package version: 0.0.16 → 0.0.17 functional
  • 15 Oct 26 0
    • Stability: Stability not yet verified: our sandbox could not run this package, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan. security
    • Capabilities: Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake. functional
    • Schema quality: Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess. functional
    • Tool coverage: Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess. functional
    • Package version: 0.0.13 → 0.0.16 functional
    • Package version: 0.0.13 → 0.0.15 functional
    • Package version: 0.0.13 → 0.0.14 functional
  • 14 Oct 26 0
    • Package version: 0.0.11 → 0.0.13 functional
    • Package version: 0.0.11 → 0.0.12 functional
  • 13 Oct 26 +1
    • Security disclosure: unverified → pass ▲ functional
    • Package version: 0.0.8 → 0.0.11 functional
    • Package version: 0.0.8 → 0.0.9 functional
  • 11 Oct 26 5

    First indexed and scored.

Diagnostics

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 18 Oct 2026 · Analysed mcpb/https://github.com/productdevbook/yuva/releases/download/v0.0.22/yuva.mcpb@0.0.22

Provenance Inconclusive

We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.

Result Inconclusive
Ecosystem mcpb
Reason Metadata unavailable

Background: How many MCP packages publish verified provenance →

MCP tools

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. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.

Install

How do I install the Yuva MCP server?

Yuva ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 58f2ec53038f072721bbb8731adbf79423569738191575d523da4074dcf68526; the commands to do that are on this page. If it does not match, do not open it.

mcpb · yuva.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

58f2ec53038f072721bbb8731adbf79423569738191575d523da4074dcf68526

macOS / Linux 

echo "58f2ec53038f072721bbb8731adbf79423569738191575d523da4074dcf68526  yuva.mcpb" | shasum -a 256 -c

Windows (PowerShell) 

(Get-FileHash -Algorithm SHA256 .\yuva.mcpb).Hash -eq "58f2ec53038f072721bbb8731adbf79423569738191575d523da4074dcf68526"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.