Storskarvia

endpoint

https://storskarvia.com/mcp/

protocol

streamable-http ·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 Storskarvia live?

Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.

Is Storskarvia free to use?

Partly — some of its tools are open, others need a key or payment.

What tools does Storskarvia have?

10 tools: get_guide, ground_claim, submit_findings, get_findings, prepare_factcheck, list_guides, get_skarvia_info, list_features, ….

Is Storskarvia 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.

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.

• list_guides reads open 6h ago

  Titles, 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.

  mcp-tool

  12345

  {
    "type": "object",
    "title": "list_guidesArguments",
    "properties": {}
  }

  arguments 5 lines copy
• get_skarvia_info reads open 17h ago

  What 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.

  mcp-tool

  12345

  {
    "type": "object",
    "title": "get_skarvia_infoArguments",
    "properties": {}
  }

  arguments 5 lines copy
• list_features reads open 17h ago

  The AI staff on Storskarvia and what each member actually does. Source: the "On staff" section of the current landing page.

  mcp-tool

  12345

  {
    "type": "object",
    "title": "list_featuresArguments",
    "properties": {}
  }

  arguments 5 lines copy
• get_pricing reads open 6h ago

  Current 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. The note here used to say payments "aren't enabled yet" unconditionally, which went on being served after they were switched on, and the tiers listed full price while every human-facing surface offered a founding seat at half of it. An agent asked what Storskarvia costs answered with a price nobody was being charged and omitted the one on offer.

  mcp-tool

  12345

  {
    "type": "object",
    "title": "get_pricingArguments",
    "properties": {}
  }

  arguments 5 lines copy
• list_my_projects reads auth-required 17h ago

  The 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.

  mcp-tool

  12345

  {
    "type": "object",
    "title": "list_my_projectsArguments",
    "properties": {}
  }

  arguments 5 lines copy
• get_guide reads unknown 13h ago

  Summary and URL for one guide, looked up by slug. Call list_guides first to get valid slugs.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "title": "get_guideArguments",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "title": "Slug"
      }
    }
  }

  arguments 13 lines copy
• ground_claim reads unknown never probed

  Step 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. Requires a personal Storskarvia API key as a Bearer token (this is not an open retrieval API).

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "title": "ground_claimArguments",
    "required": [
      "claim"
    ],
    "properties": {
      "claim": {
        "type": "string",
        "title": "Claim"
      }
    }
  }

  arguments 13 lines copy
• submit_findings changes data unknown never probed

  Step 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. `disclosure` must be REQUIRED_DISCLOSURE copied verbatim -- proof the user was shown it before findings were presented -- or this raises a ToolError instead of storing anything. Each item in `findings` must have a non-empty quote/explanation, problem in {"contradicted","misleading"}, and a non-empty sources list; findings missing any of those are rejected wholesale (nothing partial is stored).

  mcp-tool

  123456789101112131415161718192021222324252627

  {
    "type": "object",
    "title": "submit_findingsArguments",
    "required": [
      "document_id",
      "disclosure",
      "findings"
    ],
    "properties": {
      "findings": {
        "type": "array",
        "items": {
          "type": "object",
          "additionalProperties": true
        },
        "title": "Findings"
      },
      "disclosure": {
        "type": "string",
        "title": "Disclosure"
      },
      "document_id": {
        "type": "integer",
        "title": "Document Id"
      }
    }
  }

  arguments 27 lines copy
• get_findings reads unknown 13h ago

  Findings 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.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "title": "get_findingsArguments",
    "required": [
      "check_id"
    ],
    "properties": {
      "check_id": {
        "type": "integer",
        "title": "Check Id"
      }
    }
  }

  arguments 13 lines copy
• prepare_factcheck reads unknown 13h ago

  Step 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(claim) once per checkable claim you extract from `text`, then submit_findings(...) to store results.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "title": "prepare_factcheckArguments",
    "required": [
      "document_id"
    ],
    "properties": {
      "document_id": {
        "type": "integer",
        "title": "Document Id"
      }
    }
  }

  arguments 13 lines copy

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

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.