Remote MCP · Endpoint

Telesherpa Ontology Platform MCP server

No. Telesherpa Ontology Platform answered an MCP handshake 6 hours ago.

Up · key neededLast checked 6 hours ago

Server URL

https://mcp.telesherpa.com/mcp

The handshake completes, but listing its tools needs credentials.

Registry name
com.telesherpa/ontology-platform
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
289 ms
Tools exposed
Behind credentials
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Ontology platform for field service: AI agents observe, connect and act on business objects.
Listing
From the official MCP registry (active).
Recent checks of Telesherpa Ontology Platform
CheckedResultHandshake
6 hours agoHandshake completed289 ms
9 days agoCredentials required—
10 days agoCredentials required—
11 days agoCredentials required—
12 days agoCredentials required—
14 days agoCredentials required—
15 days agoCredentials required—
15 days agoCredentials required—
17 days agoCredentials required—
19 days agoCredentials required—
22 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 26 responding of 26.

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