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.

LexiShield AI — 6-Agent GDPR, EU AI Act & Contract Redlining Server

REMOTE · LEXISHIELD-AI.RUN402.COM

Run deterministic SaaS contract redlining, GDPR Art. 28 DPA & EU AI Act compliance audits.

+3 this week 68 Trust /100

Last scanned (2 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Security

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 Security63
Transport & Reachability100
Schema Quality & AI Usability58
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 319 tokens (~79/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
  • Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 57% 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
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.

  • 4 Nov 26 +1

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

  • 2 Nov 26 +1

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

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 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 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.

  • 26 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.

  • 24 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.

  • 22 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.

  • 20 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 50 → 79 ▼ functional
    • Tool coverage: 25% → 57% ▲ functional
    • Schema quality: good → fair functional
    • New tool “verify_payment_and_unlock” 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 5 Nov 2026 · Probed https://lexishield-ai.run402.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.run402.com CN=Amazon RSA 2048 M04,O=Amazon,C=US 28 Oct 2026 13 May 2027 RSA 2048 SHA256-RSA 593fbaa72723521aaf2c0c5cefcd59d
SANs: *.run402.com, run402.app, *.run402.app
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of lexishield-ai.run402.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
run402.com. 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 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://lexishield-ai.run402.com/api/mcp Verified 200
http (plaintext) http://lexishield-ai.run402.com/api/mcp HTTPS enforced 301 https://lexishield-ai.run402.com/api/mcp
MCP tools · 4 exposed · ~281 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
audit_domain ~57

6-Agent SaaS Contract, GDPR Art. 28 DPA & EU AI Act Auditor — scans any public HTTPS domain and returns deterministic readiness scores and remediation artifacts.

NameTypeReqDescription
domainstringyesTarget domain (e.g. stripe.com)

No output schema declared.

No examples provided.

get_package_manifest ~37

Returns SHA-256 checksums, byte sizes, and file trees for all turnkey SaaS source .ZIP archives and Executive Digital Pack documents.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

submit_buyer_offer ~57

Creates an instant $1 Flash Trial or custom buyout settlement link (Tonkeeper TON / Base USDC).

NameTypeReqDescription
email_or_contactstring––
offer_usdnumber––
tierstring––

No output schema declared.

No examples provided.

verify_payment_and_unlock ~130

Verifies a Base USDC/USDT or Tonkeeper TON/USDT-TON payment (by tx_hash, wallet address, or order reference) and returns the full unredacted Pro deliverables and 6-file download pack.

NameTypeReqDescription
domainstring–Target domain or query input to unlock
plan_pricenumber–Paid amount in USD (e.g. 1, 5, 15, 19, or 149)
tx_hashstringyes0x... transaction hash, 0x... sender wallet, or TON event/order reference

No output schema declared.

No examples provided.

Install

How do I install the LexiShield AI — 6-Agent GDPR, EU AI Act & Contract… MCP server?

LexiShield AI — 6-Agent GDPR, EU AI Act & Contract… is a hosted endpoint at https://lexishield-ai.run402.com/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 · lexishield-ai.run402.com

# add to Claude Code
claude mcp add --transport http sh-surge-lexishield-ai-mcp 'https://lexishield-ai.run402.com/api/mcp'
Common questions

What is the LexiShield AI — 6-Agent GDPR, EU AI Act & Contract… MCP server?

LexiShield AI — 6-Agent GDPR, EU AI Act & Contract… is an MCP server listed in the public MCP registry as sh.surge.lexishield-ai/mcp. Run deterministic SaaS contract redlining, GDPR Art. 28 DPA & EU AI Act compliance audits. This page covers its hosted endpoint (https://lexishield-ai.run402.com/api/mcp).

Is the LexiShield AI — 6-Agent GDPR, EU AI Act & Contract… MCP server safe to use?

LexiShield AI — 6-Agent GDPR, EU AI Act & Contract… scores 68 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 LexiShield AI — 6-Agent GDPR, EU AI Act & Contract… MCP server expose?

LexiShield AI — 6-Agent GDPR, EU AI Act & Contract… exposes 4 tools: audit_domain, get_package_manifest, verify_payment_and_unlock, submit_buyer_offer. Their descriptions and schemas cost roughly 281 tokens of context every time the server is loaded.

Does the LexiShield AI — 6-Agent GDPR, EU AI Act & Contract… MCP server require authentication?

No. We connected to LexiShield AI — 6-Agent GDPR, EU AI Act & Contract… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the LexiShield AI — 6-Agent GDPR, EU AI Act & Contract… MCP server still maintained?

LexiShield AI — 6-Agent GDPR, EU AI Act & Contract… 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.