Is the Outcomet MCP server down?

mcp-registry/app.outcomet/mcp · registry v3.5.0 · server reports v3.13.2

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 19:26 UTC · handshake 241ms

As of 2026-11-22 19:26 UTC, the Outcomet MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 1 minutes.

uptime (30d checks)
100%
checks observed
4,397
outages (90d)
1
tools
107

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

Point your MCP client at this streamable-http endpoint: https://mcp.outcomet.app/mcp

Agent-readiness: C (78/100)

C (78/100): 0 error(s), 4 warning(s) across 107 tool(s); ~42,133 tokens of tool definitions.
Scores higher than 20% of 27,663 MCP servers Glimind has audited.
Its tool list costs an agent ~42,133 tokens per session — more than 99% of servers.
79 → 78 since 2026-11-03
no tool-poisoning patterns
Descriptions58
Safety hints100
Schemas100
Protocol100
Stability52
Token cost25
Reliability100
Client compatibility100

What to fix (5)

1 tool definition(s) exceed ~1,200 tokens each (largest: competitor_mutate, ~1,901).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~1,301 tokens every session. How to fix →

Tools: competitor_mutate · saves ~1,301 tokens/session

107 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

201 parameter(s) across 49 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: bet_search, campaign_create, capability_create, capability_get, capability_link_work_item and 44 more

Loading this server's tool list costs an agent ~42,133 tokens before any work — more than 99% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

In the last 30 days: 0 tool(s) removed and 12 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/app.outcomet/mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/app.outcomet/mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fapp.outcomet%2Fmcp.svg)](https://glimind.com/server/mcp-registry%2Fapp.outcomet%2Fmcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fapp.outcomet%2Fmcp?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fapp.outcomet%2Fmcp.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:336890d4af1e2a58…, first seen 2026-11-16, included at leaf 303241 of 384,974. Version history · verify what your client received.

Tools (107)

Compare: most reliable retrieval servers · most reliable search servers · most reliable data servers · most reliable communication servers · most reliable other servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the Outcomet MCP server down right now?

As of 2026-11-22 19:26 UTC, the Outcomet MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 1 minutes.

How many tools does Outcomet MCP server provide?

Outcomet MCP server advertises 107 tools, including bet_get, bet_search, bet_upsert, campaign_create, campaign_get.

How do I install Outcomet MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.outcomet.app/mcp

Is the Outcomet MCP server safe to connect to an AI agent?

Glimind scanned all 107 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Outcomet MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve