Security & Testing
verified.net
Validates email addresses, phone numbers, IP addresses, and contact/domain records with risk scoring and accept/review/reject recommendations.
ENDPOINT 1
https://api.verified.net/mcp
MCP server metadata
- Name
- Verified.net
Verified.net validates email addresses, phone numbers and IP addresses, and finds who is behind a phone number or email. Every tool uses the caller's prepaid credits (the result says credits_charged and credits_remaining). Invalid input is free, and repeating the same check within 7 days is free. Prefer the `recommendation.action` field (accept / review / reject) when deciding what to do with a value. For more than a few dozen values, use create_bulk_job instead of calling a lookup tool repeatedly. Reverse lookups return personal contact details from historical domain registration records: use them only for lawful purposes such as verifying a contact or preventing fraud; people who opted out are never returned.
Known tools 11
verify_emailCheck an email address: syntax, mail server, mailbox (when the server allows), disposable, role account, typo suggestion, risk score and an accept/review/reject recommendation.
Potential side effectscarrier_lookupUS/Canada numbers: the carrier serving the number today, whether it was ported, port date, current line type and VoIP, from a live number-portability lookup.
Inferred read-onlyip_lookupCheck an IPv4/IPv6 address: approximate location, network owner (ASN), Tor exit, datacenter/hosting, risk score and recommendation.
Inferred read-onlyverify_contactCheck whether a name and/or phone match the domain registration records that list this email.
Potential side effectsreverse_emailWho is behind an email address: names and phone numbers from domain registration records.
Potential side effectscreate_bulk_jobCheck up to 100,000 values in the background, charged per unique value like single lookups (reverse lookups only when found).
Inferred read-onlyget_bulk_resultsResults of a bulk job, one page at a time (has_next tells you to ask for the next page).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.verified-net]
url = "https://api.verified.net/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"verified-net": {
"type": "http",
"url": "https://api.verified.net/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: verified-net
Remote MCP URL: https://api.verified.net/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"verified-net": {
"url": "https://api.verified.net/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"verified-net": {
"type": "http",
"url": "https://api.verified.net/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "verified-net",
"transport": "streamable-http",
"url": "https://api.verified.net/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.