Veriroute Intel Lookup
Related Servers
Alternatives to Veriroute Intel Lookup
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceProvides North American (NANP) area code and phone number intelligence for AI agents, including area code lookup, phone validation, carrier info, city/state coverage, local time, and scam context.872 npmMIT

Numbers Onlineofficial
AlicenseNot gradedqualityDmaintenanceProvides phone intelligence for AI voice agents, enabling inbound caller identification, outbound risk assessment, line type detection, and do-not-contact checks via four read-only MCP tools.MIT- AlicenseAqualityCmaintenanceVirtual phone number platform for AI agents — rent numbers across 200+ countries, receive SMS, and manage the full activation lifecycle.6267 npm4MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to look up a person’s phone number by name and current employer, LinkedIn URL, or email, returning line type, confidence grade, and person/company context.300 npmMIT
- AlicenseAqualityBmaintenanceEnables querying telecom routing data (LRN, CNAM, DNO, LERG, toll-free routing) directly from AI assistants like Claude, ChatGPT.1478 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables validating and enriching phone numbers, returning validity, international/national formats, carrier, line type, and country/location data.280 npmMIT
TDQS
Scored across 6 tools
Most tools have clear, distinct purposes: single vs bulk, sync vs async, and specialist SMS/spam verdicts. However, vri_spam_check overlaps with the optional spam reputation included in vri_number_lookup and vri_sms_deliverability, so a couple of tools could be confused if an agent only cares about a specific signal.
All tools share the vri_ prefix and snake_case, which makes the family recognizable. But action placement is inconsistent: vri_submit_job is verb-first while vri_number_lookup, vri_bulk_lookup, and vri_spam_check are noun-first, and vri_sms_deliverability is not an action at all.
Six tools is a well-scoped size for a phone-intelligence API: one-off lookup, bulk sync, bulk async, async status, spam, and SMS deliverability each cover a distinct workflow without bloat.
The core lookup surface is covered: single, bulk sync, bulk async, status, spam, and SMS deliverability. The main gap is a small one—there is no explicit results-retrieval or job-management tool beyond status/progress, and account/balance handling is only referenced as a constraint.