# com.verirouteintel/lookup (remote · verirouteintel.com)

Is this number safe to call or text right now? Live carrier, CNAM, spam and SMS checks for agents.

- Trust score: 86/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `verirouteintel.com`: 86/100 (this document), [markdown](https://verifymcp.io/servers/com-verirouteintel-lookup/api-mcp.md), [page](https://verifymcp.io/servers/com-verirouteintel-lookup/api-mcp)
- npm · `veriroute-intel-mcp`: 78/100, [markdown](https://verifymcp.io/servers/com-verirouteintel-lookup/veriroute-intel-mcp.md), [page](https://verifymcp.io/servers/com-verirouteintel-lookup/veriroute-intel-mcp)

## Channel facts

- Endpoint: `https://verirouteintel.com/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.2.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 537 tokens (~89/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the com.verirouteintel/lookup MCP server?

com.verirouteintel/lookup is a hosted endpoint at https://verirouteintel.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-verirouteintel-lookup 'https://verirouteintel.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-verirouteintel-lookup": {
      "url": "https://verirouteintel.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-verirouteintel-lookup": {
      "type": "http",
      "url": "https://verirouteintel.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-verirouteintel-lookup]
url = "https://verirouteintel.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-verirouteintel-lookup": {
      "type": "remote",
      "url": "https://verirouteintel.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-verirouteintel-lookup --url 'https://verirouteintel.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-verirouteintel-lookup:
    url: "https://verirouteintel.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-verirouteintel-lookup": {
      "Transport": "http",
      "Url": "https://verirouteintel.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-verirouteintel-lookup -t streamable-http -u 'https://verirouteintel.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-verirouteintel-lookup": {
      "type": "http",
      "url": "https://verirouteintel.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 80, +3)

- [security improvement] Authorization: fail → pass
- [security] First check of Authorization: partial

### 2026-09-07 (score 77, 0)

- [security] Tool “vri_spam_check” rewrote its description, which is the text the model reads

## MCP tools (6)

### `vri_number_lookup` (~107 tokens)

Number Lookup

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.

Input parameters:

- `phone_number` (string, required): US/Canada number, any common format
- `products` (array): Data sets to include. Default ['lrn'] (carrier/line-type/routing).

Output parameters:

- `billed` (boolean): Whether this lookup was charged
- `data` (object): Carrier, line type, LRN, and any requested cnam/spam/messaging fields
- `phone_number` (string): Normalized number
- `risk` (object): Explainable spam/risk verdict: WHY the number is flagged (or not), with an honest confidence band. A clean verdict means "nothing found against it", never "verified safe".
- `status` (string): success or error

### `vri_spam_check` (~85 tokens)

Spam Check

Spam/scam/robocall reputation for one North American phone number, with an explainable `risk` block: the verdict, a confidence band, and the individual reasons behind it (complaint volume and recency, complaint category, community reports, line type, recent porting).

Input parameters:

- `phone_number` (string, required): US/Canada number, any common format

Output parameters:

- `is_spam` (boolean): True if flagged spam/scam/robocall
- `phone_number` (string)
- `risk` (object): Explainable spam/risk verdict: WHY the number is flagged (or not), with an honest confidence band. A clean verdict means "nothing found against it", never "verified safe".
- `spam_type` (string|null): SCAM, ROBOCALL, or null when clean

### `vri_bulk_status` (~45 tokens)

Bulk Job Status

Status and progress of a VRI bulk lookup job by job id.

Input parameters:

- `job_id` (string, required): Job id returned by vri_bulk_lookup or vri_submit_job

Output parameters:

- `job_id` (string)
- `processed` (integer): Numbers completed so far
- `status` (string): Job state, e.g. RUNNING or COMPLETED

### `vri_bulk_lookup` (~89 tokens)

Bulk Lookup

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.

Input parameters:

- `phone_numbers` (array, required): US/Canada numbers, any common format (max 100)
- `products` (array): Data sets per number. Default ['lrn'].

Output parameters:

- `results` (array)
- `total_charged` (string): USD amount billed for this call

### `vri_sms_deliverability` (~115 tokens)

SMS Deliverability Check

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).

Input parameters:

- `phone_number` (string, required): US/Canada number, any common format

Output parameters:

- `line_type` (string|null)
- `ok_to_message_now` (boolean): sms_capable AND clean AND inside the calling window
- `reasons` (array): Plain-language reasons this number is or is not a good send. Empty means nothing is wrong. When reputation is against the number these also carry the evidence behind it (complaint counts and recency,…
- `recipient_local` (object|null): Approximate timezone, local_time, quiet_hours_ok
- `sms_capable` (boolean): Wireless line that can receive SMS
- `spam_flagged` (boolean)
- `voip` (boolean)

### `vri_submit_job` (~96 tokens)

Submit Async Job

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).

Input parameters:

- `phone_numbers` (array, required): US/Canada numbers to process asynchronously (max 10000)
- `products` (array): Default ['lrn'].

Output parameters:

- `job_id` (string): Use with vri_bulk_status
- `reserved` (string): USD balance reserved for the job
- `status` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-verirouteintel-lookup/api-mcp#diagnostics

## Score history

- 2026-09-21: 86
- 2026-09-20: 85
- 2026-09-19: 85
- 2026-09-18: 84
- 2026-09-17: 84
- 2026-09-16: 83
- 2026-09-15: 83
- 2026-09-14: 82
- 2026-09-13: 82
- 2026-09-12: 81
- 2026-09-11: 81
- 2026-09-10: 81
- 2026-09-09: 80
- 2026-09-08: 80
- 2026-09-07: 77
- 2026-09-06: 77
- 2026-09-05: 76
- 2026-09-04: 36
- 2026-09-03: 36
- 2026-09-02: 36
- 2026-09-01: 36

## Common questions

### What is the com.verirouteintel/lookup MCP server?

com.verirouteintel/lookup is an MCP server listed in the public MCP registry as com.verirouteintel/lookup. Is this number safe to call or text right now? Live carrier, CNAM, spam and SMS checks for agents. This page covers its hosted endpoint (https://verirouteintel.com/api/mcp).

### Is the com.verirouteintel/lookup MCP server safe to use?

com.verirouteintel/lookup scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the com.verirouteintel/lookup MCP server expose?

com.verirouteintel/lookup exposes 6 tools: vri_number_lookup, vri_spam_check, vri_bulk_status, vri_bulk_lookup, vri_sms_deliverability, vri_submit_job. Their descriptions and schemas cost roughly 537 tokens of context every time the server is loaded.

### Does the com.verirouteintel/lookup MCP server require authentication?

Yes. com.verirouteintel/lookup asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the com.verirouteintel/lookup MCP server still maintained?

com.verirouteintel/lookup is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://verirouteintel.com/api/mcp
- Authorisation metadata: https://verirouteintel.com/.well-known/oauth-protected-resource/api/mcp
- Repository: https://github.com/verirouteintel/veriroute-intel-mcp
- Website: https://verirouteintel.com/api-docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-verirouteintel-lookup/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-verirouteintel-lookup/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-verirouteintel-lookup/api-mcp