Search / io.github.hengkp/rtcf
rtcf
R0· no sign-inTurns rough requests into sharp Role/Task/Context/Format prompts. Thai and English.
v1.0.0 · active · repository · website · descriptor JSON · versions
Search / io.github.hengkp/rtcf
R0· no sign-inTurns rough requests into sharp Role/Task/Context/Format prompts. Thai and English.
v1.0.0 · active · repository · website · descriptor JSON · versions
{
"mcpServers": {
"rtcf": {
"type": "http",
"url": "https://rtcf.happlen.com/api/mcp"
}
}
}claude mcp add --transport http rtcf https://rtcf.happlen.com/api/mcp[mcp_servers.rtcf]
url = "https://rtcf.happlen.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rtcf": {
"type": "remote",
"url": "https://rtcf.happlen.com/api/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"rtcf": {
"type": "http",
"url": "https://rtcf.happlen.com/api/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=rtcf&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vcnRjZi5oYXBwbGVuLmNvbS9hcGkvbWNwIn0%3D"
}{
"servers": {
"rtcf": {
"type": "http",
"url": "https://rtcf.happlen.com/api/mcp"
}
}
}{
"mcpServers": {
"rtcf": {
"httpUrl": "https://rtcf.happlen.com/api/mcp"
}
}
}extensions:
"rtcf":
enabled: true
name: "rtcf"
type: streamable_http
uri: "https://rtcf.happlen.com/api/mcp"
timeout: 300
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28protocol.statelessonly applies to 2026-07-28 serversprotocol.transportstreamable HTTPprotocol.list_ttlonly applies to 2026-07-28 serversauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_lengthdescriptions are concisetools.schemasevery tool has an object input schematools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky onestools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: improve_prompt (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); improve_followup (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); build_prompt (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)tools.token_costabout 672 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changesno tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+repository +namespace-matches-repo +website +reachable +uptime-100% ~updated-99d-ago
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://rtcf.happlen.com/api/mcp streamable-http | none | yes | 100% | 227 ms | 2025-11-25 | 2026-10-19 |
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. |
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. |
Schemas: list_tools.
{
"name": "io.github.hengkp/rtcf",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-09-29/server.schema.json",
"remotes": [
{
"url": "https://rtcf.happlen.com/api/mcp",
"type": "streamable-http"
}
],
"version": "1.0.0",
"repository": {
"url": "https://github.com/hengkp/rtcf-mcp",
"source": "github"
},
"websiteUrl": "https://rtcf.happlen.com",
"description": "Turns rough requests into sharp Role/Task/Context/Format prompts. Thai and English."
}