Remote MCP · Endpoint

Marketing Mcp MCP server

No. Marketing Mcp answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://marketing-mcp.mcpize.run/mcp

The last check completed an MCP handshake.

Registry name
io.github.varvararatta/marketing_mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
613 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
MCP server for Marketing
Listing
From the official MCP registry (active).
Recent checks of Marketing Mcp
CheckedResultHandshake
5 hours agoHandshake completed613 ms
2 days agoHandshake completed645 ms
4 days agoHandshake completed583 ms
5 days agoHandshake completed484 ms
7 days agoHandshake completed685 ms
8 days agoHandshake completed532 ms
9 days agoHandshake completed620 ms
12 days agoHandshake completed1.18 s
13 days agoHandshake completed524 ms
15 days agoHandshake completed705 ms
16 days agoHandshake completed468 ms
17 days agoHandshake completed520 ms
18 days agoHandshake completed548 ms
19 days agoHandshake completed518 ms
20 days agoHandshake completed483 ms
21 days agoHandshake completed4.76 s
22 days agoHandshake completed522 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 Marketing Mcp and makes no claim about it beyond what these checks measured.