Remote MCP · Endpoint

Softhills MCP server

No. Softhills answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://ai.softhills.net/mcp

The last check completed an MCP handshake.

Registry name
net.softhills/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
731 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Official MCP server for Softhills 3D/2D Visualization SDKs, API documentation, and code examples.
Listing
From the official MCP registry (active).
Recent checks of Softhills
CheckedResultHandshake
1 hour agoHandshake completed731 ms
18 hours agoHandshake completed766 ms
2 days agoHandshake completed730 ms
3 days agoHandshake completed759 ms
4 days agoHandshake completed745 ms
5 days agoHandshake completed1.13 s
6 days agoHandshake completed727 ms
7 days agoHandshake completed790 ms
10 days agoHandshake completed759 ms
13 days agoHandshake completed729 ms
15 days agoHandshake completed760 ms
17 days agoHandshake completed769 ms
19 days agoHandshake completed764 ms
21 days agoHandshake completed757 ms
23 days agoHandshake completed800 ms
25 days agoHandshake completed779 ms

The last 16 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 Softhills and makes no claim about it beyond what these checks measured.