mcpbeat Sign in

exec-brief MCP Server

answering

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

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

Uptime history 48 days of history · worst day 44%
48 days agonow
100.0%
Uptime 24h
91 of 91 checks
Tools
hidden behind auth
395 ms
Response time
average over 24h
authentication required
Access
streamable-http

Nothing serious here today

Today is the operative word: we check exec-brief every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

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 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 it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://exec-brief.basenull.com/api/mcp streamable-http needs auth 234 ms 15 min ago

Alternatives to exec-brief

same job, measured the same way
BriefPort Agent Delivery
by briefport

Coding agents read frozen requirements, report progress, and submit delivery evidence.

answering
SEO Audit
by inxy

Free SEO & AI-search (AEO) audits for any site or Shopify store, with emailed weekly score reports.

5 tools answering
Report Needs MCP Server
by jarvisonm4

MCP server for AI agents to report infrastructure needs they encounter during task execution

54 installs/wk local only
Malwagon
by malwagon

Submit files and URLs to a malware sandbox, poll scans, fetch reports, hashes and IOCs.

5 tools answering
NeuroRank
by neurorank

Esports cognitive-combine data over MCP: free cohort stats, paid player & team scouting reports.

3 tools answering
Faldaro
by faldaro

Forms, submissions, workflows and reports in Faldaro, exactly as privileged as your API key.

45 installs/wk answering
Fcop
by joinwell52-ai

Durable tasks, reports, reviews and branch convergence for multi-agent teams over local files.

222 installs/wk local only
Atimelogger MCP
by zaplitny

MCP server exposing the ATimeLogger REST API (activities, reports, types)

40 installs/wk local only

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 395 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 credentials: 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 395 ms on average, which is faster than 39% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.