# Ncrypt (remote · ncrypt.me)

Share documents privately from an AI agent. The agent gets a link; it cannot read the file.

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

## Components

- remote · `ncrypt.me`: 85/100 (this document), [markdown](https://verifymcp.io/servers/andyrzr-bot-ncrypt/api-mcp-2.md), [page](https://verifymcp.io/servers/andyrzr-bot-ncrypt/api-mcp-2)

## Channel facts

- Endpoint: `https://ncrypt.me/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.1.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-07.

- **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**: 71/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 531 tokens (~132/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 92% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Ncrypt MCP server?

Ncrypt is a hosted endpoint at https://ncrypt.me/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 andyrzr-bot-ncrypt 'https://ncrypt.me/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "andyrzr-bot-ncrypt": {
      "url": "https://ncrypt.me/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "andyrzr-bot-ncrypt": {
      "type": "http",
      "url": "https://ncrypt.me/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.andyrzr-bot-ncrypt]
url = "https://ncrypt.me/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "andyrzr-bot-ncrypt": {
      "type": "remote",
      "url": "https://ncrypt.me/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add andyrzr-bot-ncrypt --url 'https://ncrypt.me/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  andyrzr-bot-ncrypt:
    url: "https://ncrypt.me/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "andyrzr-bot-ncrypt": {
      "Transport": "http",
      "Url": "https://ncrypt.me/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add andyrzr-bot-ncrypt -t streamable-http -u 'https://ncrypt.me/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "andyrzr-bot-ncrypt": {
      "type": "http",
      "url": "https://ncrypt.me/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-11-07 (score 85, +1)

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

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

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 84, +1)

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

### 2026-11-03 (score 83, +1)

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

### 2026-11-01 (score 82, +1)

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

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

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

### 2026-10-28 (score 80, +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-26 (score 79, +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.

## MCP tools (4)

### `ncrypt_create_share_link` (~267 tokens)

Create a private share link

Upload a document to Ncrypt and return a private share link. The recipient must enter their name and a valid email address before they can read a single page, the file is encrypted at rest, and downloads are denied until the owner approves them. Supply the file as base64 content, a public https URL, or a path in the owner's own storage.

Input parameters:

- `allow_forward` (boolean): Whether the viewer may re-share the link. Defaults to false.
- `content_base64` (string): The file contents encoded as base64. Best for small files.
- `download_mode` (string): Whether the viewer may ask for a download. Defaults to request.
- `filename` (string, required): The file name including its extension.
- `label` (string): Who this share is for, for example a name or a channel. It is only shown to the owner and is used to tell shares apart in the view history.
- `name` (string): Project or document name shown in the link preview.
- `storage_path` (string): A path inside the owner's own Ncrypt storage, for example tenant/<tenant id>/<document id>/source.bin.
- `title` (string): Document title.
- `url` (string): A public https URL the file can be downloaded from.

### `ncrypt_add_share_link` (~122 tokens)

Add another share link

Create an additional share link for a document that already exists. A document can be shared as many times as needed. Each link carries its own code and trace code, so the view history records which share each viewer came through.

Input parameters:

- `documentId` (string, required): The document to share again.
- `label` (string): Who this share is for, for example a name or a channel.
- `trace_code` (string): A short trace code for the link, 3 to 8 letters and numbers. One is generated if it is left out.

### `ncrypt_list_documents` (~27 tokens)

List shared documents

List the documents in the owner's Ncrypt workspace with their share codes and view counts.

### `ncrypt_get_view_analytics` (~36 tokens)

Get view analytics

Return who viewed a document, when, on what device and for how long.

Input parameters:

- `documentId` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/andyrzr-bot-ncrypt/api-mcp-2#diagnostics

## Score history

- 2026-11-07: 85
- 2026-11-06: 84
- 2026-11-05: 84
- 2026-11-04: 83
- 2026-11-03: 83
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 80
- 2026-10-28: 80
- 2026-10-27: 79
- 2026-10-26: 79
- 2026-10-25: 78
- 2026-10-24: 78
- 2026-10-23: 78
- 2026-10-22: 77
- 2026-10-21: 77

## Common questions

### What is the Ncrypt MCP server?

Ncrypt is an MCP server listed in the public MCP registry as io.github.andyrzr-bot/ncrypt. Share documents privately from an AI agent. The agent gets a link; it cannot read the file. This page covers its hosted endpoint (https://ncrypt.me/api/mcp).

### Is the Ncrypt MCP server safe to use?

Ncrypt scores 85 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 Ncrypt MCP server expose?

Ncrypt exposes 4 tools: ncrypt_create_share_link, ncrypt_add_share_link, ncrypt_list_documents, ncrypt_get_view_analytics. Their descriptions and schemas cost roughly 452 tokens of context every time the server is loaded.

### Does the Ncrypt MCP server require authentication?

Yes. Ncrypt 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 Ncrypt MCP server still maintained?

Ncrypt is still listed as active in the MCP registry. We last reached this channel on 7 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 Ncrypt MCP server?

VerifyMCP ran 13 checks on Ncrypt, 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.

## Links

- Remote endpoint: https://ncrypt.me/api/mcp
- Authorisation metadata: https://ncrypt.me/.well-known/oauth-protected-resource/api/mcp
- Repository: https://github.com/andyrzr-bot/Ncrypt
- Website: https://ncrypt.me/
- Changelog RSS feed: https://verifymcp.io/servers/andyrzr-bot-ncrypt/api-mcp-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/andyrzr-bot-ncrypt/api-mcp-2/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/andyrzr-bot-ncrypt/api-mcp-2.json
- HTML version of this page: https://verifymcp.io/servers/andyrzr-bot-ncrypt/api-mcp-2