Regex/Email/URL Validator is a remote MCP server that gives an AI agent 4 tools, among them email_validate, jsonschema_validate, regex_match. It answers at https://apished.com/mcp/v1/validate over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 17 October 2026, succeeded.
Regex matching, email/URL format validation, and JSON Schema validation.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
email_validate | Checks value is a single, bare RFC 5322 email address — syntax only, not a deliverability check. user@localhost is valid (no TLD required). "Name <email>" display syntax is rejected. Inputs: value |
jsonschema_validate | Validates document against schema (JSON Schema draft-07 or 2020-12). Reports one specific violation per call, not an aggregated list. Inputs: schema, document |
regex_match | Tests input against pattern (Go's regexp package: RE2 syntax, not PCRE — no backreferences or lookaround; use inline flags like (?i) for case-insensitive matching). Returns the full match and captured groups. Inputs: pattern, input |
url_validate | Checks value is a well-formed absolute URL (has both a scheme and a host) — syntax only, not a reachability check. Inputs: value |
Every block below points at https://apished.com/mcp/v1/validate. Pick your client and copy.
claude mcp add --transport http regex-email-url-validator https://apished.com/mcp/v1/validate
{
"mcpServers": {
"regex-email-url-validator": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://apished.com/mcp/v1/validate"]
}
}
}{
"mcpServers": {
"regex-email-url-validator": {
"url": "https://apished.com/mcp/v1/validate"
}
}
}{
"servers": {
"regex-email-url-validator": {
"type": "http",
"url": "https://apished.com/mcp/v1/validate"
}
}
}{
"context_servers": {
"regex-email-url-validator": {
"url": "https://apished.com/mcp/v1/validate"
}
}
}{
"mcpServers": {
"regex-email-url-validator": {
"serverUrl": "https://apished.com/mcp/v1/validate"
}
}
}{
"mcpServers": {
"regex-email-url-validator": {
"url": "https://apished.com/mcp/v1/validate"
}
}
}name: Regex/Email/URL Validator
version: 0.0.1
schema: v1
mcpServers:
- name: Regex/Email/URL Validator
type: streamable-http
url: https://apished.com/mcp/v1/validate{
"mcpServers": {
"regex-email-url-validator": {
"httpUrl": "https://apished.com/mcp/v1/validate"
}
}
}{
"mcpServers": {
"regex-email-url-validator": {
"type": "http",
"url": "https://apished.com/mcp/v1/validate"
}
}
}{
"mcpServers": {
"regex-email-url-validator": {
"url": "https://apished.com/mcp/v1/validate"
}
}
}goose://extension?url=https%3A%2F%2Fapished.com%2Fmcp%2Fv1%2Fvalidate&type=streamable_http&id=regex-email-url-validator&name=Regex/Email/URL%20Validator
It answered our last check on 17 October 2026 in 242 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by apished.com and served from apished.com, the vendor's own domain: https://apished.com/mcp/v1/validate.
4, as returned by the server's own tools/list on 10 September 2026: email_validate, jsonschema_validate, regex_match, url_validate.
It answered our last check on 17 October 2026 in 242 ms. Over 10 checks since 4 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://apished.com/mcp/v1/validate. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.apished. Endpoint host: apished.com. ARD identifier: urn:air:com.apished:mcp:regex-email-url-validator.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.