mcpbeat

Attrove MCP Server

com.attrove/mcp
answering

Attrove is answering right now. Last checked 15 min ago. 176 installs a week from npm.

Catch conversations going quiet — watch outcomes and search Gmail, Slack, and meetings. One MCP.

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

Installs per day peak 63 · avg 18 · +80% w/w
a month agotoday
Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
Tools
hidden behind auth
629 ms
Response time
average over 24h
176
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://api.attrove.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://api.attrove.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://api.attrove.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://api.attrove.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://api.attrove.com/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://api.attrove.com/mcp streamable-http needs key 638 ms 15 min ago

Attrove — questions

Answers built from our own checks of this server.

Why is there no tool list for Attrove?
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 Attrove working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 629 ms. The bar chart above shows every period we have measured.
Is Attrove 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 Attrove?
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 Attrove need an API key?
Yes. Every time we knock, Attrove 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 Attrove?
It answers our handshake in 629 ms on average, which is faster than 15% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Attrove?
The npm package @attrove/mcp was installed 176 times in the last week. Week over week that is +80%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.