Remote MCP · Endpoint

typesearch MCP server

No. typesearch answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.typesearch.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.typesearch/news
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
44 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
News search for AI agents: recent news on any topic from outlets worldwide, by country and language.
Listing
From the official MCP registry (active).
Recent checks of typesearch
CheckedResultHandshake
1 hour agoHandshake completed44 ms
2 days agoHandshake completed45 ms
4 days agoHandshake completed45 ms
6 days agoHandshake completed49 ms
7 days agoHandshake completed43 ms
9 days agoHandshake completed50 ms
10 days agoHandshake completed46 ms
11 days agoHandshake completed46 ms
14 days agoHandshake completed54 ms
15 days agoHandshake completed53 ms
17 days agoHandshake completed45 ms
19 days agoHandshake completed48 ms
20 days agoHandshake completed41 ms
21 days agoHandshake completed45 ms
22 days agoHandshake completed99 ms

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

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