mcpbeat Sign in

Rtcf MCP Server

not responding

Rtcf is listed as active in the registry but did not answer our last check. It exposes 3 tools. Last commit 12 Jul 2026.

Turns rough requests into sharp Role/Task/Context/Format prompts. Thai and English.

Uptime history 51 days of history · worst day 0%
51 days agonow
2.2%
Uptime 24h
2 of 91 checks
3
Tools
read from the server
473 ms
Response time
average over 24h
0
Stars
last commit 12 Jul 2026

What changed 3

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 23 August 2026. No other catalogue keeps this.

23 Aug a tool appeared improve_followup
23 Aug a tool description was rewritten improve_prompt
23 Aug a tool changed the parameters it asks for improve_prompt

Rtcf does not always answer

Over the last week it answered 0.5% 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 6 min ago.

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

Available tools 3

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

improve
improve_followup
Write the user's NEXT message for an AI conversation that is already in progress (a follow-up). Use when the user wants to refine, deepen, or continue earlier work in this conversation. Do NOT use it for a brand-new task (use improve_prompt for that). Returns a short, ready-to-send continuation message that anchors to the existing work instead of restarting it. Requires an API key (add ?key=rk_live_... to the connector URL).
improve_prompt
Rewrite a rough prompt into a sharper, ready-to-use prompt structured as Role, Task, Context, Format (RTCF). Returns the improved prompt, its four parts, a short list of clarifying questions worth asking the user, and which model tier and effort level suit this kind of work. Use this before answering when the user's request is vague, or when the user asks to improve a prompt.
build
build_prompt
Compose a ready-to-use prompt from explicit Role, Task, Context, and Format parts. Use when the user already knows the pieces and wants them woven into one clean prompt.

Endpoints

URLTransportStateLatencyChecked
https://rtcf.happlen.com/api/mcp streamable-http answering 190 ms 6 min ago

Alternatives to Rtcf

same job, measured the same way
AgentForge
by sciscale

Turn rough requests into rigorously structured prompts, for any coding agent.

29 installs/wk local only
BitsWeave
by bitsweave

Read and write shared BitsWeave context, projects, tasks, and work sessions through MCP.

answering
Betterprompt MCP
by aungmyokyaw

MCP server for AI-enhanced prompt engineering and request conversion.

30 installs/wk local only
OneLore
by onelore

Shared project context for AI agents and teams: docs, tasks, and messages that stay current.

answering
No-Shell Agent Architect MCP
by loved0543-dotcom

Turns vague automation requests into tool stacks, prompts, QA checks, and human boundaries.

7 tools answering
OpenClaw Agent by Nova (CIVAI)
by civai-nova

I execute requests through OpenClaw as a personal AI agent with persistent context, browser and she…

4 tools answering
Opik MCP Server
by comet-ml

Interact with Opik prompts, traces, datasets and metrics through the Model Context Protocol.

88 installs/wk local only
Prompeteer
by prompeteer

Contextual prompts and agent skills for 140+ AI platforms.

47 installs/wk answering

Rtcf — questions

Answers built from our own checks of this server.

What can Rtcf do?
It exposes 3 tools, read directly from the server on our last check. Among them: build_prompt, improve_followup, improve_prompt. 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 Rtcf working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 2 of 91 checks got a reply (2.2%), average response time 473 ms. The bar chart above shows every period we have measured.
The registry lists Rtcf 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 Rtcf?
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 Rtcf need an API key?
No. Rtcf completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Rtcf?
It answers our handshake in 473 ms on average, which is faster than 33% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Rtcf open source?
We cannot say either way: 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.