Remote MCP · Endpoint

Fictura MCP server

No. Fictura answered an MCP handshake 3 days ago.

UpLast checked 3 days ago

Server URL

https://mcp.fictura.co/mcp

The last check completed an MCP handshake.

Registry name
co.fictura/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
32 ms
Tools exposed
88 tools
Uptime, last 30 days
100% from 10 checks
Described by its publisher as
Paywalls, onboarding, subscription analytics, A/B tests, attribution and errors for mobile apps.
Listing
From the official MCP registry (active).
Recent checks of Fictura
CheckedResultHandshake
3 days agoHandshake completed32 ms
6 days agoHandshake completed32 ms
16 days agoHandshake completed38 ms
17 days agoHandshake completed110 ms
18 days agoHandshake completed25 ms
19 days agoHandshake completed25 ms
21 days agoHandshake completed43 ms
21 days agoHandshake completed27 ms
22 days agoHandshake completed26 ms
24 days agoHandshake completed26 ms

The last 10 checks. Full history is kept for 30 days; the all-time counter stands at 10 responding of 10.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Fictura and makes no claim about it beyond what these checks measured.