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.

ai.vruum/mcp

NPM · @VRUUM/MCP · 2 COMPONENTS

Vruum AI revenue platform — outbound, deals, pipeline & CRM automation over one MCP.

0 this week 57 Trust /100

Last scanned (12 hours ago)

Scores higher than 27% of npm 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 Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 4 of 14 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability0
  • Schema quality not yet verified: the captured schema was too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge it on a partial copy.Unverified
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage0
  • Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge them on a partial copy.Unverified
Tool Safety0
  • Tool safety not yet verified: the captured tool definitions were too large for us to store in full (the trim removes the very descriptions this category reads), or the server stopped listing its tools part-way.Unverified
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 3 categories

Categories scored 0 because our sandbox 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 →

What we tested

Checks we ran (11)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Stability
  • MCP protocol

Checks we could not complete (3)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: the captured schema was too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge it on a partial copy.
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge them on a partial copy.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: the captured tool definitions were too large for us to store in full (the trim removes the very descriptions this category reads), or the server stopped listing its tools part-way.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +1
    • Stability: 0.97 → pass security
  • 20 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 19 Nov 26 0
    • Package version: 0.14.0 → 0.17.0 functional
  • 18 Nov 26 0
    • Package version: 0.14.0 → 0.17.0 functional
  • 15 Nov 26 0
    • Package version: 0.14.0 → 0.17.0 functional
  • 14 Nov 26 +6
    • Source repository: unverified → pass ▲ security
    • Stability: 0.97 → pass security
    • Package version: 0.14.0 → 0.17.0 functional
  • 13 Nov 26 −5
    • Provenance: pass → unverified ▼ security
    • Stability: 0.93 → unverified ▼ security
    • 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
    • Capabilities: pass → unverified ▼ 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
    • 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
    • Package version: 0.16.0 → 0.17.0 functional
    • Package version: 0.14.0 → 0.17.0 functional
  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

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 21 Nov 2026 · Analysed npm/@vruum/mcp@0.17.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 14 packages
Packages resolved 14
Stale 4
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 37 exposed · ~63,758 tokens partial

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 →

Tool Tokens
fetch ~4,952

No description provided.

NameTypeReqDescription
filtersobject––
for_companystring––
id–––
subtypestring––
typestringyes–

No output schema declared.

No examples provided.

find_warm_path ~1,127

No description provided.

NameTypeReqDescription
for_companystring––
limitinteger––
scopestring––
targetstringyes–

No output schema declared.

No examples provided.

get_content_review ~623

No description provided.

NameTypeReqDescription
content_typestring––
daysinteger––
for_companystring––
limitinteger––
offsetinteger––
post_idsarray––
statusstring––

No output schema declared.

No examples provided.

get_daily_briefing ~2,665

No description provided.

NameTypeReqDescription
for_companystring––

No output schema declared.

No examples provided.

get_deal_360 ~432

No description provided.

NameTypeReqDescription
deal_idstringyes–
for_companystring––
timeline_limitinteger––

No output schema declared.

No examples provided.

get_engagement_review ~1,189

No description provided.

NameTypeReqDescription
content_lengthstring––
engagement_idsstring––
for_companystring––
include_decidedboolean––
limitinteger––
near_miss_max_age_daysinteger––
objectivestring––
offsetinteger––
sender_user_idstring––
sourcestring––

No output schema declared.

No examples provided.

get_network_identity_review ~421

No description provided.

NameTypeReqDescription
for_companystring––
kindstring––
limitinteger––
offsetinteger––
person_refstring––

No output schema declared.

No examples provided.

get_next_actions ~327

No description provided.

NameTypeReqDescription
for_companystring––
limitinteger––

No output schema declared.

No examples provided.

get_objective_outcomes ~995

No description provided.

NameTypeReqDescription
end_atstringyes–
for_companystring––
objective_idsarrayyes–
outcome_cutoffstringyes–
start_atstringyes–

No output schema declared.

No examples provided.

get_operator_companies ~237

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_outreach_review ~2,234

No description provided.

NameTypeReqDescription
content_lengthstring––
for_companystring––
limitinteger––
message_idsstring––
objectivestring––
offsetinteger––

No output schema declared.

No examples provided.

get_performance_metrics ~2,416

No description provided.

NameTypeReqDescription
end_datestring––
for_companystring––
metricstring––
objective_idstring––
start_datestring––
viewstring––

No output schema declared.

No examples provided.

get_person_360 ~313

No description provided.

NameTypeReqDescription
for_companystring––
person_idstringyes–

No output schema declared.

No examples provided.

get_revenue ~607

No description provided.

NameTypeReqDescription
binding_statusstring––
company_idstring––
currencystring––
cursorstring––
for_companystring––
instruction_idstring––
journey_idstring––
knowledge_cutoffstring––
limitinteger––
metricstring––
offsetinteger––
period_endstring––
period_startstring––
reporting_entity_idstring––
source_idsarray––
viewstringyes–

No output schema declared.

No examples provided.

import_prospects ~984

No description provided.

NameTypeReqDescription
actionstringyes–
for_companystring––
id–––
idempotency_keystring––
itemsarray––
payloadobject––

No output schema declared.

No examples provided.

inspect_assistant ~2,481

No description provided.

NameTypeReqDescription
actionstringyes–
for_companystring––
id–––
itemsarray––
payloadobject––

No output schema declared.

No examples provided.

inspect_objective ~1,748

No description provided.

NameTypeReqDescription
actionstringyes–
for_companystring––
id–––
itemsarray––
payloadobject––

No output schema declared.

No examples provided.

inspect_pipeline ~310

No description provided.

NameTypeReqDescription
for_companystring––

No output schema declared.

No examples provided.

manage_account ~3,797

No description provided.

NameTypeReqDescription
actionstringyes–
for_companystring––
id–––
idempotency_keystring––
itemsarray––
payloadobject––

No output schema declared.

No examples provided.

manage_assistant ~3,336

No description provided.

NameTypeReqDescription
actionstringyes–
for_companystring––
id–––
itemsarray––
payloadobject––

No output schema declared.

No examples provided.

manage_content ~3,749

No description provided.

NameTypeReqDescription
actionstringyes–
for_companystring––
id–––
idempotency_keystring––
itemsarray––
kindstring––
payloadobject––

No output schema declared.

No examples provided.

manage_deal ~2,858

No description provided.

NameTypeReqDescription
actionstringyes–
for_companystring––
id–––
idempotency_keystring––
itemsarray––
payloadobject––

No output schema declared.

No examples provided.

manage_engagements ~1,443

No description provided.

NameTypeReqDescription
actionstringyes–
for_companystring––
id–––
idempotency_keystring––
itemsarray––
payloadobject––

No output schema declared.

No examples provided.

manage_history_import ~1,006

No description provided.

NameTypeReqDescription
actionstringyes–
for_companystring––
id–––
idempotency_keystring––
itemsarray––
payloadobject––

No output schema declared.

No examples provided.

manage_kb ~623

No description provided.

NameTypeReqDescription
actionstringyes–
for_companystring––
id–––
idempotency_keystring––
itemsarray––
payloadobject––

No output schema declared.

No examples provided.

manage_messages ~4,185

No description provided.

NameTypeReqDescription
actionstringyes–
for_companystring––
id–––
idempotency_keystring––
itemsarray––
payloadobject––

No output schema declared.

No examples provided.

manage_network_identity_resolution ~436

No description provided.

NameTypeReqDescription
actionstringyes–
affiliation_kindstring––
basisstring––
classificationstring––
commitboolean––
company_refstring––
decisionstring––
for_companystring––
reasonstringyes–
source_identity_refstring––
source_person_refstring––
surviving_person_refstring––
target_entity_refstring––
target_person_refstring––
titlestring––

No output schema declared.

No examples provided.

manage_outreach ~4,011

No description provided.

NameTypeReqDescription
actionstringyes–
for_companystring––
id–––
idempotency_keystring––
itemsarray––
payloadobject––

No output schema declared.

No examples provided.

manage_person ~2,137

No description provided.

NameTypeReqDescription
actionstringyes–
for_companystring––
id–––
idempotency_keystring––
itemsarray––
payloadobject––

No output schema declared.

No examples provided.

manage_relationship_action ~866

No description provided.

NameTypeReqDescription
actionstringyes–
attempt_refstring––
channelstring––
client_request_idstring––
expected_versioninteger––
for_companystring––
message_textstring––
outcomeobject––
purposestring––
responsestring––
result_refstring––
sentboolean––
targetstring––

No output schema declared.

No examples provided.

manage_revenue ~1,048

No description provided.

NameTypeReqDescription
actionstringyes–
for_companystring––
id–––
idempotency_keystring––
itemsarray––
payloadobject––

No output schema declared.

No examples provided.

manage_settings ~2,833

No description provided.

NameTypeReqDescription
actionstringyes–
for_companystring––
id–––
idempotency_keystring––
itemsarray––
payloadobject––

No output schema declared.

No examples provided.

query_crm ~511

No description provided.

NameTypeReqDescription
for_companystring––
limitinteger––
offsetinteger––
querystring––

No output schema declared.

No examples provided.

research ~4,047

No description provided.

NameTypeReqDescription
actionstringyes–
for_companystring––
id–––
idempotency_keystring––
itemsarray––
payloadobject––

No output schema declared.

No examples provided.

research_lookup ~1,357

No description provided.

NameTypeReqDescription
actionstringyes–
for_companystring––
id–––
itemsarray––
payloadobject––

No output schema declared.

No examples provided.

search ~898

No description provided.

NameTypeReqDescription
filtersobject––
for_companystring––
limitinteger––
offsetinteger––
query–––
typestringyes–

No output schema declared.

No examples provided.

skill ~556

No description provided.

NameTypeReqDescription
actionstringyes–
for_companystring––
id–––
idempotency_keystring––
itemsarray––
payloadobject––

No output schema declared.

No examples provided.

Install

How do I install the ai.vruum/mcp server?

ai.vruum/mcp runs locally as an npm package, launched with npx -y @vruum/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 · @vruum/mcp

# add to Claude Code
claude mcp add ai-vruum-mcp -- npx -y @vruum/mcp
Common questions

What is the ai.vruum/mcp server?

ai.vruum/mcp is listed in the public MCP registry as ai.vruum/mcp. Vruum AI revenue platform, outbound, deals, pipeline & CRM automation over one MCP. This page covers its npm package (@vruum/mcp).

Is the ai.vruum/mcp server safe to use?

ai.vruum/mcp scores 57 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 ai.vruum/mcp server still maintained?

ai.vruum/mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 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 ai.vruum/mcp server under?

ai.vruum/mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the ai.vruum/mcp server?

VerifyMCP ran 11 checks on ai.vruum/mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 7 more. 3 items could not be completed, a gap on our side rather than a finding about ai.vruum/mcp: Schema quality, Tool coverage and Tool safety. 3 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.