Remote MCP · Endpoint

PostWire MCP server

No. PostWire answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://postwire.io/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.Perufitlife/postwire-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
106 ms
Tools exposed
21 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Writes a native post per network from one idea and publishes it: TikTok, Instagram, YouTube & more
Listing
From the official MCP registry (active).
Recent checks of PostWire
CheckedResultHandshake
1 hour agoHandshake completed106 ms
1 day agoHandshake completed105 ms
3 days agoHandshake completed113 ms
6 days agoHandshake completed79 ms
8 days agoHandshake completed160 ms
9 days agoHandshake completed71 ms
11 days agoHandshake completed158 ms
11 days agoHandshake completed57 ms
13 days agoHandshake completed74 ms
16 days agoHandshake completed71 ms
17 days agoHandshake completed61 ms
19 days agoHandshake completed83 ms
20 days agoHandshake completed54 ms
21 days agoHandshake completed78 ms
22 days agoHandshake completed96 ms

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

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