Remote MCP · Endpoint

Howseen MCP server

No. Howseen answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
ai.howseen/howseen-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
163 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
How ChatGPT, Gemini, Perplexity and Google AI name your brand, cite sources and rank rivals.
Listing
From the official MCP registry (active).
Recent checks of Howseen
CheckedResultHandshake
34 minutes agoHandshake completed163 ms
9 days agoHandshake completed179 ms
10 days agoHandshake completed292 ms
11 days agoHandshake completed176 ms
12 days agoHandshake completed188 ms
14 days agoHandshake completed186 ms
14 days agoHandshake completed336 ms
15 days agoHandshake completed164 ms
17 days agoHandshake completed473 ms
19 days agoHandshake completed178 ms
21 days agoHandshake completed265 ms
24 days agoHandshake completed168 ms
26 days agoHandshake completed588 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 Howseen and makes no claim about it beyond what these checks measured.