# nTop vs SimScale (slim)

> SimScale and nTop score within a point of each other for cad simulate, 41 and 40.2 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/ntop-vs-simscale.md (~4,300 tokens) · this version ~2,880 tokens · JSON https://www.anchorterminal.com/compare/ntop-vs-simscale.json · canonical https://www.anchorterminal.com/compare/ntop-vs-simscale
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-03
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

SimScale and nTop score within a point of each other on agent readiness, 41 (E) and 40.2 (E). nTop leads on reliability, agent ergonomics and maintenance & community. Both do cad simulate.

- nTop: E 40.2, rank #1214 of 1349 · https://www.anchorterminal.com/tools/ntop.min.md
- SimScale: E 41, rank #1203 of 1349 · https://www.anchorterminal.com/tools/simscale.min.md
- nTop, good for An engineering team that already runs nTop and wants an agent to drive design-of-experiments loops over a notebook or read exported implicit bodies in Python. Ahead on Reliability, 38 against 15; Agent ergonomics, 60 against 55; Maintenance & community, 45 against 33. Also A hosted endpoint, with nothing to install.
- SimScale, good for An enterprise engineering team that wants an agent to automate CFD, FEA or thermal studies on a platform it already licenses, with a sandbox for development. Ahead on Schema & documentation, 71 against 61; Security & auth, 44 against 26; Payments & pricing, 10 against 0; Transparency & trust, 65 against 51.

| Category | nTop | SimScale |
| --- | --- | --- |
| Reliability (16%) | 38 | 15 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 61 | 71 |
| Agent ergonomics (13%) | 60 | 55 |
| Security & auth (14%) | 26 | 44 |
| Payments & pricing (10%) | 0 | 10 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 45 | 33 |
| Transparency & trust (7%) | 51 | 65 |

| Fact (where they differ) | nTop | SimScale |
| --- | --- | --- |
| Kind | SDK + MCP | HTTP API |
| Vendor | nTopology Inc. | SimScale GmbH |
| Hosted endpoint | `https://docs.ntop.com/mcp` | no (local only) |
| Transports | Streamable HTTP |  |
| Auth | OAuth or key | API key |
| Tools exposed | 2 | 0 |
| Read-only variant documented | yes | no |
| Last release | none | 2026-03-03 |
| Terms last updated | 2026-02-01 | no date given |
| Privacy policy last updated | 2026-02-01 | no date given |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | yes | not found in the text |

Why the edge:
- Reliability, nTop +23: nTop 38 (Read with the local-software lines, since ntopcl and the Core package run on the owner's machine. ntopcl ships inside the nTop Windows installer and the Core package states Python 3.10 or later on Windows and Linux, but both come from app.ntop.com behind a login, not a public package index (12 of 20). No public CI or test suite (0). No public issue tracker; the knowledge base has articles on debugging Automate errors and the 6.3 notes record ntopcl rejecting duplicate input names, which is all the crash record we could read (8 of 25). Release notes per version call out behaviour changes such as unique block names in 6.3, and the Core package warns that breaking changes may land between any two versions, with no semver statement (8 of 15). nTop 6.x is a released product; nTop Core is beta (10 of 15). 12 + 0 + 8 + 8 + 10 = 38.); SimScale 15 (Read with the hosted lines on api.simscale.com. No status page, since status.simscale.com has no DNS record and none is linked from the site, the docs hub or the API document (0). No readable incident history (5). No rate limit with a number; the terms reserve the right to impose rate or traffic limits and the v0 document mentions a 429 response once (0). No Retry-After, backoff guidance or idempotency keys; runs can be cancelled (0). No SLA, and the terms say SimScale cannot warrant uninterrupted availability with Free plans carrying no availability obligation (0). /v0 is the generally available version; /v1 is in beta (10). 0 + 5 + 0 + 0 + 0 + 10 = 15.)
- Security & auth, SimScale +18: nTop 26 (Licence credentials rather than tokens, since ntopcl signs in with a username and password on the command line or a FlexNet server address, with no scoped, revocable or expiring key (8 of 30). The Run Command block has Prompt per File, Prompt per Block and Disallow All settings, which is the only approval control found; the docs MCP server is read-only (10 of 20). The docs server returns nTop's own documentation and ntopcl returns geometry, so little untrusted content reaches the model; no guidance was found (8 of 15). No audit log or per-call record found (0 of 15). No security.txt (404), disclosure policy, bug bounty, certification or advisories found on ntop.com or docs.ntop.com (0 of 20). 8 + 10 + 8 + 0 + 0 = 26.); SimScale 44 (One API key per user in the X-API-KEY header, with no scopes, documented expiry, rotation or revocation; the SDK reads it from an environment variable (10 of 30). Project and space permission endpoints exist and the sandbox cannot change data, but no read-only key or confirmation step for deletes was found (8 of 20). The API returns the owner's own geometry and results and no third-party content, so there is little untrusted content to inject (10 of 15). No audit log or per-call visibility found on the pages read (0 of 15). SOC 2 Type II by Prescient Assurance, a public Intigriti bug bounty with the API in scope, security.txt and AES encryption (16 of 20). 10 + 8 + 10 + 0 + 16 = 44.)
- Transparency & trust, SimScale +14: nTop 51 (Closed software under an EULA last updated February 2026 that names nTopology Inc. and New York law (15). The privacy policy of February 2026 names the controller and US hosting, keeps data as long as needed with no periods, names no subprocessors, and the EULA says usage data is collected to run and improve the products; the statements agree but say little (12 of 30). No deprecation policy; the Core package says only that breaking changes may occur (4 of 20). The EULA discloses usage data collection and the licensing page says the desktop connects to the cloud for analytics, with no opt-out found (6 of 20). 15 + 12 + 4 + 6 = 37.); SimScale 65 (Closed service with clear terms (version July 2023) naming SimScale GmbH under German law (15). The data privacy statement (November 2025) gives retention periods for site data, names subprocessors with locations and the LLM providers used on platform content, and the terms give SimScale a licence over paid-plan content for improving the services; the statement's section 14 still says July 2023, and neither document says whether platform content trains models (20 of 30). v1 is announced as beta with a migration guide and v0 stays, but no deprecation policy or dated notices were found (8 of 20). Subprocessors and data locations are disclosed in detail, with production in AWS EU regions (18 of 20). 15 + 20 + 8 + 18 = 61.)
- Maintenance & community, nTop +12: nTop 45 (Read for closed software with a docs site. The newest release notes are for nTop 6.3, undated; the docs sitemap last modified the 6.1 page on 21 September 2026 and the Core package page on 19 October 2026, so a change within 90 days is likely but no release date was read (20 of 30). Four versions (6.0 to 6.3) are documented and the 6.0 and 6.1 pages changed in September, but without dates we can't count three releases in 90 days (12 of 20). support@ntop.com, a community site that renders only a loading screen, and a feedback tool on the docs server; no public issues or reply times (8 of 25). No entry in the official MCP registry for the docs server, and the only SDK is a beta Python package behind a login (5 of 15). No CI, package index or dependency data to read (0 of 10). 20 + 12 + 8 + 5 + 0 = 45.); SimScale 33 (Read for a closed service with open SDK sources. The Python SDK's newest release is 19.1.0 of 3 March 2026, 245 days before the check, and the v1 document carries no date (5 of 30, for a change in the window being likely from the v1 beta but unproven). Ten SDK releases from February 2025 to March 2026 and none since (0 of 20). api@simscale.com, support@simscale.com and a community forum; response times were not tested and the SDK repository has no issue activity we could read (10 of 15). Official Python and C# SDKs, with v1 editions, generated from the document (15). The SDK repository has no CI workflow and pins the document version at 0.0.0 (3 of 10). 5 + 0 + 10 + 15 + 3 = 33.)
- Schema & documentation, SimScale +10: nTop 61 (ntopcl writes JSON input and output templates from a notebook with `-t`, and the Core Python API is fully typed, but there is no OpenAPI or schema document for ntopcl's own flags, which the docs say to print by running it (12 of 25). docs.ntop.com serves every article as Markdown with a .md suffix and a hosted docs MCP server (10). The API reference states the purpose of each Core function with parameter notes and the Automate lessons say what each helper does; ntopcl's full option list is not documented on the pages read (12 of 20). Core inputs are typed NumPy arrays with keyword-only parameters, builtin exceptions and unit conventions stated (10 of 15). Python examples for Core and Automate, a sample script in a zip, and a security error page; no error catalogue for ntopcl (9 of 15). Release notes per version without dates, no changelog for the Core package (8 of 15). 12 + 10 + 12 + 10 + 9 + 8 = 61.); SimScale 71 (Public OpenAPI 3.0.3 documents for /v0 (98 operations) and /v1 (163 operations), with the simulation and meshing schema versions selectable by query parameter (25). No llms.txt and no Markdown docs; the API docs are Swagger UI and script-rendered pages (0). The introduction explains the sandbox, versioning and Workbench compatibility, and operations carry one-line summaries, but 10 of the 98 v0 operations have no description and the guides for v1 rendered empty (12 of 20). 2,112 schemas with 355 enum lists, required fields and a typed security scheme (13 of 15). The sandbox answers every endpoint with example data, which stands in for examples, and responses are typed for 400, 403, 404, 409, 422 and 429 (11 of 15). Path versions v0 and v1 with a migration guide and changelog for v1, and dated SDK releases, though the changelog page itself rendered empty (10 of 15). 25 + 0 + 12 + 13 + 11 + 10 = 71.)
- Payments & pricing, SimScale +10: nTop 0 (Read with the paid-software rule, since nothing an agent would run is free. No x402, MPP or L402 (0). No price is published anywhere we read; licences are quoted by sales (0). No free tier or trial terms found; educational licences exist for students (0). A person buys a per-user licence, signs in at app.ntop.com and installs nTop; nothing is obtainable by an agent alone (0). 0 + 0 + 0 + 0 = 0.); SimScale 10 (No x402, MPP or L402 (0). No price is published; Mechanical, Professional and Enterprise are on request and the Community plan carries no API (0). The sandbox with its fixed public key lets an agent exercise every endpoint without an account or card, though it runs nothing, and the free Community plan has no API; read as a partial free route (10 of 20). An API key comes with an Enterprise contract arranged by people (0). 0 + 0 + 10 + 0 = 10.)