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.

Livespace CRM MCP Server

NPM · LIVESPACE-CRM-MCP · SCANNED SEP 27

Unofficial local MCP server for Livespace CRM with read tools and guarded writes.

Available components

0 this week 47 Trust /100
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 Security90
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known medium-severity CVE affects hono 4.13.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 0 of 5 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to proAutomator/livespace-crm-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 50 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks 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 we can run it. How we score packages →

Install

How do I install the Livespace CRM MCP Server server?

Livespace CRM MCP Server runs locally as an npm package, launched with npx -y livespace-crm-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · livespace-crm-mcp

# add to Claude Code
claude mcp add proautomator-livespace-crm-mcp -- npx -y livespace-crm-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "proautomator-livespace-crm-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "livespace-crm-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "proautomator-livespace-crm-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "livespace-crm-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add proautomator-livespace-crm-mcp -- npx -y livespace-crm-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "proautomator-livespace-crm-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "livespace-crm-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add proautomator-livespace-crm-mcp --command npx --arg -y --arg livespace-crm-mcp
# ~/.hermes/config.yaml
mcp_servers:
  proautomator-livespace-crm-mcp:
    command: "npx"
    args: ["-y", "livespace-crm-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "proautomator-livespace-crm-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "livespace-crm-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add proautomator-livespace-crm-mcp -t stdio -c npx -a -y livespace-crm-mcp
// mcp.json
{
  "mcpServers": {
    "proautomator-livespace-crm-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "livespace-crm-mcp"
      ]
    }
  }
}
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.

  • 25 Sept 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
  • 9 Sept 26 −3
    • CVE-2026-84365 affects this package: medium ▼ security
    • CVE-2026-84363 affects this package: medium ▼ security
    • CVE-2026-84364 affects this package: medium ▼ security
    • Known CVEs: pass → fail ▼ security
  • 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 → pass ▲ functional
  • 14 Aug 26 0
    • Security disclosure: pass → 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
  • 8 Aug 26 0
    • Stability: Stability not yet verified: our sandbox could not run this package, so we have no schema to compare. security
    • 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
    • Tool coverage: Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess. functional
  • 7 Aug 26 0

    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 27 Sept 2026 · Analysed npm/livespace-crm-mcp@0.1.1

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 proAutomator/livespace-crm-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/proAutomator/livespace-crm-mcp/.github/workflows/publish.yml@refs/tags/v0.1.1
Rekor log index 2371153157
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:0aaa643e9cd6d50df3a7c561dcfad89652bb767f3394314ab67ecd1490f9e5380bab296015e27559de5079ec2ff02cccfccefbcdce6bdf14ab4c2687c

Background: How many MCP packages publish verified provenance →

Vulnerabilities 3 findings
ID CVE Severity Vector Fix available
GHSA-crvj-82cr-hjcx CVE-2026-84363 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-g6gw-c38x-mqfc CVE-2026-84364 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-gqvv-2mrq-wpjv CVE-2026-84365 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 5 packages
Packages resolved 5
Tree resolution Complete

Background: SBOMs and build attestations, explained →

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.

Common questions

What is the Livespace CRM MCP Server server?

Livespace CRM MCP Server is listed in the public MCP registry as io.github.proAutomator/livespace-crm-mcp. Unofficial local MCP server for Livespace CRM with read tools and guarded writes. This page covers its npm package (livespace-crm-mcp).

Is the Livespace CRM MCP Server server safe to use?

Livespace CRM MCP Server scores 47 out of 100 on VerifyMCP. We recorded 3 known advisories against it as of 27 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 Livespace CRM MCP Server server still maintained?

Livespace CRM MCP Server is still listed as active in the MCP registry. We last reached this channel on 27 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 Livespace CRM MCP Server server under?

Livespace CRM MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.