MCP servers › io.github.keplertech › naja-scope
MCP server · registry snapshot 2026-11-16 · last checked 2026-11-16
naja-scope MCP server
Registry name io.github.keplertech/naja-scope
by keplertech · GitHub account (the registry's namespace rule)repository: same ownerSource ↗PyPI ↗Website ↗
Let AI agents explore SystemVerilog, Verilog and VHDL designs: connectivity, hierarchy, source. — the publisher's description
Summary
io.github.keplertech/naja-scope is a local MCP server listed in the official MCP registry at version 0.1.26, under the namespace of the GitHub account keplertech. Its linked repository, github.com/keplertech/naja-scope, belongs to the same GitHub account.
Record checks
7 of 8 record checks met · 1 does not apply
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- not met: Repository publishes a security policy (SECURITY.md)
- met: Package names its licence with a standard (SPDX) identifier
- met: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- met: No known critical or high advisory in the package or its dependencies
- #3,309 of 20,610 packages by monthly downloads, tied with 3 others
- #2,100 of 28,859 repositories by GitHub stars, tied with 48 others
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- local package
- Transport
- standard input/output
- Your own values
- none declared (not a guarantee)
- Package
- PyPI · listed version current
- License
- Apache-2.0
- Dependencies
- no known high or critical advisories
- Repository
- public
- Last tested
- not tested
Tool list
Not read: It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. So there is no tool-list size and no result from the three APIs.
How fresh this is
- Live-tested
- no
- Last tested
- not tested
- Latest version
- 0.1.26, published 2026-11-15 (registry, as of the 2026-11-16 snapshot)
- First listed version
- 2026-11-08 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 3 versions listed, 2026-11-08 to 2026-11-15; 3 in the 90 days before the 2026-11-16 snapshot.(versions still listed in the registry only)
Most recent 3 versions
0.1.26· 2026-11-150.1.25· 2026-11-120.1.24· 2026-11-08
- Registry data
- snapshot 2026-11-16
- Package and repository
- checked 2026-11-16
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
Version 0.1.25 (published 2026-11-12) → 0.1.26 (published 2026-11-15), between the registry lists of 2026-11-15 and 2026-11-16.
The publisher’s GitHub release note for v0.1.26 (“naja-scope v0.1.26”), published 2026-11-15.
Read the release note (the publisher’s text, shown as plain text)
# naja-scope 0.1.26 candidate Requires **najaeda 0.7.35 or newer**. The optional schematic extra now requires **naja-schematic >=0.3.0,<0.4**. This candidate has not been published. ## Browser traces and headless export `show_schematic_net(path, trace=False, add=True, color=None)` draws a pin's net in the browser. Set `trace=True` to draw its combinational fan-in back to flops, ports and blackboxes. Set `add=False` to replace the drawing. Targets use scope pin/port paths, including anonymous `#id` instances and explicit bus-bit selections. `export_schematic(file, instances=None, nets=None, traces=None, view_options=None, scale=1.0)` writes a fresh SVG or PNG without starting a browser. Supply 1–200 total targets; the file suffix selects the format. Instances draw boxes; nets and traces take pin/port paths. PNG supports a resolution scale. The result reports the local file path, format and size. Existing destination files may be overwritten. `open_schematic` and `export_schematic` accept `view_options`: instance/model labels, fanout rows and limits, grouping by model/hierarchy/role/pin, and convergence outlines. Export options additionally include title, caption, legend and hiding UI glyphs. Export targets and options are independent of the browser's current drawing and annotation state. The integration uses the installed naja-schematic package directly on the current raw naja universe, under the existing design lock. It does not reload or elaborate the design. Existing selection, annotations and reload behavior are retained. Custom styling and batch exports are available upstream but are not exposed as scope tools in this candidate. ## Validation and compatibility Validated with the published naja-schematic 0.3.0 macOS universal2 wheel and published najaeda 0.7.35. Real HTTP/WebSocket and native headless-renderer tests cover anonymous paths, scalar and bus pins, replay, locking, stale selections, snapshot reload, SVG structure, PNG output, invalid targets/options and file errors. A loaded UART cone export reaches logic and state registers inside the `u_tx` hierarchy. Platform CI now installs the schematic extra. CVA6 upstream was rechecked on 2026-11-15: latest release remains v5.3.0 (`2ef1c1b1fca419354920c5487293bc605294904e`), and master remains `742dc82a0c706e0a3bfb98b709fd3ee06d50d12a`. [CVA6 #3594](https://github.com/openhwfoundation/cva6/issues/3594) remains open with two comments. The engine and upstream revision are unchanged from the prior validation, so master was not retried. Retain v5.3.0. The compatible isolated RV32 snapshot built for the 0.1.25 validation is reused for the three unchanged CVA6 regressions; the shared 0.7.34 cache is preserved. See [schematic validation](../validation/naja-schematic-0.3.0.md). The complete local suite passes **177 tests, none skipped**, including all three CVA6 regressions, using: ```sh PYTHONPATH=/tmp/naja-scope-025-validation:src .venv/bin/python -m pytest -q -rs -p fresh_cva6 ``` Wheel and sdist build successfully and pass `twine check`; runtime and MCP metadata agree on 0.1.26. No tag, publication, or MCP Registry submission has been performed.
Source: the official MCP Registry list on 2026-11-15 and on 2026-11-16; release notes from the GitHub Releases API, checked 2026-11-16.
What it is
How do I add it to my client?
Config from the registry entry
From the PyPI package naja-scope
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.
Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
"mcpServers": {
"naja-scope": {
"command": "uvx",
"args": [
"naja-scope==0.1.26"
]
}
}
}Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"naja-scope": {
"command": "uvx",
"args": [
"naja-scope==0.1.26"
]
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"naja-scope": {
"type": "stdio",
"command": "uvx",
"args": [
"naja-scope==0.1.26"
]
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"naja-scope","type":"stdio","command":"uvx","args":["naja-scope==0.1.26"]}'Claude Code
claude mcp add --transport stdio naja-scope -- uvx naja-scope==0.1.26
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"naja-scope": {
"command": "uvx",
"args": [
"naja-scope==0.1.26"
],
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"naja-scope": {
"command": "uvx",
"args": [
"naja-scope==0.1.26"
]
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.naja-scope] command = "uvx" args = ["naja-scope==0.1.26"]
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"naja-scope": {
"command": "uvx",
"args": [
"naja-scope==0.1.26"
]
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- uvx naja-scope==0.1.26
- This runs the publisher's code on your machine (uvx). Read its README first.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Can it be installed, and is it up to date?
Version pin · advisories
Listed version
- Registry lists
- 0.1.26
- Latest stable
- 0.1.26
- Status
- current
- Withdrawn
- no
Source: pypi.org · 2026-11-16. About the version the registry lists; a manual install may resolve to a different one.
Dependency advisories
Counted in the full dependency tree as resolved on 2026-11-16 (OSV.dev; each bar counts advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha256-cc8d123fb6e318c91…
- License
- Apache-2.0
Source: the package registry · 2026-11-16.
Usage
- Downloads
- 1,126 in the last month
Source: pypistats.org · 2026-11-16.
What do the published files and outside lists say?
Read as text · nothing run · no tool called
Package files
- Python version and wheels (PyPI). Needs Python 3.10 or later (requires_python
>=3.10). Source: pypi.org/pypi/naja-scope/0.1.26/json · read 2026-11-16. - Build workflow. Built and published by GitHub Actions workflow
publish.ymlinkeplertech/naja-scope(PyPI provenance). Source: pypi.org/integrity/naja-scope/0.1.26/naja_scope-0.1.26-py3-none-any.whl/provenance · read 2026-11-16.
Registry entry
- Same package in other registry entries. No other registry entry lists this entry's npm or PyPI package at a newer version. Source: own registry snapshot · read 2026-11-16.
Outside lists
- CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-16. This product uses the NVD API but is not endorsed or certified by the NVD.
- GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-16. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-16. Source: read 2026-11-16.
- Cline marketplace. Not in the Cline marketplace on 2026-11-16. Source: read 2026-11-16.
Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Version 0.1.26 on PyPI | Exists and can be installed | matches | PyPI · 2026-11-16 |
| Repository github.com/keplertech/naja-scope | Opens publicly | matches | api.github.com · 2026-11-16 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.keplertech
- GitHub owner
- an organization (keplertech)
- Repository
- github.com/keplertech/naja-scope
- Stars
- 22
- Repository age
- 91–180 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)
Source: the registry entry and api.github.com · 2026-11-16; security policy read from GitHub · 2026-11-09.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating7 of 8 record checks met · 1 does not apply
- #3,309 of 20,610 packages by monthly downloads, tied with 3 others
- #2,100 of 28,859 repositories by GitHub stars, tied with 48 others
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
- MetPackage names its licence with a standard (SPDX) identifierApache-2.0
- MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
- Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
- MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-16 (security policy 2026-11-09). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about io.github.keplertech/naja-scope
Answered from the data aboveWho publishes io.github.keplertech/naja-scope?
The registry ties the namespace io.github.keplertech to the GitHub account keplertech; only its owner can publish under it. Its linked repository, github.com/keplertech/naja-scope, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.
Is io.github.keplertech/naja-scope safe to install?
We do not rate servers as safe or unsafe. 7 of its 8 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Has io.github.keplertech/naja-scope been security tested?
No. It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's.
Does io.github.keplertech/naja-scope publish a security policy?
We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.
Is the listed version current?
Yes. The registry lists 0.1.26, the latest stable release on PyPI.
Where is the source code of io.github.keplertech/naja-scope?
In github.com/keplertech/naja-scope, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
Has it been tested?
Feature #1It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. — our limit
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.keplertech/naja-scope: MCP server record.” Data checked 2026-11-16. https://protocolprobe.com/mcp/servers/io.github.keplertech/naja-scope
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.keplertech/naja-scope)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).
Write to hello@protocolprobe.com · corrections log · methodology