NexIP
REMOTE · NEXIP.RU
Network, domain and website diagnostics for AI clients via MCP.
Available components
Last scanned (49 minutes ago)
Scores higher than 93% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Monitoring and Observability
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 Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 823 tokens (~58/item across 14 items; 13 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 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 (15% 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
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.
- 5 Nov 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.
- 4 Nov 26 +1
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.37 ▲ functional
- 3 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.30 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 2 Nov 26 +7
- Authorization: partial → pass ▲ security
- First check of Authorization: partial security
- Tool “check_dns” rewrote its description, which is the text the model reads security
- Tool “check_headers” rewrote its description, which is the text the model reads security
- Tool “check_ip” rewrote its description, which is the text the model reads security
- Tool “check_meta” rewrote its description, which is the text the model reads security
- Tool “check_redirects” rewrote its description, which is the text the model reads security
- Tool “check_robots” rewrote its description, which is the text the model reads security
- Tool “check_site” rewrote its description, which is the text the model reads security
- Tool “check_sitemap” rewrote its description, which is the text the model reads security
- Tool “check_ssl” rewrote its description, which is the text the model reads security
- Tool “check_whois” rewrote its description, which is the text the model reads security
- Tool “get_account_plan” rewrote its description, which is the text the model reads security
- Tool “get_api_limits” rewrote its description, which is the text the model reads security
- Tool “render_website_report” rewrote its description, which is the text the model reads security
- Schema quality: 49 → 58 ▼ functional
- Tool coverage: 65% → 100% ▲ functional
- Tool “get_account_plan” now declares an output schema ▲ functional
- Tool “get_api_limits” now declares an output schema ▲ functional
- First check of Tool coverage: 15 functional
- “render_website_report” reworded the description of “checks” cosmetic
- “render_website_report” reworded the description of “dns_status” cosmetic
- “render_website_report” reworded the description of “http_status” cosmetic
- “render_website_report” reworded the description of “response_ms” cosmetic
- “render_website_report” reworded the description of “summary” cosmetic
- “render_website_report” reworded the description of “tls_status” cosmetic
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 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.
- 28 Oct 26 0
- Server version: 2.9.2 → 2.9.3 functional
- 27 Oct 26 0
- Server version: 2.9.1 → 2.9.2 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://nexip.ru/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nexip.ru | CN=YR1,O=Let's Encrypt,C=US | 23 Sept 2026 | 22 Dec 2026 | RSA 2048 | SHA256-RSA | 55afb19e7c8f2cc7d4245779a2bd54ba56b |
| SANs: nexip.ru, www.nexip.ru | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
| CN=ISRG Root X1,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 4 Jun 2015 | 4 Jun 2035 | RSA 4096 | SHA256-RSA | 8210cfb0d240e3594463e0bb63828b00 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of nexip.ru. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ru. | present | 26734 | 8 | Verified |
| nexip.ru. | 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 resource_metadata="https://nexip.ru/.well-known/oauth-protected-resource", scope="mcp.use tools.run"
Bearer resource_metadata="https://nexip.ru/.well-known/oauth-protected-resource", scope="mcp.use tools.run"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | default-src 'self'; img-src 'self' data: https:; style-src 'self' 'unsafe-inline' https:; script-src 'self' 'unsafe-inline' https:; connect-src 'self' https:; frame-src 'self' https:; font-src 'self' data: https:; form-action 'self'; base-uri 'self'; frame-ancestors 'self' |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=() |
Protected resource metadata
| Document | https://nexip.ru/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://nexip.ru/mcp |
| Authorisation server | https://nexip.ru |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nexip.ru/mcp | Verified | 200 | |
| http (plaintext) | http://nexip.ru/mcp | HTTPS enforced | 301 | https://nexip.ru/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 →
check_dns ~49
Read DNS records for a domain using NexIP. Runs on NexIP servers, uses account quota and stores history. Example: target="example.com".
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Domain name to inspect. |
No output schema declared.
No examples provided.
check_headers ~51
Inspect HTTP response headers and security-related headers. Runs on NexIP servers, uses account quota and stores history. Example: target="https://example.com".
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Public website URL to inspect. |
No output schema declared.
No examples provided.
check_ip ~60
Check an IP address or host using NexIP IP diagnostics. Runs on NexIP servers, uses account quota and stores history. Example: target="1.1.1.1".
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | IP address, domain or URL to inspect. |
No output schema declared.
No examples provided.
check_meta ~55
Inspect page title, description, canonical, robots and social metadata. Runs on NexIP servers, uses account quota and stores history. Example: target="https://example.com".
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Public webpage URL to inspect. |
No output schema declared.
No examples provided.
check_redirects ~50
Follow and inspect an HTTP redirect chain. Runs on NexIP servers, uses account quota and stores history. Example: target="https://example.com".
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Public URL to inspect. |
No output schema declared.
No examples provided.
check_robots ~50
Inspect robots.txt availability and directives. Runs on NexIP servers, uses account quota and stores history. Example: target="https://example.com".
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Public website URL to inspect. |
No output schema declared.
No examples provided.
check_site ~52
Check website availability, HTTP status and response information. Runs on NexIP servers, uses account quota and stores history. Example: target="https://example.com".
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Public website URL to inspect. |
No output schema declared.
No examples provided.
check_sitemap ~54
Validate and inspect an XML sitemap. Runs on NexIP servers, uses account quota and stores history. Example: target="https://example.com/sitemap.xml".
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Public sitemap URL or website URL. |
No output schema declared.
No examples provided.
check_ssl ~49
Inspect SSL/TLS certificate and connection information. Runs on NexIP servers, uses account quota and stores history. Example: target="example.com".
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Domain or hostname to inspect. |
No output schema declared.
No examples provided.
check_whois ~50
Read public WHOIS information for a domain. Runs on NexIP servers, uses account quota and stores history. Example: target="example.com".
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Domain name to inspect. |
No output schema declared.
No examples provided.
get_account_plan ~27
Return the current NexIP account plan available to this MCP connection. Example: arguments={}.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| account | object | yes | – |
| ok | boolean | yes | – |
| plan | object | yes | – |
| workspace | object | yes | – |
No examples provided.
get_api_limits ~27
Return API and MCP-related limits for the current NexIP account. Example: arguments={}.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| limits | object | yes | – |
| ok | boolean | yes | – |
| plan | string | yes | – |
| workspace | object | yes | – |
No examples provided.
render_website_report ~200
Render a NexIP website report card from already obtained tool results. First call check_site, check_dns or check_ssl, then pass only verified fields; never invent statuses. This tool does not perform a network check, persist data, or consume diagnostic quota. Example: target="https://example.com", http_status=200.
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | – | Up to eight rows copied from already verified diagnostics. |
| dns_status | string | – | DNS result status from check_dns; unknown if untested. |
| http_status | integer | – | HTTP response code observed by check_site; omit if not measured. |
| response_ms | integer | – | Observed response time in milliseconds; omit if unavailable. |
| summary | string | – | Short factual summary based on earlier NexIP results. |
| target | string | yes | Public http(s) URL from prior NexIP diagnostic. |
| tls_status | string | – | TLS result status from check_ssl; unknown if untested. |
No output schema declared.
No examples provided.
How do I install the NexIP MCP server?
NexIP is a hosted endpoint at https://nexip.ru/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 · nexip.ru
claude mcp add --transport http ru-nexip-mcp 'https://nexip.ru/mcp'
What is the NexIP MCP server?
NexIP is an MCP server listed in the public MCP registry as ru.nexip/mcp. Network, domain and website diagnostics for AI clients via MCP. This page covers its hosted endpoint (https://nexip.ru/mcp).
Is the NexIP MCP server safe to use?
NexIP 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 NexIP MCP server expose?
NexIP exposes 13 tools: check_ip, check_dns, check_whois, check_ssl, check_site, and 8 more. Their descriptions and schemas cost roughly 774 tokens of context every time the server is loaded.
Does the NexIP MCP server require authentication?
Yes. NexIP 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 NexIP MCP server still maintained?
NexIP 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.