io.github.hengkp/rtcf
REMOTE · RTCF.HAPPLEN.COM
Turns rough requests into sharp Role/Task/Context/Format prompts. Thai and English.
Available components
Last scanned (18 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 443 tokens (~110/item across 4 items; 3 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −1
- Stability: pass → 0.97 functional
- 13 Oct 26 −1
- Schema quality: fail → pass ▲ functional
- The server now declares the “resources” capability functional
- First check of Capabilities: pass functional
- Schema quality: excellent → good functional
- New resource “RTCF result card” functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 0
- Tool “improve_prompt” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- New prompt “rtcf-next” functional
- New tool “improve_followup” functional
- “improve_prompt” added an optional parameter “target” cosmetic
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://rtcf.happlen.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.happlen.com | CN=YR2,O=Let's Encrypt,C=US | 3 Oct 2026 | 1 Jan 2027 | RSA 2048 | SHA256-RSA | 529a04694da3bf61f1ea2bd553a343b51fd |
| SANs: *.happlen.com, happlen.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of rtcf.happlen.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| happlen.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://*.supabase.co; font-src 'self' data:; connect-src 'self' https://*.supabase.co wss://*.supabase.co; frame-ancestors 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://rtcf.happlen.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://rtcf.happlen.com/api/mcp | HTTPS enforced | 308 | https://rtcf.happlen.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
build_prompt ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Background the AI needs |
| format | string | – | How the answer should be shaped |
| role | string | yes | Who the AI should be |
| task | string | yes | What the AI should do |
No output schema declared.
No examples provided.
improve_followup ~180
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).
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_summary | string | – | 2-6 sentences summarizing what the AI last produced and any key decisions so far (you can see the conversation; the tool cannot) |
| next_request | string | yes | What the user wants next, or where they are stuck, in their own words |
| original_goal | string | – | The original goal or starter prompt of the conversation, if known |
No output schema declared.
No examples provided.
improve_prompt ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | The rough prompt or request to restructure |
| target | string | – | Which AI family will actually run the improved prompt ("claude" or "gpt"). Pass your own family so the wording is shaped for it and the model recommendation is concrete. Omit for a provider-neutral p… |
No output schema declared.
No examples provided.
How do I install the io.github.hengkp/rtcf MCP server?
io.github.hengkp/rtcf is a hosted endpoint at https://rtcf.happlen.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · rtcf.happlen.com
claude mcp add --transport http hengkp-rtcf 'https://rtcf.happlen.com/api/mcp'
What is the io.github.hengkp/rtcf MCP server?
io.github.hengkp/rtcf is an MCP server listed in the public MCP registry as io.github.hengkp/rtcf. Turns rough requests into sharp Role/Task/Context/Format prompts. Thai and English. This page covers its hosted endpoint (https://rtcf.happlen.com/api/mcp).
Is the io.github.hengkp/rtcf MCP server safe to use?
io.github.hengkp/rtcf scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.hengkp/rtcf MCP server expose?
io.github.hengkp/rtcf exposes 3 tools: improve_prompt, improve_followup, build_prompt. Their descriptions and schemas cost roughly 423 tokens of context every time the server is loaded.
Does the io.github.hengkp/rtcf MCP server require authentication?
No. We connected to io.github.hengkp/rtcf without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.hengkp/rtcf MCP server still maintained?
io.github.hengkp/rtcf is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.