mcpbeat

Skew MCP Server

site.skew/skew
not responding

Skew is listed as active in the registry but did not answer our last check. It exposes 4 tools.

Authored design service: one-of-one landing pages, pitch decks, and research-grounded briefs.

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

Uptime history 39 hours of history · worst hour 0%
39 hours agonow
0.0%
Uptime 24h
0 of 92 checks
4
Tools
read from the server
101 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 skew --transport http https://skew.site/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "skew": {
      "url": "https://skew.site/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.skew]
url = "https://skew.site/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "skew": {
      "url": "https://skew.site/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "skew": {
      "url": "https://skew.site/api/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

generate
generate_brief
Generate a research-grounded brief from a topic and optional source URLs. Persists on stream close at /b/{slug}.
generate_deck
Generate a one-of-one pitch deck from a brief and slide count. Persists on stream close at /d/{slug}.
generate_landing
Stream a one-of-one landing page from a one-paragraph brief. Persists on stream close at /p/{slug}.
artifact
fetch_artifact
Retrieve a previously generated artifact (landing, deck, or brief) by slug. Returns HTML.

Endpoints

URLTransportStateLatencyChecked
https://skew.site/api/mcp streamable-http answering 101 ms 3 min ago

Skew — questions

Answers built from our own checks of this server.

What can Skew do?
It exposes 4 tools, read directly from the server on our last check. Among them: fetch_artifact, generate_brief, generate_deck, generate_landing. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Skew working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 101 ms. The bar chart above shows every period we have measured.
Is Skew 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 Skew 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 Skew?
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 Skew need an API key?
No. Skew completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.