Remote MCP · Endpoint

Python Code Reviewer MCP server

Yes, as of 1 hour ago: the connection was refused or dropped.

DownLast checked 1 hour ago

Server URL

https://43-134-36-21.duckdns.org/mcp/mcp

The last check failed: the connection was refused or dropped.

Registry name
org.duckdns.43-134-36-21/python-code-reviewer
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
2 tools
Uptime, last 30 days
47.4% from 19 checks
Described by its publisher as
Security + bug + perf + refactor audit for Python. Returns 0-10 score + MD report.
Listing
From the official MCP registry (active).
Recent checks of Python Code Reviewer
CheckedResultHandshake
1 hour agoFailed - the connection was refused or dropped—
1 day agoFailed - the connection was refused or dropped—
2 days agoFailed - the connection was refused or dropped—
3 days agoFailed - the connection was refused or dropped—
4 days agoFailed - the request timed out—
5 days agoFailed - the connection was refused or dropped—
6 days agoFailed - the connection was refused or dropped—
8 days agoHandshake completed651 ms
11 days agoHandshake completed826 ms
13 days agoHandshake completed657 ms
15 days agoHandshake completed690 ms
18 days agoHandshake completed693 ms
20 days agoHandshake completed717 ms
22 days agoHandshake completed693 ms
24 days agoHandshake completed686 ms
26 days agoHandshake completed711 ms
27 days agoFailed - the TLS certificate could not be verified—
28 days agoFailed - the TLS certificate could not be verified—
29 days agoFailed - the TLS certificate could not be verified—

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

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 Python Code Reviewer and makes no claim about it beyond what these checks measured.