com.verirouteintel/lookup
REMOTE · VERIROUTEINTEL.COM · 2 COMPONENTS
Is this number safe to call or text right now? Live carrier, CNAM, spam and SMS checks for agents.
Available components
Last scanned (13 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Communication
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 Usability45
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1228 tokens (~87/item across 14 items; 10 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 74% of tool parameters carry a description.Partial
- 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 10 Oct 26 −6
- Stability: 0.97 → pass security
- Schema quality: 537 → 1228 ▼ functional
- Tool coverage: 100% → 74% ▼ functional
- Schema quality: unverified → 0 ▲ functional
- Schema quality: excellent → good functional
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 8 Sept 26 0
- 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
- 6 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
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 5 Nov 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=YE2,O=Let's Encrypt,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 671d5ad90143f770a8aedd1a4747608ee0b |
| SANs: messageproviderlookup.com, stopsendingspam.com, verirouteintel.com, www.messageproviderlookup.com, www.stopsendingspam.com, www.verirouteintel.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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. | DS published | 19718 | 13 | Verified |
| verirouteintel.com. | No DS | 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_account_info Account and connection budget ~21
Free: available balance, connection limits and allowed products.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
vri_bulk_lookup Bulk Lookup ~178
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. Live customer keys spend balance. Repeating a call can charge again; reuse a stable request_id with identical arguments for a safe retry. Use max_cost to cap the quote. Use a test key for integration tests.
| Name | Type | Req | Description |
|---|---|---|---|
| max_cost | number | – | Maximum quoted cost in USD; rejected before lookup if exceeded. |
| phone_numbers | array | yes | US/Canada numbers, any common format (max 100) |
| products | array | – | Data sets per number. Default ['lrn']. |
| request_id | string | – | Stable unique ID for this operation. Reuse with identical arguments to retrieve its receipt without another charge. |
| 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_submit_job or the REST Jobs API |
| 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_job_results Read job results ~53
Free, owner-scoped stored results. Follow next_cursor until null; never re-submit a completed job.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| job_id | string | yes | – |
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
vri_number_lookup Number Lookup ~225
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. Live customer keys spend balance. Repeating a call can charge again; reuse a stable request_id with identical arguments for a safe retry. Use max_cost to cap the quote. Use a test key for integration tests.
| Name | Type | Req | Description |
|---|---|---|---|
| include_sms_assessment | boolean | – | Include SMS assessment from this same lookup. Adds LRN/spam if absent; no second lookup. |
| max_cost | number | – | Maximum quoted cost in USD; rejected before lookup if exceeded. |
| phone_number | string | yes | US/Canada number, any common format |
| products | array | – | Data sets to include. Default ['lrn'] (carrier/line-type/routing). |
| request_id | string | – | Stable unique ID for this operation. Reuse with identical arguments to retrieve its receipt without another charge. |
| Name | Type | Req | Description |
|---|---|---|---|
| billed | boolean | – | Whether this lookup was charged |
| data | object | – | – |
| partial_results | boolean | – | – |
| phone_number | string | – | Normalized number |
| products_available | array | – | – |
| products_unavailable | array | – | – |
| 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 | – | – |
| total_charged | number | – | – |
No examples provided.
vri_operation_status Check request receipt ~41
Free: check an operation after an interrupted call; pending work must not be resubmitted with a new ID.
| Name | Type | Req | Description |
|---|---|---|---|
| operation_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
vri_quote Estimate lookup cost ~49
Free estimate using account pricing and deduplicated valid numbers; no lookup.
| Name | Type | Req | Description |
|---|---|---|---|
| include_sms_assessment | boolean | – | – |
| phone_numbers | array | yes | – |
| products | array | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
vri_sms_deliverability SMS Deliverability Check ~231
Line-type-based SMS capability and reputation signals for a North American number. Not an actual delivery test or guarantee. Unknown reputation never clears a number to message. 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). Performs its own LRN and spam lookup; avoid calling after number_lookup for the same data. Live customer keys spend balance. Repeating a call can charge again; reuse a stable request_id with identical arguments for a safe retry. Use max_cost to cap the quote. Use a test key for integration tests.
| Name | Type | Req | Description |
|---|---|---|---|
| max_cost | number | – | Maximum quoted cost in USD; rejected before lookup if exceeded. |
| phone_number | string | yes | US/Canada number, any common format |
| request_id | string | – | Stable unique ID for this operation. Reuse with identical arguments to retrieve its receipt without another charge. |
| 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|null | – | Inferred from line type; null when unknown. Not a delivery guarantee. |
| spam_flagged | boolean|null | – | – |
| voip | boolean | – | – |
No examples provided.
vri_spam_check Spam Check ~174
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). Live customer keys spend balance. Repeating a call can charge again; reuse a stable request_id with identical arguments for a safe retry. Use max_cost to cap the quote. Use a test key for integration tests.
| Name | Type | Req | Description |
|---|---|---|---|
| max_cost | number | – | Maximum quoted cost in USD; rejected before lookup if exceeded. |
| phone_number | string | yes | US/Canada number, any common format |
| request_id | string | – | Stable unique ID for this operation. Reuse with identical arguments to retrieve its receipt without another charge. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| partial_results | boolean | – | – |
| phone_number | string | – | – |
| products_available | array | – | – |
| products_unavailable | array | – | – |
| 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 | – | – |
| total_charged | number | – | – |
No examples provided.
vri_submit_job Submit Async Job ~185
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). Live customer keys spend balance. Repeating a call can charge again; reuse a stable request_id with identical arguments for a safe retry. Use max_cost to cap the quote. Use a test key for integration tests.
| Name | Type | Req | Description |
|---|---|---|---|
| max_cost | number | – | Maximum quoted cost in USD; rejected before lookup if exceeded. |
| phone_numbers | array | yes | US/Canada numbers to process asynchronously (max 10000) |
| products | array | – | Default ['lrn']. |
| request_id | string | – | Stable unique ID for this operation. Reuse with identical arguments to retrieve its receipt without another charge. |
| 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.
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'
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 10 tools: vri_number_lookup, vri_spam_check, vri_bulk_status, vri_bulk_lookup, vri_sms_deliverability, and 5 more. Their descriptions and schemas cost roughly 1,202 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the com.verirouteintel/lookup MCP server?
VerifyMCP ran 13 checks on com.verirouteintel/lookup, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.