Remote MCP · Endpoint

BeliefState MCP server

No. BeliefState answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://beliefstate.ai/v1/research/mcp

The last check completed an MCP handshake.

Registry name
ai.beliefstate/investor-research
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
75 ms
Tools exposed
Not measured yet
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
26 account tools; 23 wallet tools (20 paid). Free company snapshots and cited research.
Listing
From the official MCP registry (active).
Recent checks of BeliefState
CheckedResultHandshake
35 minutes agoHandshake completed75 ms
3 days agoHandshake completed1.12 s
13 days agoHandshake completed72 ms
13 days agoHandshake completed152 ms
15 days agoHandshake completed590 ms
16 days agoHandshake completed644 ms
17 days agoHandshake completed301 ms
18 days agoHandshake completed1.40 s
18 days agoHandshake completed84 ms
20 days agoHandshake completed1.29 s
22 days agoHandshake completed687 ms
25 days agoHandshake completed1.05 s

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

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