Remote MCP · Endpoint

Factline MCP server

No. Factline answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://factline.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.snefhew/factline
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
133 ms
Tools exposed
53 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
EU company, sanctions, PEP and VAT checks, x402 pay guard, Dutch data. 5 checks a day free, no key.
Website
https://factline.dev/
Listing
From the official MCP registry (active).
Recent checks of Factline
CheckedResultHandshake
1 hour agoHandshake completed133 ms
2 days agoHandshake completed215 ms
5 days agoHandshake completed1.00 s
7 days agoHandshake completed121 ms
9 days agoHandshake completed132 ms
11 days agoHandshake completed587 ms
13 days agoHandshake completed221 ms
15 days agoHandshake completed97 ms
17 days agoHandshake completed51 ms
19 days agoHandshake completed172 ms
20 days agoHandshake completed730 ms
21 days agoHandshake completed331 ms
23 days agoHandshake completed271 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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