Remote MCP · Endpoint

ai.fugentic/fugentic MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://fugentic.mcp.fugentic.ai/mcp

The last check failed: the server returned an HTTP error.

Registry name
ai.fugentic/fugentic
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
6 tools
Uptime, last 30 days
58.8% from 17 checks
Described by its publisher as
Fugentic helps any business to be found by customers using AI to find products and service.
Listing
From the official MCP registry (active).
Recent checks of ai.fugentic/fugentic
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
6 days agoFailed - the server returned an HTTP error—
7 days agoFailed - the server returned an HTTP error—
9 days agoFailed - the server returned an HTTP error—
10 days agoFailed - the server returned an HTTP error—
11 days agoHandshake completed499 ms
14 days agoHandshake completed68 ms
15 days agoHandshake completed77 ms
17 days agoHandshake completed647 ms
18 days agoHandshake completed70 ms
19 days agoHandshake completed62 ms
20 days agoHandshake completed536 ms
21 days agoHandshake completed102 ms
22 days agoHandshake completed519 ms
23 days agoHandshake completed148 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 10 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.

Listing data comes from the official MCP registry. Glide is not affiliated with ai.fugentic/fugentic and makes no claim about it beyond what these checks measured.