Remote MCP · Endpoint

MisarPost MCP Server MCP server

No. MisarPost MCP Server answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://api.misar.io/post/mcp

The last check completed an MCP handshake.

Registry name
io.github.Misar-AI/misarpost-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
641 ms
Tools exposed
85 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Plan, generate, schedule and repurpose posts across every channel, and track what performs.
Listing
From the official MCP registry (active).
Recent checks of MisarPost MCP Server
CheckedResultHandshake
34 minutes agoHandshake completed641 ms
8 days agoHandshake completed575 ms
9 days agoHandshake completed647 ms
11 days agoHandshake completed525 ms
12 days agoHandshake completed638 ms
12 days agoHandshake completed603 ms
14 days agoHandshake completed578 ms
14 days agoHandshake completed614 ms
16 days agoHandshake completed1.05 s
19 days agoHandshake completed628 ms
21 days agoHandshake completed610 ms
24 days agoHandshake completed592 ms
26 days agoHandshake completed601 ms
28 days agoFailed - the check failed for an unclassified reason—

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 13 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 MisarPost MCP Server and makes no claim about it beyond what these checks measured.