NordLayer Intelligence by NordStellar MCP
Connect any MCP-compatible AI assistant to NordLayer Intelligence via the NordStellar MCP so you can detect external exposure, prioritize risks, and act — directly from chat.
NordLayer Intelligence gives you real-time visibility into your external attack surface and threat landscape: exposed assets, leaked credentials, brand impersonations, dark web mentions, and malware infections.
What you can detect
Ask your AI assistant about the same risk areas covered by NordLayer Intelligence:
- External vulnerabilities — open ports, forgotten subdomains, exposed admin panels, public config files and backups, and other attack-surface findings
- Compromised identities — stolen credentials, active session cookies, and autofill data that could enable account takeover
- Exposed sensitive data — dark web and criminal-forum mentions of company files, customer records, and other sensitive information
- Brand impersonation — fake domains, look-alike brand abuse, and related squatting activity
- Malware infections — devices where information-stealing malware has captured company data
What you get
- Natural-language access to your NordLayer Intelligence data through NordStellar MCP
- No need to switch to the UI or write GraphQL by hand
- Secure login via your NordStellar account
Setup
1. Add to your MCP client
Add the NordStellar MCP server to your AI assistant’s MCP configuration (e.g. mcp.json or the equivalent in your client):
{
"nordstellar-mcp": {
"command": "uvx",
"args": [
"nordstellar-mcp",
"https://platform-mcp.nordstellar.com/mcp"
]
}
}
uvx pulls the nordstellar-mcp package from PyPI. To pin a version, use e.g. "--from", "nordstellar-mcp==0.1.6" before the tool name in args.
To run the same from a shell:
uvx nordstellar-mcp https://platform-mcp.nordstellar.com/mcp
The default endpoint is https://platform-mcp.nordstellar.com/mcp. Contact your NordStellar administrator if you need a different URL.
2. First-time login
When you first use NordStellar, a browser window will open. Sign in with your NordStellar credentials. After that, you’re set—the connection stays authenticated until you sign out or the session expires.
3. Start using it
Ask your AI assistant things like:
- “What projects do I have?”
- “Show me critical external vulnerabilities that are still unresolved”
- “Are there leaked employee credentials for our domains?”
- “Any dark web mentions of our company this month?”
- “Which look-alike domains look like brand impersonation?”
- “Do we have malware infections with active session cookies?”
4. Install agent skills (optional)
You can install bundled skills the same way as other npx skills add workflows (for example the Google Workspace CLI repo):
# Install all skills at once
npx skills add https://github.com/NordStellar/nordstellar-mcp
# Or pick only what you need
npx skills add https://github.com/NordStellar/nordstellar-mcp/tree/main/skills/nordstellar-general
npx skills add https://github.com/NordStellar/nordstellar-mcp/tree/main/skills/attack-surface-management
npx skills add https://github.com/NordStellar/nordstellar-mcp/tree/main/skills/dark-web-search
npx skills add https://github.com/NordStellar/nordstellar-mcp/tree/main/skills/domain-squatting
npx skills add https://github.com/NordStellar/nordstellar-mcp/tree/main/skills/malware-infection-analysis
Credential storage
Session cookies are saved in your OS credential store under the service name NordStellar MCP:
- macOS — Keychain
- Windows — Credential Locker
- Linux — Freedesktop Secret Service (for example GNOME Keyring or KWallet)
If no secure credential store is available, the proxy keeps credentials in memory only. In that mode, credentials are lost when the process exits.
Any application running as your user account may be able to read stored credentials through the OS credential APIs. This is the standard behavior for desktop credential stores.
Clear stored credentials
To remove stored session cookies, use one of the following:
- Any platform: run
nordstellar-mcp --logout - macOS: run
security delete-generic-password -s "NordStellar MCP" - Windows: remove the Generic Credential named
NordStellar MCPfrom Credential Manager - Linux: remove the
NordStellar MCPsecret from your Secret Service keyring (for example with Seahorse or KWallet Manager)
Requirements
- uv installed (
curl -LsSf https://astral.sh/uv/install.sh | sh) - Python 3.10 or newer (uv handles this automatically)
- keyring — installed automatically as a dependency. Provides persistent, secure credential storage using each platform's native backend:
- macOS — Keychain
- Windows — Credential Locker
- Linux — Freedesktop Secret Service (GNOME Keyring / KWallet). Requires
gnome-keyringorkwalletto be available; on headless systems, see the keyring docs for setup instructions.
Community
- Code of Conduct
- Security policy
- Contributing
- License (GNU General Public License v3.0 only)
Need help?
- Product overview: NordLayer Intelligence
- MCP endpoint / access: contact your NordStellar administrator
Metadata
Release files for nordstellar-mcp 0.1.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| nordstellar_mcp-0.1.6.tar.gz | 33.5 kB | With provenance | Details for nordstellar_mcp-0.1.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| nordstellar_mcp-0.1.6-py3-none-any.whl | Python 3 | none | any | Details for nordstellar_mcp-0.1.6-py3-none-any.whl |
Total release size: 72.8 kB
Release files / nordstellar_mcp-0.1.6.tar.gz
| Download URL | nordstellar_mcp-0.1.6.tar.gz |
|---|---|
| Size | 33.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a8f0fcb7052f6fdc08676a5744823294bd443f35ecf8be89b22cfb03301b3ffa
|
|
BLAKE2b-256 checksum How to use checksums |
0f22981e52bdfc27f7fdb77d914d373514f5a638aec7b3289d2b82a18f4c1212
|
| 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 20, 2026.
Transparency logRelease files / nordstellar_mcp-0.1.6-py3-none-any.whl
| Download URL | nordstellar_mcp-0.1.6-py3-none-any.whl |
|---|---|
| Size | 39.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
caccf8a4d23d10b90313746fedf49eb6ddb26afdae9b902bccecbfe2563a1c03
|
|
BLAKE2b-256 checksum How to use checksums |
d3bbb42be23d7952e35b31a020980603c985517fb70fcd0918ec55851688e193
|
| 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 20, 2026.
Transparency logSecurity for nordstellar-mcp 0.1.6
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for nordstellar_mcp-0.1.6.tar.gz
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 20, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.