Nexargio Sovereign Model Context Protocol (MCP) Server
The Sovereign Cyber-Physics Defense Organ for Autonomous AI Agents
Connects Claude Desktop, Cursor IDE, Antigravity, and autonomous agent frameworks directly to the Nexargio Autonomous Cyber-Physics & Neural Defense Gateway.
🛠️ The Unified Sovereign Tool: nexargio_scan
We provide ONE single, polymorphic tool. No confusion, no multiple buttons:
nexargio_scan(target: str, scan_mode: str = "fast")
What target accepts:
- Full URL: e.g.
https://login.microsoftonline.portal-security-check.com/auth - Domain name: e.g.
portal-security-check.com(automatically normalized tohttps://) - QR Code Image: e.g.
C:\Downloads\invoice_qr.pngor Base64 (automatically decodes to URL and scans the destination)
What it executes:
- All 18 DOM Primitives (credential sinks, login forms, hidden fields, exfiltration actions)
- Sensory DAG (DNS domain age/NRD, TLS/X.509 cert authority, BGP ASN routing)
- Brand Contradiction Analysis (detects mimicry of Microsoft, Google, PayPal, Amazon, etc.)
- Autonomous Neural Reasoning:
- Single Scan: Evaluated by Qwen for deep forensic explanation and verdict.
- Bulk / Fleet Scan: Evaluated by JEV for high-velocity probability scoring.
- RFC 3161 NIST SHA-256 Notarization: Returns an immutable evidence seal for SOC compliance.
🚀 Connect to Claude Desktop
Option A: Via uvx (Recommended - Zero Path Dependency)
In %APPDATA%\Claude\claude_desktop_config.json:
{
"mcpServers": {
"nexargio": {
"command": "uvx",
"args": ["nexargio-mcp"],
"env": {
"NEXARGIO_API_KEY": "<YOUR_PORTAL_API_KEY>",
"NEXARGIO_GATEWAY_URL": "https://nexargio-vip-gateway-bepltxkx4a-el.a.run.app"
}
}
}
}
Option B: Local Direct Python Path
{
"mcpServers": {
"nexargio": {
"command": "python",
"args": [
"c:\\Users\\venky\\my project 4-1\\myproject\\nexargio_mcp.py"
],
"env": {
"NEXARGIO_API_KEY": "<YOUR_PORTAL_API_KEY>",
"NEXARGIO_GATEWAY_URL": "https://nexargio-vip-gateway-bepltxkx4a-el.a.run.app"
}
}
}
}
🚀 Connect to Cursor IDE
In .cursor/mcp.json:
{
"mcpServers": {
"nexargio-defense": {
"command": "uvx",
"args": ["nexargio-mcp"],
"env": {
"NEXARGIO_API_KEY": "<YOUR_PORTAL_API_KEY>"
}
}
}
}
🧪 Verification
Run the validation test:
python "c:\Users\venky\my project 4-1\myproject\test_mcp_client.py"
Metadata
Release files for nexargio-mcp 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| nexargio_mcp-1.1.0.tar.gz | 10.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nexargio_mcp-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 20.9 kB
Release files / nexargio_mcp-1.1.0.tar.gz
| Download URL | nexargio_mcp-1.1.0.tar.gz |
|---|---|
| Size | 10.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5a0933e0dcc9fcc862ed5b4747a87e77c492fb07f310ff3386e580f7d11c66c1
|
|
BLAKE2b-256 checksum How to use checksums |
d027ced44a379606a683bbd408d5e2fbd4f16667d84467c51d740cc359809840
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 3, 2026.
Transparency logRelease files / nexargio_mcp-1.1.0-py3-none-any.whl
| Download URL | nexargio_mcp-1.1.0-py3-none-any.whl |
|---|---|
| Size | 10.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dd730fe7efb2c80408184e2770bbcdd55e860c1ecea788cc0861b4738ef7c3b0
|
|
BLAKE2b-256 checksum How to use checksums |
46ed0a1675914ac641f06b116396aa39675c91895e5cc9de979de306f1cccbfa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 3, 2026.
Transparency log