com.storskarvia/writing-studio

Est-ce que com.storskarvia/writing-studio est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.storskarvia/writing-studio » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 10 outils

• get_findings≈ 143 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • check_id · integer · requis

  Exemple d'appel

  {"name": "get_findings", "arguments": {"check_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_guide≈ 117 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • slug · string · requis

  Exemple d'appel

  {"name": "get_guide", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_pricing≈ 244 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_pricing", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_skarvia_info≈ 145 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_skarvia_info", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ground_claim≈ 196 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • claim · string · requis

  Exemple d'appel

  {"name": "ground_claim", "arguments": {"claim": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_features≈ 140 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_features", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": []}}

• list_guides≈ 174 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_guides", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": []}}

• list_my_projects≈ 182 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_my_projects", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": []}}

• prepare_factcheck≈ 205 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • document_id · integer · requis

  Exemple d'appel

  {"name": "prepare_factcheck", "arguments": {"document_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• submit_findings≈ 346 tokens

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

  Paramètres, retour & exemple (3)

  Paramètres

  • findings · array · requis
  • disclosure · string · requis
  • document_id · integer · requis

  Exemple d'appel

  {"name": "submit_findings", "arguments": {"findings": [], "disclosure": "texte", "document_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://storskarvia.com/mcp/