Productivity · Remote MCP server

vruum.ai

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

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
ai.vruum/mcp
Version
0.7.0
Status
Active
Category
productivity
Transport
Streamable HTTP, stdio (local process)
Package
npm
Published
2026-10-03
Updated
2026-10-03
Publisher
ai.vruum
Namespace
Namespace verified by the MCP Registry via the domain vruum.ai · how
Repository
github.com/vruum-gtm/mcp
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://api.vruum.ai/mcpAuthorization (required, secret)

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 401)
Handshake
Not completed: sign-in required
Sign-in required
Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
Checked on
2026-10-05

How the live check works

Packages

RegistryPackageVersionTransportEnvironment variables
npm@vruum/mcp0.7.0stdioNone declared

How to connect vruum.ai

vruum.ai is a remote MCP server: there is nothing to install. Its endpoint is https://api.vruum.ai/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.

It can also run locally from a Node.js package published to the npm registry: @vruum/mcp version 0.7.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @vruum/mcp@0.7.0.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@vruum/mcp@0.7.0"
      ]
    }
  }
}

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More productivity servers

All 2,706 →
ServerRunsEndpoint or package
Volta NotesBurn-after-read encrypted notes. E2E encrypted, decentralised on the Internet Computer.Local · stdionpm: @voltanotes/mcp
VornJob board for AI agents: find and post paid work, bid, deliver, award, approve and get paid.Remote · HTTPLive check: ✓ handshakeapi.joinvorn.com
VorortaiReal-world tasks in Hamburg: quote, check service area, submit an enquiry for human review.Remote · HTTPLive check: ✓ handshakevorortai.de
Voyager CommerceAI ticket commerce for theme parks, zoos, museums, and aquariums via any AI agent.Remote · HTTPLive check: ✗ no handshakereview-002-voyager-ai-commerce.zeus.gatewayticketing.hosting
Walkie MCPSearch and read your recorded meetings: notes, action items, participants, transcripts.Remote · HTTPLive check: sign-in requiredmcp.trywalkie.com
WalkMyPlanDescribe a house or upload a DWG/vector-PDF plan and get a walkable, editable 3D model.Remote · HTTPLive check: sign-in requiredmcp.walkmyplan.com
WarmerlyCold email outreach: find leads, launch campaigns, fix deliverability, answer replies.Remote · HTTPLive check: sign-in requiredapp.warmerly.com
WASync - WhatsApp Platform APIWhatsApp for your app or AI agent over OAuth2 - the same connections WASync runs inside your CRM.Remote · HTTPLive check: ✗ no handshakecloudapi.wasync.app