Remote MCP · Endpoint

Censais MCP server

No. Censais answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.censais.com/mcp

The last check completed an MCP handshake.

Registry name
com.censais/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
290 ms
Tools exposed
2 tools
Uptime, last 30 days
73.3% from 15 checks
Described by its publisher as
Censais software and AI services: browse what we build and sketch your project idea.
Listing
From the official MCP registry (active).
Recent checks of Censais
CheckedResultHandshake
1 hour agoHandshake completed290 ms
16 hours agoHandshake completed162 ms
2 days agoHandshake completed288 ms
4 days agoHandshake completed148 ms
6 days agoFailed - the connection was refused or dropped—
9 days agoFailed - the connection was refused or dropped—
11 days agoFailed - the connection was refused or dropped—
13 days agoFailed - the connection was refused or dropped—
15 days agoHandshake completed133 ms
17 days agoHandshake completed171 ms
19 days agoHandshake completed163 ms
21 days agoHandshake completed309 ms
23 days agoHandshake completed155 ms
24 days agoHandshake completed164 ms
25 days agoHandshake completed176 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 11 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 Censais and makes no claim about it beyond what these checks measured.