Is Jaxonomy — hybrid dynamical systems on JAX MCP server safe?

Yes, with the usual care.

A85/100grade A

Passed every safety check we run. Maintained, authenticated, reachable, clean scan.

No critical or high findings in the latest scan.

How Jaxonomy — hybrid dynamical systems on JAX compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 85/100; higher than 70% of 48,255 servers
Tools that change things: 14%; typical: 0%. Fewer write tools means less an agent can break

What its tools let an agent do: 6 read · 1 run or deploy

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

1 medium

Code scan278 source files scanned20/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 6 days ago15/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

mediumeval / new Function usedexec.eval

jaxonomy-3.4.1/jaxonomy/analysis/block_jacobians.py: …cache[port.cache_index] return port.eval(context) def _eval_leaf(leaf, root_con…

Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON