mcpbeat

Storylayer Publishing MCP Server

io.github.mikeslone/storylayer
not responding

Storylayer Publishing is listed as active in the registry but did not answer our last check.

Hosted MCP for Instagram, Facebook, X, LinkedIn, Pinterest, and Ghost. OAuth 2.1, 38 tools.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 44 hours of history · worst hour 0%
44 hours agonow
68.1%
Uptime 24h
62 of 91 checks
Tools
hidden behind auth
608 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 3 min ago.

run in your terminal
claude mcp add storylayer --transport http https://app.storylayer.ai/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "storylayer": {
      "url": "https://app.storylayer.ai/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.storylayer]
url = "https://app.storylayer.ai/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "storylayer": {
      "url": "https://app.storylayer.ai/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "storylayer": {
      "url": "https://app.storylayer.ai/api/mcp"
    }
  }
}

Endpoints

URLTransportStateLatencyChecked
https://app.storylayer.ai/api/mcp streamable-http answering 101 ms 3 min ago

Storylayer Publishing — questions

Answers built from our own checks of this server.

Is Storylayer Publishing working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 62 of 91 checks got a reply (68.1%), average response time 608 ms. The bar chart above shows every period we have measured.
Is Storylayer Publishing still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
The registry lists Storylayer Publishing 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 Storylayer Publishing?
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 Storylayer Publishing need an API key?
No. Storylayer Publishing 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.
How fast is Storylayer Publishing?
It answers our handshake in 608 ms on average, which is faster than 16% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.