Other · Remote MCP server
Ask Xverum
Find and enrich people from 750M professional profiles, with Next Move Signal job-change scores.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.xverum/mcp- Version
- 2.3.1
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-10-01
- Updated
- 2026-10-01
- Publisher
- com.xverum
- Namespace
- Namespace verified by the MCP Registry via the domain xverum.com · how
- Website
- ask.xverum.com/docs/mcp-server
- Repository
- github.com/Xverum-LLC/xverum-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.xverum.com/mcp | None |
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
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @xverum/mcp | 1.0.2 | stdio |
How to connect Ask Xverum
Ask Xverum is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.xverum.com/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.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @xverum/mcp version 1.0.2. 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 @xverum/mcp@1.0.2.
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",
"@xverum/mcp@1.0.2"
]
}
}
}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 other servers
| Server | Runs |
|---|---|
| Ask HelenaOfficial answers about Helena Bioinformatics and its products, with citations to public sources. | Remote · HTTPLive check: ✓ handshake |
| Ask JevEvaluate state with typed choice, score, and probability questions. | Remote · HTTPLive check: sign-in required |
| Ask MeAsk about an operator's work, reusable patterns, availability and offer. Typed tools, eval-gated. | Remote · HTTPLive check: sign-in required |
| Ask OllamaBridge Claude with local Ollama LLMs for private AI-to-AI collaboration - no API keys, fully local. | Local · stdio |
| ask-oginoQuery Shunki Ogino's public profile: his thesis, the tools he builds, and his writing. | Remote · HTTPLive check: ✓ handshake |
| ask10aisIndependent measurements of how 12 AI models answer brand questions in Chinese and English. | Remote · HTTPLive check: ✓ handshake |
| AskAiRankHow ChatGPT, Claude, Perplexity and Gemini mention your brand: visibility, mentions, competitors. | Remote · HTTPLive check: sign-in required |
| Asked ThriceMeasure whether AI assistants actually recommend a brand, from measured answers. | Remote & Local · HTTP, stdioLive check: ✓ handshake |