FICTURN — Short Fiction Inside ChatGPT
REMOTE · FICTURN.THOMAS-JUDES.WORKERS.DEV · SCANNED SEP 20
Short, finished fiction to discover by mood, genre or reading time inside ChatGPT.
Available components
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
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability82
- 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 341 tokens (~68/item across 5 items; 3 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 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 current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
How do I install the FICTURN — Short Fiction Inside ChatGPT MCP server?
FICTURN — Short Fiction Inside ChatGPT is a hosted endpoint at https://ficturn.thomas-judes.workers.dev/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 · ficturn.thomas-judes.workers.dev
claude mcp add --transport http thomasjudes-del-ficturn 'https://ficturn.thomas-judes.workers.dev/mcp'
{
"mcpServers": {
"thomasjudes-del-ficturn": {
"url": "https://ficturn.thomas-judes.workers.dev/mcp"
}
}
} {
"servers": {
"thomasjudes-del-ficturn": {
"type": "http",
"url": "https://ficturn.thomas-judes.workers.dev/mcp"
}
}
} [mcp_servers.thomasjudes-del-ficturn] url = "https://ficturn.thomas-judes.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"thomasjudes-del-ficturn": {
"type": "remote",
"url": "https://ficturn.thomas-judes.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add thomasjudes-del-ficturn --url 'https://ficturn.thomas-judes.workers.dev/mcp' --transport streamable-http
mcp_servers:
thomasjudes-del-ficturn:
url: "https://ficturn.thomas-judes.workers.dev/mcp" {
"McpServers": {
"thomasjudes-del-ficturn": {
"Transport": "http",
"Url": "https://ficturn.thomas-judes.workers.dev/mcp"
}
}
} assistant mcp add thomasjudes-del-ficturn -t streamable-http -u 'https://ficturn.thomas-judes.workers.dev/mcp'
{
"mcpServers": {
"thomasjudes-del-ficturn": {
"type": "http",
"url": "https://ficturn.thomas-judes.workers.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Probed https://ficturn.thomas-judes.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=thomas-judes.workers.dev | CN=WE1,O=Google Trust Services,C=US | 12 Aug 2026 | 10 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | dfedffbd43ad4f690e6d8ff0e4dbf9d1 |
| SANs: thomas-judes.workers.dev, *.thomas-judes.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ficturn.thomas-judes.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ficturn.thomas-judes.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://ficturn.thomas-judes.workers.dev/mcp | Inconclusive | 405 |
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 →
browse_stories Browse FICTURN stories ~100
Browse a library of short, finished, pre-authored fiction to read directly inside ChatGPT. Use for generic requests such as a short story, quick fiction, a five-minute read, romance, romantic suspense, eerie or uncanny horror, mystery, near-future science fiction, AI thriller, speculative fiction, or when the user wants to choose a story by mood, genre or reading time. The user does not need to know the name FICTURN.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
next_fragment Continue a FICTURN story ~73
Return the requested next fragment of the fixed FICTURN story already open in the reader. Never invent, rewrite, summarise, or skip story fragments.
| Name | Type | Req | Description |
|---|---|---|---|
| part | integer | yes | Exact fragment number to display. |
| storyId | string | – | Story currently being read. Defaults to the-safehouse-rule for legacy clients. |
No output schema declared.
No examples provided.
start_story Start a FICTURN story ~130
Open one short, finished, pre-authored story directly inside ChatGPT in the FICTURN reader. Use when a user asks to read short fiction or requests a story by genre, mood or time: romance or romantic suspense, second chance, forced proximity, eerie or uncanny horror, mystery, near-future science fiction, AI thriller or speculative fiction. If no story is specified, open The Safehouse Rule. The user does not need to mention FICTURN by name.
| Name | Type | Req | Description |
|---|---|---|---|
| storyId | string | – | Story to open: the-safehouse-rule, room-713, or the-last-reply. |
No output schema declared.
No examples provided.
What is the FICTURN — Short Fiction Inside ChatGPT MCP server?
FICTURN — Short Fiction Inside ChatGPT is an MCP server listed in the public MCP registry as io.github.thomasjudes-del/ficturn. Short, finished fiction to discover by mood, genre or reading time inside ChatGPT. This page covers its hosted endpoint (https://ficturn.thomas-judes.workers.dev/mcp).
Is the FICTURN — Short Fiction Inside ChatGPT MCP server safe to use?
FICTURN — Short Fiction Inside ChatGPT scores 79 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 FICTURN — Short Fiction Inside ChatGPT MCP server expose?
FICTURN — Short Fiction Inside ChatGPT exposes 3 tools: browse_stories, start_story, next_fragment. Their descriptions and schemas cost roughly 303 tokens of context every time the server is loaded.
Does the FICTURN — Short Fiction Inside ChatGPT MCP server require authentication?
No. We connected to FICTURN — Short Fiction Inside ChatGPT without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FICTURN — Short Fiction Inside ChatGPT MCP server still maintained?
FICTURN — Short Fiction Inside ChatGPT is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.