Vruum MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Vruum stdio bridge for remote revenue-platform tools: Does credential-free introspection remain separate from account-authorized campaign execution on the remote server?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Operate research, outbound, pipeline, deals and CRM workflows from an MCP client.

What we know

Stdio bridge and remote MCP surface for the Vruum revenue platform. The bridge can expose the tool schema without credentials and proxies execution to the hosted Vruum MCP under the user's account token.

Maintenance / activity evidence

@vruum/mcp 0.8.0 published 2026-10-05T15:54:20.279Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Account-scoped revenue/CRM/outreach authority. Writes: Create/update CRM records; Run or stage outreach; Manage deals/pipeline and related workflow state.
OAuth/bearer token.
Sensitive access: Prospect/customer data, CRM history, Email/LinkedIn outreach content, Revenue data

Can communicate externally and alter revenue records; approval and account scope matter.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Does credential-free introspection remain separate from account-authorized campaign execution on the remote server?

The bounded review of the publisher's documented Vruum stdio bridge for remote revenue-platform tools and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Can communicate externally and alter revenue records; approval and account scope matter.
Account-scoped revenue/CRM/outreach authority.
OAuth/bearer token.
Prospect/account/deal/outreach data is processed by Vruum.
Reviewed write actions: Create/update CRM records; Run or stage outreach; Manage deals/pipeline and related workflow state
Sensitive access: Prospect/customer data, CRM history, Email/LinkedIn outreach content, Revenue data
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
exact public repository binding
retention/privacy detail
Write authority is account-scoped and can contact prospects or mutate CRM state.
Hosted remote is preferred for modern clients; local package acts as bridge.
Exact retention/privacy details were not established here.

Original activity observations

@vruum/mcp 0.8.0 published 2026-10-05T15:54:20.279Z

Technical identity

npm/@vruum/mcp

Exact implementation source: https://www.npmjs.com/package/@vruum/mcp ↗
Reviewed resource type: Gateway
Package identity: npm:@vruum/mcp
Service endpoint: https://api.vruum.ai/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry metadata ↗
@vruum/mcp
Recorded package identity, distribution or download evidence.
Evidence source ↗
vruum.ai/docs
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
vruum.ai/faq
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
www.npmjs.com/~jonmccutchen
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Gateway setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect gateway
Publisher instructions
OAuth remote preferred; stdio proxy may read existing `~/.vruum/credentials` and operate on real account even with no explicit env key.
Publisher recommends remote OAuth at https://api.vruum.ai/mcp; @vruum/mcp is for stdio-only clients, with VRUUM_MCP_TOKEN. Do not require a token for remote OAuth path.
publisher documented step or launch · Publisher instructions
claude mcp add --transport http vruum https://api.vruum.ai/mcp
Configure / authenticate
MCP100 setup guide
Vruum recommends remote OAuth at https://api.vruum.ai/mcp. Local npx is an optional stdio bridge requiring VRUUM_MCP_TOKEN for calls; tool introspection can work without credentials.
remote_streamable_http: https://api.vruum.ai/mcp
Environment variables referenced by this route (respect the alternatives above): VRUUM_MCP_TOKEN
Check connection
Suggested check
After OAuth sign-in inspect read-only available tools; absence of local token does not indicate failed remote OAuth.
Remove / uninstall / revoke
MCP100 setup guide
Generic client guidance (not publisher-specific uninstall): unregister MCP entry in the chosen client. If installed globally, remove the npm package separately. Revoke provider access separately through account controls, where supported. This does not erase local data or revoke funds/credentials automatically.
Unregister the named MCP entry from the actual host separately from removing a global npm install; no claim that either revokes remote credentials.
PAT in local bridge can be managed under Vruum Settings -> API tokens; precise revoke action was not independently observed.

Official Documentation & Sources

What it does

Stdio bridge and remote MCP surface for the Vruum revenue platform. The bridge can expose the tool schema without credentials and proxies execution to the hosted Vruum MCP under the user's account token.

Capability: Productivity & Collaboration
Resource type: Gateway
Industry: Professional Services
Best fit: Operate research, outbound, pipeline, deals and CRM workflows from an MCP client.

Representative uses

Research prospects and accounts
Draft/run email and LinkedIn outreach
Triage replies and engagement
Manage people, deals and pipeline
Read CRM/revenue state

Limitations

Write authority is account-scoped and can contact prospects or mutate CRM state.
Hosted remote is preferred for modern clients; local package acts as bridge.
Exact retention/privacy details were not established here.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: OAuth/bearer token.
Permissions: Account-scoped revenue/CRM/outreach authority.
Data handling: Prospect/account/deal/outreach data is processed by Vruum.
Cost: plan_based
Risk and cautions: Can communicate externally and alter revenue records; approval and account scope matter.

Access scope and cautions

Write actions: Create/update CRM records Run or stage outreach Manage deals/pipeline and related workflow state
Sensitive access: Prospect/customer data CRM history Email/LinkedIn outreach content Revenue data
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Research prospects and accounts; Draft/run email and LinkedIn outreach; Triage replies and engagement; Manage people, deals and pipeline; Read CRM/revenue state.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @vruum/mcp. Recorded endpoint: https://api.vruum.ai/mcp. Recorded transport: stdio, streamable_http. Recorded environment-variable notes: Vruum token for local/bridge execution. No configuration values are supplied here. Prerequisites: Vruum account; Node 20+ for local bridge. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: OAuth 2.1 or bearer token (vk_live_…); local bridge forwards user token.

Can it modify data or perform write operations?

Documented write actions include: Create/update CRM records; Run or stage outreach; Manage deals/pipeline and related workflow state. Recorded permission boundary: Account-scoped revenue/CRM/outreach authority.

What data-handling boundary should I consider?

Prospect/account/deal/outreach data is processed by Vruum. Recorded sensitive-access context: Prospect/customer data; CRM history; Email/LinkedIn outreach content; Revenue data.

What limitations and risks should I check before use?

Can communicate externally and alter revenue records; approval and account scope matter. Write authority is account-scoped and can contact prospects or mutate CRM state. Hosted remote is preferred for modern clients; local package acts as bridge. Exact retention/privacy details were not established here. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is plan based. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.