# NexIP (remote · nexip.ru)

Network, domain and website diagnostics for AI clients via MCP.

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

## Components

- remote · `nexip.ru`: 86/100 (this document), [markdown](https://verifymcp.io/servers/ru-nexip-mcp/nexip.md), [page](https://verifymcp.io/servers/ru-nexip-mcp/nexip)

## Channel facts

- Endpoint: `https://nexip.ru/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `2.9.0`

## 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-11-05.

- **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**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 823 tokens (~58/item across 14 items; 13 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 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 (15% 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

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

### Claude

```bash
claude mcp add --transport http ru-nexip-mcp 'https://nexip.ru/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ru-nexip-mcp": {
      "url": "https://nexip.ru/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ru-nexip-mcp": {
      "type": "http",
      "url": "https://nexip.ru/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ru-nexip-mcp]
url = "https://nexip.ru/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ru-nexip-mcp": {
      "type": "remote",
      "url": "https://nexip.ru/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ru-nexip-mcp --url 'https://nexip.ru/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ru-nexip-mcp:
    url: "https://nexip.ru/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ru-nexip-mcp": {
      "Transport": "http",
      "Url": "https://nexip.ru/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ru-nexip-mcp -t streamable-http -u 'https://nexip.ru/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ru-nexip-mcp": {
      "type": "http",
      "url": "https://nexip.ru/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-11-05 (score 86, +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-11-04 (score 85, +1)

- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security improvement] Transport: fail → pass
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.37

### 2026-11-03 (score 84, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.30 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-02 (score 84, +7)

- [security improvement] 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
- [functional regression] Schema quality: 49 → 58
- [functional improvement] Tool coverage: 65% → 100%
- [functional improvement] Tool “get_account_plan” now declares an output schema
- [functional improvement] Tool “get_api_limits” now declares an output schema
- [functional] First check of Tool coverage: 15
- [cosmetic] “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”

### 2026-10-31 (score 77, +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.

### 2026-10-29 (score 76, +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-10-28 (score 75, 0)

- [functional] Server version: 2.9.2 → 2.9.3

### 2026-10-27 (score 75, 0)

- [functional] Server version: 2.9.1 → 2.9.2

## MCP tools (13)

### `check_ip` (~60 tokens)

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

Input parameters:

- `target` (string, required): IP address, domain or URL to inspect.

### `check_dns` (~49 tokens)

Read DNS records for a domain using NexIP. Runs on NexIP servers, uses account quota and stores history. Example: target="example.com".

Input parameters:

- `target` (string, required): Domain name to inspect.

### `check_whois` (~50 tokens)

Read public WHOIS information for a domain. Runs on NexIP servers, uses account quota and stores history. Example: target="example.com".

Input parameters:

- `target` (string, required): Domain name to inspect.

### `check_ssl` (~49 tokens)

Inspect SSL/TLS certificate and connection information. Runs on NexIP servers, uses account quota and stores history. Example: target="example.com".

Input parameters:

- `target` (string, required): Domain or hostname to inspect.

### `check_site` (~52 tokens)

Check website availability, HTTP status and response information. Runs on NexIP servers, uses account quota and stores history. Example: target="https://example.com".

Input parameters:

- `target` (string, required): Public website URL to inspect.

### `check_headers` (~51 tokens)

Inspect HTTP response headers and security-related headers. Runs on NexIP servers, uses account quota and stores history. Example: target="https://example.com".

Input parameters:

- `target` (string, required): Public website URL to inspect.

### `check_redirects` (~50 tokens)

Follow and inspect an HTTP redirect chain. Runs on NexIP servers, uses account quota and stores history. Example: target="https://example.com".

Input parameters:

- `target` (string, required): Public URL to inspect.

### `check_robots` (~50 tokens)

Inspect robots.txt availability and directives. Runs on NexIP servers, uses account quota and stores history. Example: target="https://example.com".

Input parameters:

- `target` (string, required): Public website URL to inspect.

### `check_sitemap` (~54 tokens)

Validate and inspect an XML sitemap. Runs on NexIP servers, uses account quota and stores history. Example: target="https://example.com/sitemap.xml".

Input parameters:

- `target` (string, required): Public sitemap URL or website URL.

### `check_meta` (~55 tokens)

Inspect page title, description, canonical, robots and social metadata. Runs on NexIP servers, uses account quota and stores history. Example: target="https://example.com".

Input parameters:

- `target` (string, required): Public webpage URL to inspect.

### `render_website_report` (~200 tokens)

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.

Input parameters:

- `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, required): Public http(s) URL from prior NexIP diagnostic.
- `tls_status` (string): TLS result status from check_ssl; unknown if untested.

### `get_account_plan` (~27 tokens)

Return the current NexIP account plan available to this MCP connection. Example: arguments={}.

Output parameters:

- `account` (object)
- `ok` (boolean)
- `plan` (object)
- `workspace` (object)

### `get_api_limits` (~27 tokens)

Return API and MCP-related limits for the current NexIP account. Example: arguments={}.

Output parameters:

- `limits` (object)
- `ok` (boolean)
- `plan` (string)
- `workspace` (object)

## Diagnostics

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

## Score history

- 2026-11-05: 86
- 2026-11-04: 85
- 2026-11-03: 84
- 2026-11-02: 84
- 2026-11-01: 77
- 2026-10-31: 77
- 2026-10-30: 76
- 2026-10-29: 76
- 2026-10-28: 75
- 2026-10-27: 75
- 2026-10-26: 75
- 2026-10-25: 74
- 2026-10-24: 74
- 2026-10-23: 39
- 2026-10-22: 39
- 2026-10-21: 39
- 2026-10-20: 39
- 2026-10-19: 39
- 2026-10-18: 39
- 2026-10-17: 39
- 2026-10-16: 39
- 2026-10-15: 39
- 2026-10-14: 35
- 2026-10-13: 35
- 2026-10-12: 35
- 2026-10-10: 35
- 2026-10-07: 35
- 2026-10-04: 25
- 2026-10-03: 25
- 2026-10-02: 25

## Common questions

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

## Links

- Remote endpoint: https://nexip.ru/mcp
- Authorisation metadata: https://nexip.ru/.well-known/oauth-protected-resource/mcp
- Website: https://nexip.ru/api/mcp
- Changelog RSS feed: https://verifymcp.io/servers/ru-nexip-mcp/nexip.xml
- Changelog JSON feed: https://verifymcp.io/servers/ru-nexip-mcp/nexip.json
- HTML version of this page: https://verifymcp.io/servers/ru-nexip-mcp/nexip