Remote MCP · Endpoint

CERT-FR Security Advisories — buy per-query in-session (certfrwatch) MCP server

No. CERT-FR Security Advisories — buy per-query in-session (certfrwatch) answered an MCP handshake 21 minutes ago.

UpLast checked 21 minutes ago

Server URL

https://a2awire.com/mcp/data/certfrwatch-cert-fr-anssi-national-security-advisories-b65f45/http

The last check completed an MCP handshake.

Registry name
com.a2awire/data-cert-fr-advisory-national-cert-alert
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
144 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
CERT-FR (ANSSI) security advisories & alerts: French national CERT vulnerability feed, hourly
Website
https://a2awire.com/data/certfrwatch-cert-fr-anssi-national-security-advisories-b65f45
Repository
https://github.com/ee324/a2awire
Listing
From the official MCP registry (active).
Recent checks of CERT-FR Security Advisories — buy per-query in-session (certfrwatch)
CheckedResultHandshake
21 minutes agoHandshake completed144 ms
2 days agoHandshake completed44 ms
4 days agoHandshake completed48 ms
5 days agoHandshake completed57 ms
7 days agoHandshake completed86 ms
8 days agoHandshake completed47 ms
9 days agoHandshake completed2.08 s
12 days agoHandshake completed947 ms
14 days agoHandshake completed351 ms
15 days agoHandshake completed179 ms
17 days agoHandshake completed338 ms
18 days agoHandshake completed368 ms
19 days agoHandshake completed336 ms
20 days agoHandshake completed391 ms
20 days agoHandshake completed155 ms
22 days agoHandshake completed361 ms
23 days agoHandshake completed63 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with CERT-FR Security Advisories — buy per-query in-session (certfrwatch) and makes no claim about it beyond what these checks measured.