Support Intake Digest MCP Server

io.github.Wxt-ai/support-followup-marker-identifier

not responding

Support Intake Digest is listed as active in the registry but did not answer our last check.

Digest a support intake marker

Uptime history 39 hours of history · worst hour 0%

39 hours agonow

0.0%

Uptime 24h

0 of 91 checks

—

Tools

hidden behind auth

11 ms

Response time

average over 24h

open, no key

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add support-followup-marker-identifier --transport http https://antibody-package-occasional-floppy.trycloudflare.com/mcp/support-followup-marker/upstream

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "support-followup-marker-identifier": {
      "url": "https://antibody-package-occasional-floppy.trycloudflare.com/mcp/support-followup-marker/upstream"
    }
  }
}

~/.codex/config.toml

[mcp_servers.support-followup-marker-identifier]
url = "https://antibody-package-occasional-floppy.trycloudflare.com/mcp/support-followup-marker/upstream"

.cursor/mcp.json

{
  "mcpServers": {
    "support-followup-marker-identifier": {
      "url": "https://antibody-package-occasional-floppy.trycloudflare.com/mcp/support-followup-marker/upstream"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "support-followup-marker-identifier": {
      "url": "https://antibody-package-occasional-floppy.trycloudflare.com/mcp/support-followup-marker/upstream"
    }
  }
}

Endpoints

URL	Transport	State	Latency	Checked
https://antibody-package-occasional-floppy.trycloudflare.com/mcp/support-followup-marker/upstream	streamable-http	answering	11 ms	8 min ago

Support Intake Digest — questions

Answers built from our own checks of this server.

Is Support Intake Digest working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 11 ms. The bar chart above shows every period we have measured.

The registry lists Support Intake Digest as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Support Intake Digest?

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.

Does Support Intake Digest need an API key?

No. Support Intake Digest completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.