mcpbeat

VerifyRef MCP Server

com.verifyref/mcp
not responding

VerifyRef is listed as active in the registry but did not answer our last check. 52 installs a week from npm.

AI agent recruiting: talent pool match, reference checks, credit packs via Stripe MPP

Installs per day peak 131 · avg 8 · +68% w/w
a month agotoday
Uptime history 42 hours of history · worst hour 0%
42 hours agonow
0.0%
Uptime 24h
0 of 91 checks
—
Tools
hidden behind auth
794 ms
Response time
average over 24h
52
Installs / week
npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add mcp --transport http https://verifyref.com/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://verifyref.com/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://verifyref.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://verifyref.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://verifyref.com/api/mcp"
    }
  }
}

Endpoints

URLTransportStateLatencyChecked
https://verifyref.com/api/mcp streamable-http answering 794 ms 15 min ago

VerifyRef — questions

Answers built from our own checks of this server.

Is VerifyRef working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 794 ms. The bar chart above shows every period we have measured.
The registry lists VerifyRef as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect VerifyRef?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does VerifyRef need an API key?
No. VerifyRef completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.
How many people use VerifyRef?
The npm package @datalinc/verifyref-mcp was installed 52 times in the last week. Week over week that is +68%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.