Skip to content

MCP servers › io.github.novasolver › novasolver-studio

MCP server · registry snapshot 2026-11-01 · last checked 2026-11-01

io.github.novasolver/novasolver-studio

by novasolver · GitHub account (the registry's namespace rule)repository: same ownerSource ↗Website ↗

Free desktop CAE: import CAD/STL, solve FEM structural/thermal and CFD, verify the answer. — the publisher's description

4 of 5 record checks metversion 0.7.1Pythonstandard input/output

Summary

io.github.novasolver/novasolver-studio is a local MCP server listed in the official MCP registry at version 0.7.1, under the namespace of the GitHub account novasolver. Its linked repository, github.com/novasolver/novasolver-studio, belongs to the same GitHub account.

Record checks

4 of 5 record checks met · 4 do 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)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: not an npm or PyPI package
  • Not ranked by stars: 1 star (ranked from 10)

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

Key facts

Runs
local package
Transport
standard input/output
Your own values
none declared (not a guarantee)
Package
MCP bundle
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. This is our limit, not the server's. So there is no tool-list size and no result from the three APIs.

Add to your client

How fresh this is

Live-tested
no
Last tested
not tested
Latest version
0.7.1, published 2026-11-01 (registry, as of the 2026-11-01 snapshot)
First listed version
2026-10-26 (earliest version still in the registry; older removed versions would be earlier)
Version history
15 versions listed, 2026-10-26 to 2026-11-01; 15 in the 90 days before the 2026-11-01 snapshot.
Most recent 12 versions
  • 0.7.1 · 2026-11-01
  • 0.7.0 · 2026-10-31
  • 0.6.3 · 2026-10-30
  • 0.6.2 · 2026-10-30
  • 0.6.1 · 2026-10-29
  • 0.6.0 · 2026-10-29
  • 0.5.0 · 2026-10-28
  • 0.4.1 · 2026-10-28
  • 0.4.0 · 2026-10-28
  • 0.3.1 · 2026-10-28
  • 0.3.0 · 2026-10-28
  • 0.2.3 · 2026-10-27
(versions still listed in the registry only)
Registry data
snapshot 2026-11-01
Package and repository
checked 2026-11-01

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. 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.6.3 (published 2026-10-30) → 0.7.1 (published 2026-11-01), between the registry lists of 2026-10-31 and 2026-11-01.

The publisher’s GitHub release note for v0.7.1 (“NovaSolver Studio 0.7.1”), published 2026-11-01.

Read the release note (the publisher’s text, shown as plain text, cut at 4,000 characters)
## NovaSolver Studio 0.7.1

- The third check on a result now says what it checked. Instead of "Verified" it reads "Mesh convergence: checked
  (GCI 1.9%)", "Mesh convergence: not checked", or, for the built-in examples, "Matches reference". These checks show
  that the answer does not depend on the mesh; they do not check the boundary conditions, the material or the design.
  The printed report and the AI tools use the same words. The report also shows the extrapolated value only when the
  three meshes allow one, and labels the GCI as a GCI (it was shown as a difference).
- More results to colour by: stress components (σx … τzx), principal stresses σ1 and σ3, Tresca stress and
  displacement x and y join von Mises stress and displacement in the same list (sections follow). The everyday three
  stay at the top, so the panel is as simple as before.
- STL parts keep their faces. A fillet blends smoothly into its planes, so a rounded plate used to come in as 4 faces
  and a fully rounded block as 1. Flat faces are now separated from fillets and holes: the plate has its 11 faces and
  the block its 6 flat faces, so supports and loads can go on the face you mean.
- Elastoplastic and other nonlinear runs on larger meshes are much faster: they use a direct solver up to about
  120,000 unknowns instead of an iterative one that could stall on a near-collapse tangent (the collapse example's
  fine mesh: from over two hours to 11 minutes).
- Blender and FreeCAD: when Studio was not running, sending a part opened two windows; it now opens one, and FreeCAD
  waits at most a few seconds instead of until Studio has started.
- Fatigue: the life card describes the same point as the safety-factor card (away from a fully fixed face), and the
  mesh study follows that value.
- Contact: a strongly graded mesh no longer hides the element that holds a contact point.
- Hertz contact example: the curved face is a cylinder, so a bearing load can be put on it.
- Validation: 43 of 43 problems with known answers are within tolerance (docs/VALIDATION.en.md).
- Scratch folders used by OpenFOAM on Windows accounts with Japanese or Chinese names are removed with their case,
  and unused ones after a week.

---

## NovaSolver Studio 0.7.1

- 結果の3つ目の判定を、何を確かめたかがわかる表示にしました。「検証済み」ではなく「メッシュ収束:確認済み(GCI 1.9%)」「メッシュ収束:未確認」、付属の例題では「参照解と一致」と表示します。確かめているのは答えがメッシュの粗さに左右されないことで、境界条件の置き方・材料・設計の安全性は確かめていません。レポートと AI 向けの説明も同じ言葉にそろえました。レポートでは、3段階の値から外挿できるときだけ外挿値を出し、GCI を「差」と表示していた誤りも直しました。
- 色分けで見られる量を増やしました。ミーゼス応力・変位に加えて、応力の成分(σx〜τzx)、最大・最小主応力(σ1・σ3)、トレスカ応力、変位 x・y を同じ選択欄から選べます(断面表示も対応)。よく使う3つは上のままなので、画面はこれまでどおりシンプルです。
- STL の部品が CAD に近い面に分かれるようになりました。角丸(フィレット)は平面となめらかにつながるため、角丸の板が4面、全部の辺が丸い箱が1面として読み込まれていました。平面と角丸・穴を分けるようにしたので、板は11面、箱は平らな6面がそれぞれ選べます。
- 塑性などの非線形解析が、大きめのメッシュで大幅に速くなりました。未知数が約12万までは直接法で解きます(崩壊荷重の例題の細かいメッシュで、2時間以上 → 11分)。
- Blender・FreeCAD 連携:Studio が起動していないときに送ると窓が2つ開いていたのを1つにしました。FreeCAD が Studio の起動完了まで待たされることもなくなりました(待つのは数秒以内です)。
- 疲労:寿命のカードが、安全率のカードと同じ点(完全固定した面から離れた位置)の値を示すようにしました。メッシュ収束の確認もその値で行います。
- 接触:大きさの違う要素が混ざったメッシュでも、接触点を含む要素を見落とさないようにしました。
- Hertz 接触の例題:円柱面を円柱として扱うので、軸受荷重をかけられます。
- 検証:答えの分かっている 43 題すべてが許容差内に入りました(docs/VALIDATION.md)。
- 日本語・中国語のユーザー名の Windows で OpenFOAM が使う作業フォルダを、ケースの削除時と、1週間使われなかったときに片付けます。

---

## NovaSolver Studio 0.7.1

- 结果的第三项判定现在说明检查了什么:不再显示“已验证”,而是“网格收敛:已确认(GCI 1.9%)”“网格收敛:未确认”,自带例题则显示“与参考解一致”。这些检查表示结果不随网格粗细变化,并不检查边界条件、材料或设计是否安全。报告和 AI 工具使用相同的表述。报告只在三级网格允许外推时显示外推值,并修正了把 GCI 显示为“差值”的错误。
- 可着色显示的物理量增加:除米塞斯应力和位移外,还可在同一下拉框中选择应力分量(σx…τzx)、最大与最小主应力(σ1、σ3)、Tresca 应力以及 x、y 方向位移(剖面显示同样支持)。常用的三项仍在最前,界面依旧简洁。
- STL 零件可以保留接近 CAD 的面。圆角与平面光滑相接,此前带圆角的板被读成 4 个面,所有边都倒圆的块被读成 1 个面。现在平面与圆角、孔分开:板有 11 个面,块的 6 个平面都可以单独选择。
- 塑性等非线性分析在较大网格上大幅提速:未知数约 12 万以内改用直接法(崩溃载荷例题的细网格:两个多小时 → 11 分钟)。
- Blender 与 FreeCAD:Studio 未运行时发送零件会打开两个窗口,现在只打开一个;FreeCAD 也不再等到 Studio 启动完毕(最多等待几秒)。
- 疲劳:寿命卡片与安全系数卡片描述同一位置(远离完全固定面),网格收敛检查也跟踪该值。
- 接触:网格尺寸差异很大时,也不会漏掉包含接触点的单元。
- Hertz 接触例题:曲面按圆柱面处理,可以施加轴承载荷。
- 验证:43 个已知答案的问题全部在允许误差之内(docs/VALIDATION.zh.md)。
- 用户名为中文或日文的 Windows 上,

The release on GitHub

Source: the official MCP Registry list on 2026-10-31 and on 2026-11-01; release notes from the GitHub Releases API, checked 2026-11-01.

What it is

How do I add it to my client?

Config from the registry entry
  • No config: the MCP bundle is a file to install in a client that supports bundles, not a command.

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.

Does the registry listing match what we found?

Feature #6

The 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 saysWe foundResultSource · date
Repository github.com/novasolver/novasolver-studioOpens publiclymatchesapi.github.com · 2026-11-01

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.novasolver
GitHub owner
an organization (novasolver)
Repository
github.com/novasolver/novasolver-studio
Stars
1
Repository age
0–30 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-01; security policy read from GitHub · 2026-11-01.

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 rating

4 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: not an npm or PyPI package
  • Not ranked by stars: 1 star (ranked from 10)
  • 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
  • Does not applyPackage names its licence with a standard (SPDX) identifierNot an npm or PyPI package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnNot an npm or PyPI package.
  • Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
  • Does not applyNo known critical or high advisory in the package or its dependenciesNot an npm or PyPI package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-01 (security policy 2026-11-01). 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.novasolver/novasolver-studio

Answered from the data above

Who publishes io.github.novasolver/novasolver-studio?

The registry ties the namespace io.github.novasolver to the GitHub account novasolver; only its owner can publish under it. Its linked repository, github.com/novasolver/novasolver-studio, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.novasolver/novasolver-studio safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 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. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.novasolver/novasolver-studio been security tested?

No. It could be started, but has not been tested; we call no server's tools for anything we publish. This is our limit, not the server's.

Does io.github.novasolver/novasolver-studio publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of io.github.novasolver/novasolver-studio?

In github.com/novasolver/novasolver-studio, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A 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 #1

It could be started, but has not been tested; we call no server's tools for anything we publish. 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.

TopicAI-classified
pending: added in the weekly update
listed 2026-11-01; not classified yet
Pricing modelAI-classified
pending: added in the weekly update
the website is not read yet
Programming language
api.github.com · 2026-11-01
Hosting type
registry · 2026-11-01
MCP capability
not checked
not read (no session)
Transport
standard input/output
registry · 2026-11-01
Required credentials
none declared
registry · 2026-11-01 · no declaration is not a guarantee
Package registry
registry · 2026-11-01
Freshness
0–30 days
registry updatedAt · 2026-11-01
Lifecycle status
registry · 2026-11-01
License class
does not apply
package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here
Integrity hash
does not apply
package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here
Signature / provenance
does not apply
package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here
Dependency advisories
not checked
only npm and PyPI packages are audited
Popularity
does not apply
package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here
Publisher signals
owner: an organization · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-11-01
Maintenance
api.github.com · 2026-11-01
Environment
your machine
where it runs, from the hosting type · 2026-11-01

“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.novasolver/novasolver-studio: MCP server record.” Data checked 2026-11-01. https://protocolprobe.com/mcp/servers/io.github.novasolver/novasolver-studio

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

ProtocolProbe: 4 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.novasolver/novasolver-studio)](https://protocolprobe.com/mcp/servers/io.github.novasolver/novasolver-studio)

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.

Write to hello@protocolprobe.com · corrections log · methodology