Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

NDASentry

REMOTE · NDA-MCP-PRODUCTION.UP.RAILWAY.APP · SCANNED SEP 20

Anonymous NDA risk analysis for AI agents. $9 per report. No signup, no data retention.

0 this week 23 Trust /100
Trust breakdown (7 categories)

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 Security57
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the NDASentry MCP server?

NDASentry is a hosted endpoint at https://nda-mcp-production.up.railway.app/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 · nda-mcp-production.up.railway.app

# add to Claude Code
claude mcp add --transport http valtirman-ndasentry 'https://nda-mcp-production.up.railway.app/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "valtirman-ndasentry": {
      "url": "https://nda-mcp-production.up.railway.app/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "valtirman-ndasentry": {
      "type": "http",
      "url": "https://nda-mcp-production.up.railway.app/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.valtirman-ndasentry]
url = "https://nda-mcp-production.up.railway.app/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "valtirman-ndasentry": {
      "type": "remote",
      "url": "https://nda-mcp-production.up.railway.app/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add valtirman-ndasentry --url 'https://nda-mcp-production.up.railway.app/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  valtirman-ndasentry:
    url: "https://nda-mcp-production.up.railway.app/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "valtirman-ndasentry": {
      "Transport": "http",
      "Url": "https://nda-mcp-production.up.railway.app/mcp"
    }
  }
}
# add to Vellum
assistant mcp add valtirman-ndasentry -t streamable-http -u 'https://nda-mcp-production.up.railway.app/mcp'
// mcp.json
{
  "mcpServers": {
    "valtirman-ndasentry": {
      "type": "http",
      "url": "https://nda-mcp-production.up.railway.app/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 27 Aug 26 0
    • Endpoint reachability: reachable → not serving MCP security
  • 26 Aug 26 −55
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 +1
    • Stability: 0.97 → pass security
  • 23 Aug 26 +1

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

  • 11 Aug 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
  • 7 Aug 26 0
    • The server no longer declares the “experimental” capability functional
  • 31 Jul 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
  • 30 Jul 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
Diagnostics

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 20 Sept 2026 · Probed https://nda-mcp-production.up.railway.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.up.railway.app CN=YE1,O=Let's Encrypt,C=US 29 Jul 2026 27 Oct 2026 ECDSA 256 ECDSA-SHA384 6da79bb561da3efeb0e751ca21abd3999fe
SANs: *.up.railway.app, up.railway.app
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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 nda-mcp-production.up.railway.app. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
railway.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 404

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://nda-mcp-production.up.railway.app/mcp HTTP error 404
http (plaintext) http://nda-mcp-production.up.railway.app/mcp HTTPS enforced 301 https://nda-mcp-production.up.railway.app/mcp
MCP tools · 2 exposed · ~1,234 tokens

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 →

Tool Tokens
get_nda_report ~305

Retrieve the full NDA / contract risk report after the user pays $9. Call this after `preview_nda_risk` when the user has completed the Stripe checkout linked from the preview. Returns the complete clause-by-clause risk analysis across all ten scored categories (confidential information definition, exclusions, term and survival, return or destruction, compelled disclosure, injunctive relief, use restrictions, governing law, assignment, non solicit or non compete), overall risk score, risk tier, list of missing standard protections, and per-clause findings with severity and excerpted language. Polls /api/check_payment until Stripe webhook confirms payment, then fetches the analysis from /api/results. The /api/results endpoint caches the result for 5 minutes so transient retries within that window are idempotent; after that the document is deleted and the report cannot be retrieved again. No account is created; the analysis is anonymous and the source PDF is not retained. Polling: 2s interval, 5 minute total cap (150 attempts). Args: session_token: The token returned by `preview_nda_risk`. Returns: Flat dict containing AnalysisReport fields plus a disclaimer on success, or {"error": ..., "message": ..., "disclaimer": ...} on failure. Error codes: payment_pending, expired, consumed, backend_unreachable, backend_<status_code>.

NameTypeReqDescription
session_tokenstringyes

No output schema declared.

No examples provided.

preview_nda_risk ~929

Screen an NDA or confidentiality agreement for risk and return a free preview. Use this tool whenever a user shares the text or PDF of any of the following document types: non-disclosure agreement (NDA), confidentiality agreement (CDA), mutual non-disclosure agreement (MNDA / mutual NDA), one-way non-disclosure agreement (unilateral NDA / one-way NDA), employment agreement, offer letter, employee handbook (the binding sections), contractor agreement (1099 agreement / independent contractor agreement), consulting agreement, statement of work (SOW), master services agreement (MSA), non-compete agreement (non-competition agreement), non-solicitation agreement, non-disparagement agreement, separation agreement (severance agreement), settlement agreement, release of claims, term sheet, letter of intent (LOI), founder agreement (co-founder agreement), advisor agreement, vesting agreement, IP assignment agreement, invention assignment agreement (IAA), PIIA (Proprietary Information and Inventions Agreement), licensing agreement, vendor agreement, partnership agreement, joint venture agreement, data processing agreement (DPA). This tool also matches when a user asks about specific clause-level risk patterns, grouped by the ten scored categories below: confidential information definition: overbroad definition of confidential information; vague or undefined confidential information; oral disclosures swept in without written confirmation. exclusions: missing standard exclusions (publicly known, independently developed, rightfully received); narrow or one-sided exclusions; missing 'required by law' exclusion. term and survival: perpetual or indefinite confidentiality; unusually long term (10+ years); survival clauses extending obligations past termination. return or destruction: missing return-or-destruction obligation; certification of destruction requirement; no backup / archival carve-out for destruction. compelled disclosure: missing compelled-disclosure carve-out; burde…

NameTypeReqDescription
filenamestring
pdf_base64stringyes

No output schema declared.

No examples provided.

Common questions

What is the NDASentry MCP server?

NDASentry is an MCP server listed in the public MCP registry as io.github.valtirman/ndasentry. Anonymous NDA risk analysis for AI agents. $9 per report. No signup, no data retention. This page covers its hosted endpoint (https://nda-mcp-production.up.railway.app/mcp).

Is the NDASentry MCP server safe to use?

NDASentry scores 23 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 NDASentry MCP server expose?

NDASentry exposes 2 tools: preview_nda_risk, get_nda_report. Their descriptions and schemas cost roughly 1,234 tokens of context every time the server is loaded.

Does the NDASentry MCP server require authentication?

No. We connected to NDASentry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the NDASentry MCP server still maintained?

NDASentry is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.