Ncrypt
REMOTE · NCRYPT.ME
Share documents privately from an AI agent. The agent gets a link; it cannot read the file.
Available components
Last scanned (16 hours ago)
Scores higher than 90% of remote servers
Reachable. Last reached 7 Nov 2026.
Category Documents and Files
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 Usability71
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 7 Nov 26 +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.
- 6 Nov 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
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 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.
- 26 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.
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 7 Nov 2026 · Probed https://ncrypt.me/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ncrypt.me | CN=YR2,O=Let's Encrypt,C=US | 21 Oct 2026 | 19 Jan 2027 | RSA 2048 | SHA256-RSA | 615cccdfbee3102db8b954c41b32aee419d |
| SANs: ncrypt.me | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ncrypt.me. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| me. | DS published | 45352 | 8 | Verified |
| ncrypt.me. | 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="ncrypt", resource_metadata="https://ncrypt.me/.well-known/oauth-protected-resource", error="invalid_token"
Bearer realm="ncrypt", resource_metadata="https://ncrypt.me/.well-known/oauth-protected-resource", error="invalid_token"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'nonce-YzYwNDFiMzktMGNkOS00MWE4LWJlMWEtOGNhOTg1YWRkYWUw' 'strict-dynamic'; style-src 'self' 'unsafe-inline' https://cdn.paddle.com; img-src 'self' data: blob: https:; font-src 'self' data:; connect-src 'self' https://*.supabase.co wss://*.supabase.co blob: https://cdn.paddle.com https://*.paddle.com https://www.google-analytics.com https://*.google-analytics.com https://analytics.google.com https://*.analytics.google.com; worker-src 'self' blob:; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; frame-src 'self' blob: https://*.paddle.com https://checkout.paddle.com |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=() |
Protected resource metadata
| Document | https://ncrypt.me/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://ncrypt.me/api/mcp |
| Authorisation server | https://cnvlulxzupuqsautbuks.supabase.co/auth/v1 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ncrypt.me/api/mcp | Verified | 200 | |
| http (plaintext) | http://ncrypt.me/api/mcp | HTTPS enforced | 308 | https://ncrypt.me/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 →
ncrypt_add_share_link Add another share link ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| documentId | string | yes | 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. |
No output schema declared.
No examples provided.
ncrypt_create_share_link Create a private share link ~267
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
ncrypt_get_view_analytics Get view analytics ~36
Return who viewed a document, when, on what device and for how long.
| Name | Type | Req | Description |
|---|---|---|---|
| documentId | string | yes | – |
No output schema declared.
No examples provided.
ncrypt_list_documents List shared documents ~27
List the documents in the owner's Ncrypt workspace with their share codes and view counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
remote · ncrypt.me
claude mcp add --transport http andyrzr-bot-ncrypt 'https://ncrypt.me/api/mcp'
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.