Rtcf is a remote MCP server that gives an AI agent 3 tools, among them build_prompt, improve_followup, improve_prompt. It answers at https://rtcf.happlen.com/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 22 October 2026, succeeded.
Turns rough requests into sharp Role/Task/Context/Format prompts. Thai and English.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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. Inputs: role, task, context, format |
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 Inputs: next_request, conversation_summary, original_goal |
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 e Inputs: prompt, target |
Every block below points at https://rtcf.happlen.com/api/mcp. Pick your client and copy.
claude mcp add --transport http rtcf https://rtcf.happlen.com/api/mcp
{
"mcpServers": {
"rtcf": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://rtcf.happlen.com/api/mcp"]
}
}
}{
"mcpServers": {
"rtcf": {
"url": "https://rtcf.happlen.com/api/mcp"
}
}
}{
"servers": {
"rtcf": {
"type": "http",
"url": "https://rtcf.happlen.com/api/mcp"
}
}
}{
"context_servers": {
"rtcf": {
"url": "https://rtcf.happlen.com/api/mcp"
}
}
}{
"mcpServers": {
"rtcf": {
"serverUrl": "https://rtcf.happlen.com/api/mcp"
}
}
}{
"mcpServers": {
"rtcf": {
"url": "https://rtcf.happlen.com/api/mcp"
}
}
}name: Rtcf
version: 0.0.1
schema: v1
mcpServers:
- name: Rtcf
type: streamable-http
url: https://rtcf.happlen.com/api/mcp{
"mcpServers": {
"rtcf": {
"httpUrl": "https://rtcf.happlen.com/api/mcp"
}
}
}{
"mcpServers": {
"rtcf": {
"type": "http",
"url": "https://rtcf.happlen.com/api/mcp"
}
}
}{
"mcpServers": {
"rtcf": {
"url": "https://rtcf.happlen.com/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Frtcf.happlen.com%2Fapi%2Fmcp&type=streamable_http&id=rtcf&name=Rtcf
It answered our last check on 22 October 2026 in 192 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
3, as returned by the server's own tools/list on 14 September 2026: build_prompt, improve_followup, improve_prompt.
It answered our last check on 22 October 2026 in 192 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://rtcf.happlen.com/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.hengkp. Endpoint host: rtcf.happlen.com. ARD identifier: urn:air:io.github.hengkp:mcp:rtcf.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.