mcpbeat Sign in

Outcomet MCP Server

answering

Outcomet is answering right now. Last checked 1 min ago.

Read customer feedback, problems and initiatives in Outcomet, and log new feedback from chat.

Uptime history 16 days of history · worst day 96%
16 days agonow
97.8%
Uptime 24h
90 of 92 checks
—
Tools
hidden behind auth
273 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Outcomet does not always answer

Over the last week it answered 98.4% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

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 1 min ago.

run in your terminal
claude mcp add mcp --transport http https://mcp.outcomet.app/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.outcomet.app/mcp
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.outcomet.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.outcomet.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://mcp.outcomet.app/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.outcomet.app/mcp streamable-http sign-in 257 ms 1 min ago

Alternatives to Outcomet

same job, measured the same way
Kairo
by kairocalories

Calorie tracker app for ChatGPT and Claude: read meals, macros, weight and log meals from chat.

answering
Nutrition by Pack4Back
by pack4back

Log meals, water, and weight to Garmin Connect from Claude or ChatGPT.

answering
Bugfender
by bugfender

Access Bugfender logs, crashes, devices, and user feedback from MCP-enabled clients.

358 installs/wk local only
Damper
by usedamper

Feedback, roadmap, agent task execution with review, changelog, status pages and error logs.

141 tools answering
CalorieLog Pro
by calorielogpro

Calorie and macro diary your AI fills in: log meals from text or photos, refine later, track goals.

answering
JustGains
by justgains

Save workouts, read training history and progress, search exercises, and log food in JustGains.

answering
Reps
by repsworkout

Your Reps gym log in Claude or ChatGPT: workouts, PRs, progress, routines and training plans.

answering
Churn Solution
by churnsolution

Query Churn Solution cancellation-flow metrics, revenue, and feedback analytics (read-only).

answering

Outcomet — questions

Answers built from our own checks of this server.

Why is there no tool list for Outcomet?
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: 97.8% of checks in the last 24 hours got a reply.
Is Outcomet working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 92 checks got a reply (97.8%), average response time 273 ms. The bar chart above shows every period we have measured.
How do I connect Outcomet?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Outcomet?
No API key is involved. Outcomet answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Outcomet?
It answers our handshake in 273 ms on average, which is faster than 52% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.