Remote MCP · Endpoint

Pipefire MCP server

No. Pipefire answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://pipefire.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.pipefire/pipefire
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
280 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Cold email for agencies: SPF, DKIM, DMARC, blacklist checks, plus campaigns and replies.
Listing
From the official MCP registry (active).
Recent checks of Pipefire
CheckedResultHandshake
35 minutes agoHandshake completed280 ms
9 days agoHandshake completed369 ms
10 days agoHandshake completed483 ms
11 days agoHandshake completed363 ms
12 days agoHandshake completed384 ms
14 days agoHandshake completed346 ms
14 days agoHandshake completed353 ms
15 days agoHandshake completed355 ms
17 days agoHandshake completed513 ms
19 days agoHandshake completed499 ms
21 days agoHandshake completed462 ms
24 days agoHandshake completed645 ms
26 days agoHandshake completed571 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.

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