mcpbeat

exec-brief MCP Server

com.basenull/exec-brief
answering

exec-brief is answering right now. Last checked 7 min ago.

Weekly 5-15 reports for executive teams: submit reports, fetch the Friday briefing.

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
Tools
hidden behind auth
407 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 7 min ago.

run in your terminal
claude mcp add exec-brief --transport http https://exec-brief.basenull.com/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "exec-brief": {
      "url": "https://exec-brief.basenull.com/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.exec-brief]
url = "https://exec-brief.basenull.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "exec-brief": {
      "url": "https://exec-brief.basenull.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "exec-brief": {
      "url": "https://exec-brief.basenull.com/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://exec-brief.basenull.com/api/mcp streamable-http needs key 347 ms 7 min ago

exec-brief — questions

Answers built from our own checks of this server.

Why is there no tool list for exec-brief?
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 exec-brief 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 407 ms. The bar chart above shows every period we have measured.
How do I connect exec-brief?
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 exec-brief need an API key?
Yes. Every time we knock, exec-brief 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 exec-brief?
It answers our handshake in 407 ms on average, which is faster than 33% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.