Storskarvia

com.storskarvia/writing-studio · v1.0.0 · agents-and-memory

Storskarvia is healthy: it completed an MCP handshake in 945 ms and exposes 10 tools.

Writing studio for novels and screenplays: read your projects and run cited fact-checks.

Endpoint: https://storskarvia.com/mcp/ (streamable-http)

No repository listed · Website · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count10
Latency945 ms
Last checked (UTC)2026-10-16T00:30:10.337Z

Health history

Checked (UTC)StatusLatencyError
2026-10-16T00:30:10.337ZHealthy945
2026-10-14T22:05:45.086ZHealthy3313

Tools (10)

get_skarvia_infoWhat Storskarvia is and how it's positioned. A professional writing studio for novelists, screenwriters, and video scriptwriters, staffed by an AI team that fact-checks, researches, and tracks continuity -- but never writes the user's prose for them.
list_featuresThe AI staff on Storskarvia and what each member actually does. Source: the "On staff" section of the current landing page.
get_pricingCurrent Storskarvia pricing tiers, features, and monthly fact-check quotas. Built from config.PLANS, the same list /pricing renders from, so this can no longer drift from the page the way it did while it was kept by hand. The founder block is read live rather than described in prose. T
list_guidesTitles, slugs, and URLs of Storskarvia's evergreen craft/how-to guides. Reads the live GUIDES list straight from app.main (imported lazily -- see the comment on the import below) so this can never drift out of sync with what's actually published at /guides.
get_guideSummary and URL for one guide, looked up by slug. Call list_guides first to get valid slugs.
list_my_projectsThe authenticated user's Storskarvia projects (novels, screenplays, video scripts), each with the id, title and binder folder of its documents in binder order. A document id is what prepare_factcheck and submit_findings take. Requires a personal Storskarvia API key as a Bearer token.
get_findingsFindings for one of the authenticated user's fact-check or continuity runs. Ownership is enforced -- a check_id belonging to another user raises an error rather than leaking their data.
prepare_factcheckStep 1 of a bring-your-own-agent fact-check. Fetches one of the authenticated user's documents (ownership enforced) plus the exact disclosure and method your agent MUST follow. Requires a personal Storskarvia API key as a Bearer token. After this, call ground_claim(c
ground_claimStep 2 of a bring-your-own-agent fact-check. Runs Storskarvia's own server-side retrieval (Wikipedia + searxng) for one claim and returns the sources -- no verdict, no judgment. Your agent should judge the claim ONLY against these returned sources, never outside knowledge.
submit_findingsStep 3 of a bring-your-own-agent fact-check. Stores your agent's findings as a real Storskarvia Check, visible on the same findings punch list as a staff-run check. Requires a personal Storskarvia API key as a Bearer token, and ownership of `document_id` is enforced.