Remote MCP · Endpoint

Daisycon (MCP server) MCP server

Yes, as of 2 days ago: the response was not JSON-RPC.

DownLast checked 2 days ago

Server URL

https://mcp.daisycon.com/campaigns/mcp

The last check failed: the response was not JSON-RPC.

Registry name
com.daisycon.mcp/daisycon
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
2 tools
Uptime, last 30 days
84.6% from 13 checks
Described by its publisher as
Search Daisycon affiliate programs, manage campaigns and leads, and track earnings and statistics.
Listing
From the official MCP registry (active).
Recent checks of Daisycon (MCP server)
CheckedResultHandshake
2 days agoFailed - the response was not JSON-RPC—
5 days agoFailed - the response was not JSON-RPC—
7 days agoHandshake completed553 ms
9 days agoHandshake completed489 ms
11 days agoHandshake completed442 ms
13 days agoHandshake completed454 ms
15 days agoHandshake completed462 ms
17 days agoHandshake completed465 ms
19 days agoHandshake completed450 ms
20 days agoHandshake completed461 ms
21 days agoHandshake completed461 ms
22 days agoHandshake completed451 ms
25 days agoHandshake completed436 ms

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