com.verirouteintel/lookup
REMOTE · VERIROUTEINTEL.COM · 2 COMPONENTS · SCANNED SEP 21
Is this number safe to call or text right now? Live carrier, CNAM, spam and SMS checks for agents.
Available components
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. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 537 tokens (~89/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · verirouteintel.com
claude mcp add --transport http com-verirouteintel-lookup 'https://verirouteintel.com/api/mcp'
{
"mcpServers": {
"com-verirouteintel-lookup": {
"url": "https://verirouteintel.com/api/mcp"
}
}
} {
"servers": {
"com-verirouteintel-lookup": {
"type": "http",
"url": "https://verirouteintel.com/api/mcp"
}
}
} [mcp_servers.com-verirouteintel-lookup] url = "https://verirouteintel.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-verirouteintel-lookup": {
"type": "remote",
"url": "https://verirouteintel.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-verirouteintel-lookup --url 'https://verirouteintel.com/api/mcp' --transport streamable-http
mcp_servers:
com-verirouteintel-lookup:
url: "https://verirouteintel.com/api/mcp" {
"McpServers": {
"com-verirouteintel-lookup": {
"Transport": "http",
"Url": "https://verirouteintel.com/api/mcp"
}
}
} assistant mcp add com-verirouteintel-lookup -t streamable-http -u 'https://verirouteintel.com/api/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 +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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 10 Sept 26 +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.
- 8 Sept 26 +3
- Authorization: fail → pass ▲ security
- First check of Authorization: partial security
- 7 Sept 26 0
- Tool “vri_spam_check” rewrote its description, which is the text the model reads security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://verirouteintel.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=verirouteintel.com | CN=YE1,O=Let's Encrypt,C=US | 22 Aug 2026 | 20 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5b1b0d9879c48cfd098d72f5d7033662efc |
| SANs: messageproviderlookup.com, stopsendingspam.com, verirouteintel.com, www.messageproviderlookup.com, www.stopsendingspam.com, www.verirouteintel.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of verirouteintel.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| verirouteintel.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="VeriRoute Intel MCP", resource_metadata="https://verirouteintel.com/.well-known/oauth-protected-resource/api/mcp"
Bearer realm="VeriRoute Intel MCP", resource_metadata="https://verirouteintel.com/.well-known/oauth-protected-resource/api/mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; img-src 'self' data: blob: https:; font-src 'self' data: https://fonts.googleapis.com https://fonts.gstatic.com https://cdnjs.cloudflare.com; script-src 'self' 'unsafe-inline' https://challenges.cloudflare.com https://www.googletagmanager.com https://www.google-analytics.com https://cdn.jsdelivr.net https://pagead2.googlesyndication.com https://*.google https://*.doubleclick.net https://*.clarity.ms https://*.authorize.net https://authorize.net https://connect.facebook.net; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://cdn.jsdelivr.net https://cdnjs.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com https://www.google-analytics.com https://*.google-analytics.com https://cdn.jsdelivr.net https://*.google.com https://*.google https://pagead2.googlesyndication.com https://*.clarity.ms https://*.authorize.net https://authorize.net https://www.facebook.com https://connect.facebook.net; frame-src 'self' https://challenges.cloudflare.com https://googleads |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Protected resource metadata
| Document | https://verirouteintel.com/.well-known/oauth-protected-resource/api/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://verirouteintel.com/api/mcp |
| Authorisation server | https://verirouteintel.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://verirouteintel.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://verirouteintel.com/api/mcp | HTTPS enforced | 301 | https://verirouteintel.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
vri_bulk_lookup Bulk Lookup ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| phone_numbers | array | yes | US/Canada numbers, any common format (max 100) |
| products | array | – | Data sets per number. Default ['lrn']. |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | – | – |
| total_charged | string | – | USD amount billed for this call |
No examples provided.
vri_bulk_status Bulk Job Status ~45
Status and progress of a VRI bulk lookup job by job id.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | Job id returned by vri_bulk_lookup or vri_submit_job |
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | – | – |
| processed | integer | – | Numbers completed so far |
| status | string | – | Job state, e.g. RUNNING or COMPLETED |
No examples provided.
vri_number_lookup Number Lookup ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| phone_number | string | yes | US/Canada number, any common format |
| products | array | – | Data sets to include. Default ['lrn'] (carrier/line-type/routing). |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No examples provided.
vri_sms_deliverability SMS Deliverability Check ~115
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).
| Name | Type | Req | Description |
|---|---|---|---|
| phone_number | string | yes | US/Canada number, any common format |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No examples provided.
vri_spam_check Spam Check ~85
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).
| Name | Type | Req | Description |
|---|---|---|---|
| phone_number | string | yes | US/Canada number, any common format |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No examples provided.
vri_submit_job Submit Async Job ~96
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).
| Name | Type | Req | Description |
|---|---|---|---|
| phone_numbers | array | yes | US/Canada numbers to process asynchronously (max 10000) |
| products | array | – | Default ['lrn']. |
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | – | Use with vri_bulk_status |
| reserved | string | – | USD balance reserved for the job |
| status | string | – | – |
No examples provided.
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.