Regex matching, email/URL format validation, and JSON Schema validation.
Connect Remote server
claude mcp add --transport http regex-email-url-validator 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"
}
}
}
Settings > Connectors > Add custom connector
URL: https://apished.com/mcp/v1/validate
Tools 4 found in our last check
email_validateChecks 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.
jsonschema_validateValidates document against schema (JSON Schema draft-07 or 2020-12). Reports one specific violation per call, not an aggregated list.
regex_matchTests 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.
url_validateChecks value is a well-formed absolute URL (has both a scheme and a host) โ syntax only, not a reachability check.
Details
| Endpoint | https://apished.com/mcp/v1/validate (Streamable HTTP) |
| First published | 18 Aug 2026 |
| Last updated | 18 Aug 2026 |
| Registry name | com.apished/regex-email-url-validator |
More communication servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
