Remote MCP · Endpoint

ESG Hub MCP Server MCP server

No. ESG Hub MCP Server answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://esg-hub.ascent.partners/api/mcp

The last check completed an MCP handshake.

Registry name
com.ascent-partners/esg-hub
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
865 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
ESG knowledge base for AI agents: hybrid search, glossary, frameworks, industries, graph traversal.
Listing
From the official MCP registry (active).
Recent checks of ESG Hub MCP Server
CheckedResultHandshake
13 minutes agoHandshake completed865 ms
10 days agoHandshake completed906 ms
10 days agoHandshake completed841 ms
11 days agoHandshake completed816 ms
13 days agoHandshake completed895 ms
14 days agoHandshake completed887 ms
14 days agoHandshake completed1.02 s
15 days agoHandshake completed1.07 s
17 days agoHandshake completed1.02 s
19 days agoHandshake completed1.14 s
21 days agoHandshake completed1.12 s
24 days agoHandshake completed1.04 s
26 days agoHandshake completed641 ms
28 days agoHandshake completed88 ms

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