Remote MCP · Endpoint

Deep Values MCP server

No. Deep Values answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://app.deepvalues.ai/api/mcp

The last check completed an MCP handshake.

Registry name
ai.deepvalues/deepvalues
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
236 ms
Tools exposed
27 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Value investing for US stocks: SEC filings, 13F guru holdings, intrinsic value, AI briefings.
Listing
From the official MCP registry (active).
Recent checks of Deep Values
CheckedResultHandshake
2 hours agoHandshake completed236 ms
2 days agoHandshake completed234 ms
5 days agoHandshake completed237 ms
7 days agoHandshake completed277 ms
9 days agoHandshake completed239 ms
11 days agoHandshake completed295 ms
13 days agoHandshake completed240 ms
15 days agoHandshake completed251 ms
17 days agoHandshake completed223 ms
19 days agoHandshake completed271 ms
20 days agoHandshake completed226 ms
21 days agoHandshake completed232 ms
23 days agoHandshake completed251 ms

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

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