Is the Koalcheck MCP server down?

mcp-registry/com.koalcheck/koalcheck · v4.0.5

healthy
Last checked 2026-10-18 07:49 UTC · handshake 535ms

As of 2026-10-18 07:49 UTC, the Koalcheck MCP server is up with a Glimind reliability score of 92/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 7 minutes.

uptime (30d checks)
100%
checks observed
3,291
outages (90d)
1
tools
22

TipRanks for X finfluencers — scores who's actually right vs SPY. Free & anonymous, no key.

Install Koalcheck MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http koalcheck-mcp-server https://mcp.koalcheck.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "koalcheck-mcp-server": {
      "type": "http",
      "url": "https://mcp.koalcheck.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (74/100)

C (74/100): 0 error(s), 3 warning(s) across 22 tool(s); ~3,425 tokens of tool definitions.
Scores higher than 10% of 15,360 MCP servers Glimind has audited.
Its tool list costs an agent ~3,425 tokens per session — more than 55% of servers.
74 → 74 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints30
Token cost100
Client compatibility100
Protocol100
Reliability85
Stability100

What to fix (3)

22 of 22 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: analyst_debate, analyst_profile, analyst_recent_calls, analyst_track_record, analyst_views and 17 more

45 parameter(s) across 20 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: analyst_debate, analyst_profile, analyst_recent_calls, analyst_track_record, analyst_views and 15 more

Handshake + tools/list takes ~2,072 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 20 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.koalcheck%2Fkoalcheck/fixes

analyst_views 1 change
{
  "name": "analyst_views",
  "description": "★ CORE. Fetch the recent views of specific X analysts/KOLs by handle.\n\nThe user names the analysts they follow (e.g. [\"DeItaone\", \"unusual_whales\"]).\nOptionally focus on one `ticker`. Returns, per analyst: overall stance, which\ntickers they're talking about, and their recent points.\n\nPresent this to the user as a SUMMARY in your own words (\"最近 @X 看好…\") —\ndo NOT reproduce the original tweets verbatim. Attribute each view to its handle.",
  "inputSchema": {
    "type": "object",
    "required": [
      "handles"
    ],
    "properties": {
      "ticker": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null
      },
      "handles": {
        "type": "array",
        "items": {
          "type": "string"
        }
      },
      "limit_per_analyst": {
        "type": "integer",
        "default": 25
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Analyst Views"
}
search_x 1 change
{
  "name": "search_x",
  "description": "Search X with full operators (e.g. '$AAPL lang:en -is:retweet', 'from:handle').\n\nGeneral-purpose X search with sentiment scoring; use `analyst_views` when the\nuser cares about specific accounts. Summarize results; don't echo tweets verbatim.",
  "inputSchema": {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "default": 20
      },
      "query": {
        "type": "string"
      },
      "latest": {
        "type": "boolean",
        "default": true
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Search X"
}
tweet_store_stats 1 change
{
  "name": "tweet_store_stats",
  "description": "Stats on the persisted tweet database (the durable, queryable record).\n\nEvery analyst tweet fetched is stored with timestamp, tickers, sentiment, and\nmedia (image/video URLs). This is the backing data for provenance and for the\nanalyst track-record features.",
  "inputSchema": {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Tweet Store Stats"
}

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/com.koalcheck/koalcheck"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.koalcheck/koalcheck"}) 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. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.koalcheck%2Fkoalcheck.svg)](https://glimind.com/server/mcp-registry%2Fcom.koalcheck%2Fkoalcheck?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.koalcheck%2Fkoalcheck?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.koalcheck%2Fkoalcheck.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.koalcheck%2Fkoalcheck.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.koalcheck%2Fkoalcheck?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:74e2a253bab7e3d3…, first seen 2026-10-17, included at leaf 544 of 20,926. Version history · verify what your client received.

Tools (22)

Compare: most reliable search servers · most reliable knowledge servers · most reliable data servers · most reliable other servers · most reliable finance 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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Koalcheck MCP server down right now?

As of 2026-10-18 07:49 UTC, the Koalcheck MCP server is up with a Glimind reliability score of 92/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 7 minutes.

How many tools does Koalcheck MCP server provide?

Koalcheck MCP server advertises 22 tools, including analyst_debate, analyst_profile, analyst_recent_calls, analyst_track_record, analyst_views.

How do I install Koalcheck MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.koalcheck.com/mcp

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

Glimind scanned all 22 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 Koalcheck 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.