Remote MCP · Endpoint

Notipo MCP server

No. Notipo answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://app.notipo.com/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.kfuras/notipo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
3.38 s
Tools exposed
13 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Publish to self-hosted WordPress from AI agents: markdown, images, SEO, and Notion sync.
Listing
From the official MCP registry (active).
Recent checks of Notipo
CheckedResultHandshake
1 hour agoHandshake completed3.38 s
2 days agoHandshake completed296 ms
4 days agoHandshake completed176 ms
5 days agoHandshake completed159 ms
7 days agoHandshake completed187 ms
8 days agoHandshake completed312 ms
9 days agoHandshake completed142 ms
12 days agoHandshake completed195 ms
13 days agoHandshake completed175 ms
15 days agoHandshake completed152 ms
17 days agoHandshake completed188 ms
18 days agoHandshake completed161 ms
19 days agoHandshake completed177 ms
20 days agoHandshake completed182 ms
20 days agoHandshake completed150 ms
21 days agoHandshake completed152 ms
23 days agoHandshake completed173 ms

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

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