mcpbeat Sign in

Slate MCP Server

answering

Slate is answering right now. Last checked 2 min ago.

Your own SLATE health data in your AI assistant: read, trend, plan and log. Never suggests a dose.

Uptime history 9 days of history
9 days agonow
100.0%
Uptime 24h
91 of 91 checks
Tools
hidden behind auth
258 ms
Response time
average over 24h
API key or OAuth
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Slate every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add slate --transport http https://ydyrdehcbyrfbnjqgdoi.functions.supabase.co/slate-mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "slate": {
      "url": "https://ydyrdehcbyrfbnjqgdoi.functions.supabase.co/slate-mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.slate]
url = "https://ydyrdehcbyrfbnjqgdoi.functions.supabase.co/slate-mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "slate": {
      "url": "https://ydyrdehcbyrfbnjqgdoi.functions.supabase.co/slate-mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "slate": {
      "url": "https://ydyrdehcbyrfbnjqgdoi.functions.supabase.co/slate-mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://ydyrdehcbyrfbnjqgdoi.functions.supabase.co/slate-mcp streamable-http needs key 236 ms 2 min ago

Alternatives to Slate

same job, measured the same way
Orquesta
by getorquesta

Read a project's prompts, logs and agents, and send new work to the agent on your own machines.

answering
Leaf
by readwithleaf

AI assistant integration for Leaf — track books, log reading sessions, and manage your library.

answering
LDAP Assistant MCP
by droideck

MCP server for 389 Directory Server health diagnostics, log analysis, and SOS-report investigation

54 installs/wk local only
SiteVitals
by tom18a

Monitor website health, uptime, SEO, security and performance via your AI assistant.

answering
Oura Ring MCP
by mitchhankins01

Connect your Oura Ring to Claude AI assistants. Health metrics with smart analysis tools.

107 installs/wk local only
A
Aether Wealth
by aetherwealth

Aether Wealth MCP for AI assistants: trades, alerts, market data, macro calendar & indicators.

507 installs/wk local only
Logmcp
by kascada

MCP server — read-only log access for AI assistants, without giving AI shell access.

local only
petromcp
by ameyxd

Local-first MCP server: read LAS well logs and DLIS files from your own disk.

166 installs/wk local only

Slate — questions

Answers built from our own checks of this server.

Why is there no tool list for Slate?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Slate working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 258 ms. The bar chart above shows every period we have measured.
How do I connect Slate?
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. You will need your own key or an OAuth login: it refuses anonymous clients.
Does Slate need an API key?
Yes. Every time we knock, Slate answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Slate?
It answers our handshake in 258 ms on average, which is faster than 63% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.