Remote MCP · Endpoint

com.trusted-blogs/blogsuche MCP server

No. com.trusted-blogs/blogsuche answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.trusted-blogs.com/mcp

The last check completed an MCP handshake.

Registry name
com.trusted-blogs/blogsuche
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
311 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Find vetted blogs for sponsored posts and link building, with topics and SEO metrics. Read-only.
Listing
From the official MCP registry (active).
Recent checks of com.trusted-blogs/blogsuche
CheckedResultHandshake
1 hour agoHandshake completed311 ms
3 days agoHandshake completed563 ms
12 days agoHandshake completed324 ms
12 days agoHandshake completed321 ms
14 days agoHandshake completed398 ms
15 days agoHandshake completed325 ms
16 days agoHandshake completed305 ms
17 days agoHandshake completed312 ms
18 days agoHandshake completed320 ms
19 days agoHandshake completed318 ms
22 days agoHandshake completed324 ms
25 days agoHandshake completed312 ms
27 days agoHandshake completed350 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 com.trusted-blogs/blogsuche and makes no claim about it beyond what these checks measured.