Remote MCP · Endpoint

PeopleMCP MCP server

Yes, as of 1 hour ago: the TLS certificate could not be verified.

DownLast checked 1 hour ago

Server URL

https://people-mcp.194-87-35-210.sslip.io/mcp

The last check failed: the TLS certificate could not be verified.

Registry name
io.github.OlegNickeshin/people-mcp
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
11 tools
Uptime, last 30 days
57.9% from 19 checks
Described by its publisher as
Semantic search for people, projects and AI agents by task, skills and collaboration needs.
Website
https://github.com/OlegNickeshin/people-mcp#readme
Repository
https://github.com/OlegNickeshin/people-mcp
Listing
From the official MCP registry (active).
Recent checks of PeopleMCP
CheckedResultHandshake
1 hour agoFailed - the TLS certificate could not be verified—
10 hours agoFailed - the TLS certificate could not be verified—
1 day agoFailed - the TLS certificate could not be verified—
2 days agoFailed - the TLS certificate could not be verified—
4 days agoFailed - the TLS certificate could not be verified—
4 days agoFailed - the TLS certificate could not be verified—
5 days agoFailed - the TLS certificate could not be verified—
6 days agoFailed - the TLS certificate could not be verified—
8 days agoHandshake completed287 ms
11 days agoHandshake completed293 ms
13 days agoHandshake completed281 ms
16 days agoHandshake completed302 ms
18 days agoHandshake completed390 ms
20 days agoHandshake completed805 ms
22 days agoHandshake completed279 ms
24 days agoHandshake completed282 ms
26 days agoHandshake completed338 ms
27 days agoHandshake completed285 ms
29 days agoHandshake completed288 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with PeopleMCP and makes no claim about it beyond what these checks measured.