Remote MCP · Endpoint

Profullstack MCP server

No. Profullstack answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://profullstack.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.profullstack/profullstack
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
104 ms
Tools exposed
154 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
153 read-only tools from 15 Profullstack MCP servers: domains, SEO, public data, feeds, podcasts
Listing
From the official MCP registry (active).
Recent checks of Profullstack
CheckedResultHandshake
9 hours agoHandshake completed104 ms
4 days agoFailed - the connection was refused or dropped—
7 days agoHandshake completed90 ms

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

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