Remote MCP · Endpoint

FirmaDB — European Company Data MCP server

Yes, as of 1 hour ago: the request timed out.

DownLast checked 1 hour ago

Server URL

https://mcp.firmadb.com/mcp

The last check failed: the request timed out.

Registry name
com.firmadb/company-data
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
6 tools
Uptime, last 30 days
64.3% from 14 checks
Described by its publisher as
Find European company records with registry source and freshness information.
Listing
From the official MCP registry (active).
Recent checks of FirmaDB — European Company Data
CheckedResultHandshake
1 hour agoFailed - the request timed out—
2 days agoFailed - the request timed out—
5 days agoFailed - the request timed out—
7 days agoFailed - the request timed out—
9 days agoHandshake completed329 ms
11 days agoHandshake completed558 ms
13 days agoHandshake completed333 ms
15 days agoFailed - the check failed for an unclassified reason—
17 days agoHandshake completed324 ms
18 days agoHandshake completed332 ms
19 days agoHandshake completed326 ms
20 days agoHandshake completed327 ms
23 days agoHandshake completed354 ms
24 days agoHandshake completed363 ms

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

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 FirmaDB — European Company Data and makes no claim about it beyond what these checks measured.