mcpbeat

ScamVerify Threat Verification MCP Server

ai.scamverify/mcp
answering

ScamVerify Threat Verification is answering right now. Last checked 1 min ago.

AI-powered scam and threat verification for phone numbers, URLs, texts, and emails.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 43 hours of history
43 hours agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
386 ms
Response time
average over 24h
API key or OAuth
Access
streamable-http

Connect this server

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

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

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://scamverify.ai/api/mcp streamable-http needs key 270 ms 1 min ago

ScamVerify Threat Verification — questions

Answers built from our own checks of this server.

Why is there no tool list for ScamVerify Threat Verification?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is ScamVerify Threat Verification working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 386 ms. The bar chart above shows every period we have measured.
Is ScamVerify Threat Verification still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect ScamVerify Threat Verification?
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. You will need your own key or an OAuth login: it refuses anonymous clients.
Does ScamVerify Threat Verification need an API key?
Yes. Every time we knock, ScamVerify Threat Verification answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is ScamVerify Threat Verification?
It answers our handshake in 386 ms on average, which is faster than 36% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.