Veriroute Intel Lookup
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VRI_API_KEY | Yes | Your VeriRoute Intel API key. Used as the bearer token in the Authorization header when connecting to the hosted MCP server. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vri_number_lookupA | Live intelligence for ONE North American phone number: current carrier of record, line type, LRN routing data, porting activation date, and optionally caller-ID name (cnam), spam reputation, and messaging provider. Always a fresh read of live numbering infrastructure — never cached carrier data. |
| vri_spam_checkA | Spam/scam/robocall reputation for one North American phone number. |
| vri_bulk_statusA | Status and progress of a VRI bulk lookup job by job id. |
| vri_bulk_lookupA | Live lookup for up to 100 North American phone numbers in one call (carrier, line type, routing; optional cnam/spam/messaging). Each number is a fresh paid read — spend scope required. |
| vri_sms_deliverabilityA | ONE verdict for AI outreach: can this North American number receive SMS, and is now a reasonable time to send? Returns sms_capable (live line-type read), VoIP flag, spam reputation, the recipient's approximate local time with an 8am-9pm calling-window flag, and plain-language reasons. Deliverability and reputation signals only — not a legal compliance determination (no DNC/reassigned-number/litigator data). |
| vri_submit_jobA | Submit an ASYNC bulk lookup job for up to 10000 North American phone numbers. Balance is reserved up front and the job runs in the background; check progress with vri_bulk_status. Requires a customer API key (jobs bill the account that owns the key). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.