# Fictura (remote · mcp.fictura.co)

Paywalls, onboarding, subscription analytics, A/B tests, attribution and errors for mobile apps.

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.fictura.co`: 82/100 (this document), [markdown](https://verifymcp.io/servers/co-fictura-mcp/mcp.md), [page](https://verifymcp.io/servers/co-fictura-mcp/mcp)
- npm · `@fictura/mcp`: 39/100, [markdown](https://verifymcp.io/servers/co-fictura-mcp/fictura-mcp.md), [page](https://verifymcp.io/servers/co-fictura-mcp/fictura-mcp)

## Channel facts

- Endpoint: `https://mcp.fictura.co/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 14/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Fictura MCP server?

Fictura is a hosted endpoint at https://mcp.fictura.co/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.

### Claude

```bash
claude mcp add --transport http co-fictura-mcp 'https://mcp.fictura.co/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "co-fictura-mcp": {
      "url": "https://mcp.fictura.co/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-fictura-mcp": {
      "type": "http",
      "url": "https://mcp.fictura.co/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.co-fictura-mcp]
url = "https://mcp.fictura.co/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-fictura-mcp": {
      "type": "remote",
      "url": "https://mcp.fictura.co/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-fictura-mcp --url 'https://mcp.fictura.co/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-fictura-mcp:
    url: "https://mcp.fictura.co/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "co-fictura-mcp": {
      "Transport": "http",
      "Url": "https://mcp.fictura.co/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-fictura-mcp -t streamable-http -u 'https://mcp.fictura.co/mcp'
```

### Other

```json
{
  "mcpServers": {
    "co-fictura-mcp": {
      "type": "http",
      "url": "https://mcp.fictura.co/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 82, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] HSTS header: fail → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Stability: 0.17 → unverified
- [security regression] Transport: pass → fail
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified

### 2026-11-03 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 80, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (44)

### `search_docs` (~119 tokens)

Search Fictura documentation

Full-text search across the Fictura docs, grouped by page. Use this before answering any 'how do I…' question about the SDK, API, paywalls, entitlements, links or webhooks — the docs are the source of truth and are regenerated on every code change. Returns page paths; pass one to read_doc for the full text. No API key required.

Input parameters:

- `limit` (integer): Max pages to return (default 8)
- `query` (string, required): What to search for, e.g. 'purchases adapter'

### `list_docs` (~48 tokens)

List Fictura documentation pages

The full documentation index — every page path, grouped by section, with a one-line description. Use it to find the right page when a search term is hard to guess. No API key required.

### `read_doc` (~86 tokens)

Read a Fictura documentation page

The complete markdown of one documentation page. Accepts a site-relative path such as '/implementation/welcome/sdk-quickstart' (a full docs.fictura.co URL works too). If the path is wrong, the closest real paths come back as suggestions. No API key required.

Input parameters:

- `path` (string, required): Page path, e.g. /implementation/sdk-reference/expo-react-native

### `get_app_setup` (~91 tokens)

Get this app's Fictura credentials and endpoints

The real values needed to wire the Fictura SDK into a codebase: the API base URL, this app's publishable SDK key (gk_…), and the RevenueCat webhook URL. ALWAYS call this before generating integration code — never leave a placeholder API key in what you write. The SDK key is publishable and safe to commit in app source; it identifies the app, not a person.

### `get_setup_status` (~89 tokens)

Get integration and feature status

What is actually configured for this app: the setup checklist, every Fictura feature toggle and whether it is on, and which third-party integrations (Stripe, RevenueCat, Slack, Sentry, App Store Connect, …) are connected. Use it to check whether a feature is enabled before writing code that depends on it — a disabled tool is a server-side kill switch the SDK obeys.

### `get_analytics` (~133 tokens)

Get funnel, overview or cohort analytics

This app's real numbers. `overview` gives headline metrics (users, trials, trial→paid rate, events by name, cancel reasons, 14-day activity). `funnel` gives the ordered conversion funnel with per-step drop-off. `cohorts` compares behaviour across billing outcomes — what converted users did that cancelled users didn't. Below ~100 users in a step the sample is too small to read. `stores` splits paying users, purchases and revenue by App Store / Google Play / web and by storefront country (last 28 days).

Input parameters:

- `view` (string, required): Which analytics view to return

### `get_attribution_report` (~146 tokens)

Get attribution, install and KPI reporting

Where installs and revenue actually came from. `summary` is the headline attribution picture (installs, organic vs non-organic, revenue). `kpis` breaks the same window down by source, campaign, link or day. `installs` lists individual installs with their attribution. Defaults to the trailing 28 days.

Input parameters:

- `group_by` (string): For view=kpis (default source)
- `limit` (integer): For view=installs (default 100)
- `since` (string): YYYY-MM-DD (default 28 days ago)
- `until` (string): YYYY-MM-DD (default today)
- `view` (string, required): Which report to return

### `list_users` (~106 tokens)

List users

The app's users, most recently active first — each with an identity label, event count, last seen, and derived churn state (in_trial, converted, cancelled, expired, billing_issue, grace_period, paused, refunded, none). Capped so a large app does not flood the context; `total` reports how many matched before the cap.

Input parameters:

- `churn_state` (string): Only users in this billing state
- `limit` (integer): Max users (default 50)

### `get_user` (~77 tokens)

Get one user's full history

One user's identity (every stitched device / account / RevenueCat id), event breakdown, churn state and recent activity. Accepts the Fictura master user id, or any identifier the app knows them by — a device id, account id or RevenueCat id.

Input parameters:

- `user_id` (string, required): Master user id, or any known identifier

### `check_entitlement` (~124 tokens)

Check whether a user is subscribed

The authoritative paid/not-paid verdict for one user, unified across Stripe, RevenueCat, App Store and Play — the same answer GET /api/v1/entitlements/{user_id} returns to a server. Note: `environment` is SANDBOX when the verdict rests on test purchases, so always check it before granting production access; a cancellation only flips will_renew (access runs to expires_at); and an unknown user is a valid 'none' answer, not an error.

Input parameters:

- `user_id` (string, required): Device id, account id or RevenueCat id

### `get_tracking_plan` (~68 tokens)

Get the event tracking plan

Every event this app has ever sent, with volume, last-seen, and whether capture is switched off. Use it before adding instrumentation so you reuse the existing event name instead of introducing a near-duplicate — the name chosen here is the same string an experiment later names as its primary metric.

### `list_surfaces` (~95 tokens)

List paywalls, onboarding flows and placements

Every paywall and onboarding flow, what is actually being served at each placement (running experiment > live > none), and the valid placement names. IMPORTANT: read `placements` before writing a placement string into code. The list is configured ∪ observed, so a name that appears only under `observed` is usually a typo in the app — and a placement that does not exist renders nothing at all, with no error.

### `get_surface` (~86 tokens)

Get one paywall or onboarding flow's config

The full configuration of one paywall or onboarding flow, plus its version history. Note that configs never contain price strings — prices resolve at render time from the PurchasesAdapter's packages, so never copy a price literal out of (or into) a config.

Input parameters:

- `id` (string, required): The surface id, from list_surfaces
- `kind` (string, required): Which kind of surface

### `list_templates` (~63 tokens)

List built-in paywall and onboarding templates

The one-click starter templates available for paywalls or onboarding flows, with the template key and what each looks like. Use this when asked to add a paywall so you pick a real template key rather than inventing one.

Input parameters:

- `kind` (string, required): Which template catalog

### `list_experiments` (~38 tokens)

List experiments

Every experiment with status and, for running or finished ones, full Bayesian results — exposures, conversions, and the probability each variant is best.

### `get_experiment` (~34 tokens)

Get one experiment

One experiment with its variants and full Bayesian results.

Input parameters:

- `id` (string, required): Experiment id, from list_experiments

### `get_acquisition_report` (~151 tokens)

Get paid acquisition performance

\`roas` gives per-campaign spend, attributed installs/trials/paying users, revenue, CPI, CAC and ROAS, plus blended totals and explicitly-unattributed revenue — always keep attributed and blended figures apart when reporting these. `spend` gives raw daily ad-spend rows. `links` lists this app's tracking links.

Input parameters:

- `days` (integer): Lookback, for view=spend
- `provider` (string): Filter, for view=spend
- `since` (string): YYYY-MM-DD, for view=roas
- `until` (string): YYYY-MM-DD, for view=roas
- `view` (string, required): Which acquisition view

### `get_store_analytics` (~134 tokens)

Get App Store and Google Play analytics (Appfigures)

Store-reported numbers synced from Appfigures: downloads, re-downloads, updates, uninstalls, store revenue after the store's cut (subscriptions, in-app purchases, ads), top countries, the ratings snapshot, recent reviews with text, and category chart positions. Money is in micros of `currency`. Store revenue is a separate figure from RevenueCat revenue; never add the two. Returns connected: false when Appfigures is not set up.

Input parameters:

- `days` (integer): Lookback in days, default 28
- `reviews` (integer): How many recent reviews to include, default 20

### `list_campaigns` (~70 tokens)

List live ad campaigns

Campaigns read live from a connected ad platform: status, daily budget and ad sets. Returns a not_connected result rather than failing when the provider is not set up. This calls the provider's API, so prefer get_acquisition_report for historical numbers.

Input parameters:

- `provider` (string, required): Which ad platform

### `list_creators` (~38 tokens)

List creators and their performance

Creator records with a 28-day funnel per creator (clicks, installs, trials, paying users) and the tracking links tagged to each.

### `get_link_infrastructure` (~156 tokens)

Get deep link and tracking domain configuration

How links reach the app. `app_links` is the most important for integration work: it returns the iOS team id, bundle id, Android package and SHA-256 fingerprints that Fictura serves in the Universal Links / App Links association files, plus ios_ready and android_ready. Get these wrong and BOTH files fail SILENTLY — they parse, associate nothing, report no error, and links simply keep opening the browser instead of the app, so verify the ready flags rather than assuming. `domains` lists branded link domains and their DNS verification state, `web_config` the web-to-app smart banner, `esp` the email provider link setup.

Input parameters:

- `view` (string, required): Which part of the link setup

### `get_push_config` (~55 tokens)

Get push notification configuration

Whether push is set up and who could receive it: registered-device counts per billing cohort (all / paid / trial / free) and whether OneSignal is configured. Returns counts and configuration only — never device tokens or individual recipients.

### `list_store_products` (~104 tokens)

List App Store subscription products

This app's auto-renewable subscriptions in App Store Connect: product id, billing period and Apple review state. Use it to check that a paywall references a product that actually exists. Pass subscription_id to also fetch Apple's price ladder for that one product (Apple scopes price points per subscription, so there is no global list).

Input parameters:

- `subscription_id` (string): Also return price points for this subscription
- `territory` (string): Territory for price points (default USA)

### `list_error_issues` (~96 tokens)

List error issues

The error feed: grouped issues with level, status, event and user counts, a 14-day sparkline, plus the app's uptime summary. Defaults to unresolved issues only. `synthetic: true` marks console lines the SDK captured, not crashes.

Input parameters:

- `include_legacy` (boolean): Also list issues grouped before grouping v2 (default false)
- `status` (string): Which issues to include (default unresolved)

### `get_error_issue` (~135 tokens)

Get one error issue with stack traces

One issue in full: the group, its 50 most recent occurrences with stack traces, release and environment, and 30 days of daily counts. This is the tool to reach for when asked to fix a production error. When the app uploaded source maps, each occurrence also has `stack_resolved` and `frames` (original file, line, column and function; `in_app` marks the app's own code) — read those instead of the minified `stack`. An occurrence with a trace_id can be opened with get_trace.

Input parameters:

- `issue_id` (string, required): Issue id, from list_error_issues

### `search_error_issues` (~87 tokens)

Search error issues

Find issues by text in the title or culprit, platform, or release (first or last seen in). Returns the same rows as list_error_issues, filtered.

Input parameters:

- `limit` (integer)
- `platform` (string)
- `query` (string): Text to look for in the title or culprit
- `release` (string)
- `status` (string)

### `get_error_issue_brief` (~72 tokens)

Get an issue brief and a fix prompt

One issue condensed for fixing it: latest stack (resolved when source maps exist), in-app frames, breadcrumbs before it, facets (release, OS, device, screen), cause chain, and a ready-to-use fix prompt.

Input parameters:

- `issue_id` (string, required): Issue id, from list_error_issues

### `update_error_issue` (~89 tokens)

Change an error issue

Resolve, ignore or reopen an issue, assign it, set its priority, or add a note. Only works when the app allows MCP writes (Issues settings → Let MCP keys change issues).

Input parameters:

- `assignee`
- `issue_id` (string, required)
- `note` (string)
- `priority`
- `resolved_in_release` (string)
- `status` (string)

### `get_trace` (~89 tokens)

Get one distributed trace

Every span of one trace (app → backend → dependencies) as a tree: names, services, start offsets, durations, HTTP status and errors, plus the error events linked to the trace. Take the trace_id from an occurrence in get_error_issue. Use it to see where the time went or what failed first.

Input parameters:

- `trace_id` (string, required): 32-character hex W3C trace id

### `get_paywall_doc` (~105 tokens)

Get a Studio paywall's document

The JSON document a Studio (visual editor) paywall is made of, with its status and version, plus the reference to the document model. Read this before save_paywall_doc, and edit the document you got rather than writing one from scratch — keep node ids, change only what was asked. Prices are never typed: use {{ products.<slot>.price }} and the other product variables.

Input parameters:

- `id` (string, required): The paywall id, from list_surfaces

### `validate_paywall_doc` (~50 tokens)

Check a paywall document without saving it

Runs a document through the same parser and renderer a save uses and reports what is wrong, if anything. Changes nothing.

Input parameters:

- `doc` (object, required): A paywall document (version: 1)

### `save_paywall_doc` (~118 tokens)

Save a DRAFT paywall's document

Replaces a draft paywall's document with the one given, as a new version (History in the dashboard shows it as `mcp: <note>` and can roll it back). Refused for a live paywall — copy it in the dashboard first. Needs an MCP key that can edit. Products, translations and other settings are kept.

Input parameters:

- `doc` (object, required): The complete edited document
- `id` (string, required): The draft paywall's id
- `note` (string): What changed, for the version history

### `create_paywall_draft` (~108 tokens)

Create a new DRAFT Studio paywall

Creates a draft paywall from a Studio template (template_key, from list_templates — the webview ones) or from a document you wrote. It is never made live: going live is done in the dashboard. Needs an MCP key that can edit.

Input parameters:

- `doc` (object): A complete document, instead of a template
- `name` (string, required): The paywall's name in the dashboard
- `template_key` (string): A webview template key to start from

### `pair_editor` (~83 tokens)

Pair with an open Studio editor

Connects to the paywall editor a person has open, using the 6-character code shown under “Pair an agent” in the Studio. Returns a pairing_id for the editor_* tools. The code works once and for 10 minutes; a pairing lasts 24 hours or until either side stops it.

Input parameters:

- `code` (string, required): The code shown in the editor

### `editor_get_doc` (~82 tokens)

Read the document open in the paired editor

The document exactly as it is on the person's screen (unsaved changes included), which paywall it is, the screen they are on and the node they have selected, plus the document model reference. Read this before editor_set_doc and edit what you got — keep node ids, change only what was asked.

Input parameters:

- `pairing_id` (string, required): From pair_editor

### `editor_set_doc` (~106 tokens)

Put a document on the paired editor's canvas

Replaces the document in the person's open editor with the one given. It is NOT saved: the person sees the change, can undo it, and saves it themselves. The document is validated first and refused with the problems if it does not parse. Needs an MCP key that can edit.

Input parameters:

- `doc` (object, required): The complete edited document
- `note` (string): What changed, shown to the person in the editor
- `pairing_id` (string, required): From pair_editor

### `unpair_editor` (~32 tokens)

End the pairing with the editor

Stops this pairing. The editor shows that the agent left.

Input parameters:

- `pairing_id` (string, required): From pair_editor

### `get_onboarding_doc` (~86 tokens)

Get an onboarding flow's document

The JSON document a builder-made onboarding flow is made of, with its status and version, plus the reference to the document model. Read this before save_onboarding_doc, and edit the document you got rather than writing one from scratch — keep step keys and node ids, change only what was asked.

Input parameters:

- `id` (string, required): The onboarding flow id, from list_surfaces

### `validate_onboarding_doc` (~53 tokens)

Check an onboarding document without saving it

Runs a document through the same parser, step-key check and renderer a save uses and reports what is wrong, if anything. Changes nothing.

Input parameters:

- `doc` (object, required): An onboarding document (version: 1)

### `save_onboarding_doc` (~110 tokens)

Save a DRAFT onboarding flow's document

Replaces a draft flow's document with the one given, as a new version (the dashboard's history shows it as `mcp: <note>` and can roll it back). Refused for a live flow. Needs an MCP key that can edit. Translations, overrides and the exit setting are kept.

Input parameters:

- `doc` (object, required): The complete edited document
- `id` (string, required): The draft flow's id
- `note` (string): What changed, for the version history

### `create_onboarding_draft` (~77 tokens)

Create a new DRAFT onboarding flow

Creates a draft onboarding flow from a document you wrote (see get_onboarding_doc's reference). It is never made live: going live is done in the dashboard. Needs an MCP key that can edit.

Input parameters:

- `doc` (object, required): A complete onboarding document
- `name` (string, required): The flow's name in the dashboard

### `start_appsflyer_import` (~199 tokens)

Start the AppsFlyer import

Import everything AppsFlyer holds for this app: installs and the channel, campaign, adset and ad behind each one, in-app events and purchases, uninstalls, reinstalls, ad revenue and retargeting traffic. All twelve raw-data reports are walked; ones the AppsFlyer plan lacks are skipped, not failed. Runs in the background and keeps going after this call. mode 'auto' (default) only pulls the days since the last finished import when there is one, and walks the full history otherwise. 'full' re-walks everything. resume=true continues a failed or cancelled run from where it stopped. Safe to call while a run is going: it reports that run instead of starting another. Anything already imported is counted once. Check progress with get_appsflyer_import_status.

Input parameters:

- `mode` (string): Default auto
- `resume` (boolean): Continue the last failed or cancelled run

### `get_appsflyer_import_status` (~77 tokens)

Get AppsFlyer import status

Whether AppsFlyer is connected, the latest import run (status, progress, rows imported, duplicates skipped, people created, date range covered, error if it stopped), and whether an import has ever finished. Call before start_appsflyer_import so a finished import is not offered again as though nothing had happened.

### `get_appsflyer_attribution_summary` (~133 tokens)

Summarize imported AppsFlyer attribution

What the AppsFlyer import brought in about where people came from: people with an imported attribution, split by media source (organic included) and acquisition vs retargeting, plus the top campaigns. Filters on the install date. Imported verdicts never overwrite an attribution Fictura's own SDK resolved. For revenue and ROAS by source, use get_attribution_report with view=kpis.

Input parameters:

- `since` (string): Install date from, YYYY-MM-DD
- `top_campaigns` (integer): Default 20
- `until` (string): Install date to, YYYY-MM-DD

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-fictura-mcp/mcp#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 79

## Common questions

### What is the Fictura MCP server?

Fictura is an MCP server listed in the public MCP registry as co.fictura/mcp. Paywalls, onboarding, subscription analytics, A/B tests, attribution and errors for mobile apps. This page covers its hosted endpoint (https://mcp.fictura.co/mcp).

### Is the Fictura MCP server safe to use?

Fictura scores 82 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 Fictura MCP server expose?

Fictura exposes 44 tools: search_docs, list_docs, read_doc, get_app_setup, get_setup_status, and 39 more. Their descriptions and schemas cost roughly 4,098 tokens of context every time the server is loaded.

### Does the Fictura MCP server require authentication?

Its publisher declares no required credentials for Fictura. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Fictura MCP server still maintained?

Fictura is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.fictura.co/mcp
- Repository: https://github.com/Apex-Byte-Technologies/fictura-mcp
- Website: https://docs.fictura.co/connections/outgoing/mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/co-fictura-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-fictura-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/co-fictura-mcp/mcp