Remote MCP · Endpoint

io.github.discover-dmc/paygentic MCP server

Yes, as of 6 hours ago: the TLS certificate could not be verified.

DownLast checked 6 hours ago

Server URL

https://api.discoverdmc.cloud/mcp

The last check failed: the TLS certificate could not be verified.

Registry name
io.github.discover-dmc/paygentic
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
10 tools
Uptime, last 30 days
28.6% from 14 checks
Described by its publisher as
Pay-per-call APIs for AI agents: web scraping, DNS/email checks, classification, trading risk.
Listing
From the official MCP registry (active).
Recent checks of io.github.discover-dmc/paygentic
CheckedResultHandshake
6 hours agoFailed - the TLS certificate could not be verified—
9 days agoFailed - the TLS certificate could not be verified—
10 days agoFailed - the TLS certificate could not be verified—
11 days agoFailed - the TLS certificate could not be verified—
12 days agoFailed - the TLS certificate could not be verified—
14 days agoFailed - the TLS certificate could not be verified—
15 days agoFailed - the hostname does not resolve—
15 days agoFailed - the hostname does not resolve—
17 days agoFailed - the hostname does not resolve—
19 days agoFailed - the hostname does not resolve—
22 days agoHandshake completed440 ms
24 days agoHandshake completed455 ms
26 days agoHandshake completed104 ms
28 days agoHandshake completed540 ms

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

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 io.github.discover-dmc/paygentic and makes no claim about it beyond what these checks measured.