_ registry / mcp http-sse · checked 2h ago

FICTURN

https://ficturn.thomas-judes.workers.dev

Registry code: ae581954b527cb7f

api record

Short, finished fiction to discover by mood, genre or reading time inside ChatGPT.

from a public catalogue that lists it, not from the operator

endpoint
https://ficturn.thomas-judes.workers.dev/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is FICTURN live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is FICTURN free to use?
Yes — the hub reached it with no key and no payment.
What tools does FICTURN have?
3 tools: next_fragment, browse_stories, start_story.
Is FICTURN safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.6%

90 days 99.8%· all time 99.8%

latency
211ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 410 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • browse short fiction stories by mood
  • open a story in the reader
  • read the next story fragment
takes → gives
text → text
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
2 open 1 never probed 2 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • browse_stories reads open 2h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 lines
  • start_story reads open 2h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "storyId": {
          "enum": [
            "the-safehouse-rule",
            "room-713",
            "the-last-reply"
          ],
          "type": "string",
          "description": "Story to open: the-safehouse-rule, room-713, or the-last-reply."
        }
      }
    }
    arguments 15 lines
  • next_fragment reads unknown 2h ago

    Return the requested next fragment of the fixed FICTURN story already open in the reader. Never invent, rewrite, summarise, or skip story fragments.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "part"
      ],
      "properties": {
        "part": {
          "type": "integer",
          "maximum": 5,
          "minimum": 2,
          "description": "Exact fragment number to display."
        },
        "storyId": {
          "enum": [
            "the-safehouse-rule",
            "room-713",
            "the-last-reply"
          ],
          "type": "string",
          "description": "Story currently being read. Defaults to the-safehouse-rule for legacy clients."
        }
      }
    }
    arguments 24 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id ae581954b527cb7f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ae581954b527cb7f/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/ae581954b527cb7f/badge.svg)](https://brick.blue/agent/ae581954b527cb7f?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.