Remote MCP · Endpoint

Regex/Email/URL Validator MCP server

No. Regex/Email/URL Validator answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://apished.com/mcp/v1/validate

The last check completed an MCP handshake.

Registry name
com.apished/regex-email-url-validator
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
364 ms
Tools exposed
4 tools
Uptime, last 30 days
66.7% from 18 checks
Described by its publisher as
Regex matching, email/URL format validation, and JSON Schema validation.
Listing
From the official MCP registry (active).
Recent checks of Regex/Email/URL Validator
CheckedResultHandshake
1 hour agoHandshake completed364 ms
1 day agoHandshake completed360 ms
2 days agoHandshake completed420 ms
3 days agoHandshake completed363 ms
4 days agoHandshake completed639 ms
5 days agoHandshake completed363 ms
6 days agoHandshake completed364 ms
9 days agoHandshake completed361 ms
12 days agoHandshake completed367 ms
14 days agoFailed - the server returned an HTTP error—
16 days agoHandshake completed377 ms
18 days agoHandshake completed363 ms
20 days agoHandshake completed364 ms
22 days agoFailed - the server returned an HTTP error—
24 days agoFailed - the server returned an HTTP error—
26 days agoFailed - the server returned an HTTP error—
27 days agoFailed - the server returned an HTTP error—
28 days agoFailed - the server returned an HTTP error—

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 22 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 Regex/Email/URL Validator and makes no claim about it beyond what these checks measured.