mcpbeat Sign in

Craft MCP Server

not responding

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

Illumora Craft — evidence-augmented prompt compile for agents via remote MCP (OAuth) or local stdio.

Uptime history 51 days of history · worst day 0%
51 days agonow
2.2%
Uptime 24h
4 of 182 checks
Tools
hidden behind auth
652 ms
Response time
average over 24h
open, no key
Access
streamable-http

Craft does not always answer

Over the last week it answered 12.9% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

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

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

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Endpoints

URLTransportStateLatencyChecked
https://mcp.illumora.io streamable-http answering 224 ms 10 min ago
https://illumora.io/api/mcp streamable-http answering 154 ms 10 min ago

Alternatives to Craft

same job, measured the same way
StremAI
by thomasjumper

StremAI MCP: shared memory for AI coding agents. Connected agents can recall. OAuth + local stdio.

76 installs/wk answering
Artifacta
by artifacta

Artifact store for AI agents. Hosted OAuth at mcp.artifacta.io/mcp; local stdio via npm/PyPI.

155 installs/wk answering
Neither MCP
by stonianua

Selected project context for Cursor & Claude Desktop via local stdio MCP, with source evidence.

30 installs/wk local only
AIppocampus
by sapientropic

Local-first, source-backed continuity for AI agents via stdio MCP.

137 installs/wk local only
Madar
by mohanagy

Authenticated local evidence paths for JavaScript and TypeScript coding agents.

130 installs/wk local only
Hooklayer
by khan-ashifur

Viral-content intelligence for AI agents — 7 read-only MCP tools, evidence-layer scoring.

12 tools answering
Provena Agent Memory
by admiralpunk

Evidence-backed, explainable persistent memory for MCP-compatible AI agents.

local only
Citra
by sylphxai

Local-first PDF evidence for agents: structure, tables, OCR, and citations. SDK · CLI · MCP.

690 installs/wk local only

Craft — questions

Answers built from our own checks of this server.

Is Craft working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 4 of 182 checks got a reply (2.2%), average response time 652 ms. The bar chart above shows every period we have measured.
The registry lists Craft 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 Craft?
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 Craft need an API key?
No. Craft 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 Craft?
It answers our handshake in 652 ms on average, which is faster than 20% 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.