Remote MCP · Endpoint

Seneca Research Platform MCP server

No. Seneca Research Platform answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://mcp.seneca.professionalaiagents.com/mcp

The last check completed an MCP handshake.

Registry name
com.professionalaiagents/seneca
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
106 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
One prompt. ~100 independent AI models. One report: consensus, disagreements, and minority insights.
Listing
From the official MCP registry (active).
Recent checks of Seneca Research Platform
CheckedResultHandshake
34 minutes agoHandshake completed106 ms
9 days agoHandshake completed93 ms
10 days agoHandshake completed103 ms
11 days agoHandshake completed216 ms
12 days agoHandshake completed204 ms
14 days agoHandshake completed112 ms
14 days agoHandshake completed132 ms
15 days agoHandshake completed109 ms
17 days agoCredentials required—
19 days agoCredentials required—
21 days agoCredentials required—
24 days agoCredentials required—
26 days agoCredentials required—
28 days agoCredentials required—

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

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