Remote MCP · Endpoint

FactStamp MCP server

No. FactStamp answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://factstamp.agentrails.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
au.com.alpineai/factstamp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.09 s
Tools exposed
17 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Verify a company, figure or citation before you rely on it. Card or crypto; signed receipt.
Listing
From the official MCP registry (active).
Recent checks of FactStamp
CheckedResultHandshake
7 hours agoHandshake completed1.09 s
2 days agoHandshake completed1.08 s
4 days agoHandshake completed995 ms
6 days agoHandshake completed956 ms
8 days agoHandshake completed765 ms
10 days agoHandshake completed773 ms
12 days agoHandshake completed578 ms
13 days agoHandshake completed742 ms
14 days agoHandshake completed1.18 s
15 days agoHandshake completed560 ms
18 days agoHandshake completed707 ms
20 days agoHandshake completed757 ms
21 days agoHandshake completed682 ms
23 days agoHandshake completed697 ms

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

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 FactStamp and makes no claim about it beyond what these checks measured.