Skip to content

Occam MCP server

fit.occam/occamoccam.fitstreamable-httpv0.1.1Scanned

Finds the simplest equation consistent with your data. SINDy and PySR symbolic regression via MCP.

4 tools: 4 change things.

Tools: 0 delete, 0 irreversible, 4 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 9 findings

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Occam MCP server can do

The Occam MCP server is published by occam.fit, a domain the MCP Registry verified. It has 4 tools. It can create or change data (4 tools: feature_request, sindy_run, pysr_run and pysr_uncertainty), but cannot delete data. None of its tools only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 9 findings (credentials-mention, long-description and annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 15, 2026, version 0.1.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 4Claude Code: ask
  • feature_requestRequest a feature that Occam doesn't support yet.No findings

    Why it is in this group

    • The name "feature_request" says "request": a word for a change.
    Description, as the server wrote it
    Request a feature that Occam doesn't support yet. Use this when you need a capability that Occam doesn't currently offer. Requests are logged and used to prioritize development. Rate limit: 5 requests/hour per IP, 50/hour global — stricter than the compute tools' 10/hour to prevent log flooding. Descriptions longer than 500 characters are truncated.

    Annotations the server declares

    • title: Request a Feature
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • pysr_runEvolutionary Symbolic Regression (PySR).4 findings

    Why it is in this group

    • The name "pysr_run" says "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...requests; paid requests without a valid credential receive a `payment_required` result..."

      What this check looks for
    • Info

      The input schema at properties.payment.description mentions "credential".

      Matched text

      inputSchema.properties.payment.description: "Payment credential. Accepts either a JSON object or a JSON..."

      What this check looks for
    • Info

      The description is 3,202 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...nds=15 Policy: occam://privacy-policy — Citation: occam://citation-info"

      What this check looks for
    • Warn

      The server marks "pysr_run" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "pysr_run" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Evolutionary Symbolic Regression (PySR). Discovers algebraic equations y = f(x1, x2, ...) from feature/target data. Returns a Pareto front ranked by the complexity/accuracy tradeoff. Slower than SINDy (10-60s); searches often terminate early on convergence. For differential equations from time series, use sindy_run instead. Pricing: free tier up to 100 rows × 8 features, 60s timeout. Beyond that, $0.25 + $0.03 per 100 extra rows + $0.01 per extra feature squared, timeout up to 300s (5 min), via x402 (USDC on Base) or MPP/Stripe. MPP/Stripe adds a flat $0.35 per-transaction fee (Stripe processing), so the MPP challenge amount in a `payment_required` response is $0.35 higher than the x402 amount for the same base price; x402 gets the lower rate. Omit `payment` for free-tier requests; paid requests without a valid credential receive a `payment_required` result with pricing and accepted schemes. Full pricing: occam://pricing Advisory limits: jobs over 50,000 rows or 20 features are accepted but may not converge; response carries a top-level `warning`. Operators: fixed supported set only — custom operators (e.g. 'inv(x) = 1/x') are rejected. Unary: sin, cos, tan, exp, log, log2, log10, sqrt, abs, sinh, cosh, tanh. Binary: +, -, *, /, ^. See also prompt `supported_operators`. Loss metric: `loss` (in `pareto_front[].loss` and `best_loss`) is mean squared error between model prediction and `y` on the full training set — not RMSE, and not normalized by Var(y). A threshold appropriate for one dataset scales with y's magnitude, so set `loss_threshold` with that in mind (e.g. for y values near 1.0, 1e-6 is a tight fit; for y near 1000, the equivalent is 1.0). Early termination: set `loss_threshold` to stop at your noise floor. The server also stops when the search stalls (<1% improvement in the last third of the budget); disable with `stall_detection=false`. Response `stop_reason` is one of: loss_threshold, stall, timeout, natural. If `feature_names` is supplied, its length must equal the number of columns in `X`; a mismatch is rejected with a validation error. Follow-up: call `pysr_uncertainty` with a chosen expression and the same dataset for bootstrap confidence intervals on its fit constants and optional prediction bands. Rate limit: 10 requests/hour per IP, 200/hour global, max queue depth 20 (shared with sindy_run and pysr_uncertainty). Response (success) includes `pareto_front[]` (each with `complexity`, `loss`, `expression`, `expression_latex`), `best_expression`, `best_expression_latex`, `best_loss`, `best_complexity`, `stop_reason`, `elapsed_seconds`, `queue_seconds` (>0 = server saturated; use as backoff signal), optional `warning`, optional `_meta` (MPP receipt). Full response and payment-required schemas: occam://tool-schemas Example request: X=[[0.0], [1.0], [2.0], [3.0], [4.0]], y=[1.0, 3.0, 5.0, 7.0, 9.0], feature_names=["x"], max_complexity=10, timeout_seconds=15 Policy: occam://privacy-policy — Citation: occam://citation-info

    Annotations the server declares

    • title: Run PySR
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • pysr_uncertaintyBootstrap confidence intervals for the numeric constants of a frozen expression, plus optional prediction bands on an x-grid.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The description is 2,377 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...00/hour global, max queue depth 20 (shared with sindy_run and pysr_run)."

      What this check looks for
    Description, as the server wrote it
    Bootstrap confidence intervals for the numeric constants of a frozen expression, plus optional prediction bands on an x-grid. Typical flow: call pysr_run, pick an expression from the response (best_expression or a pareto_front entry), pass it back here with the same dataset to get CIs on its fit constants. Returns frequentist bootstrap confidence intervals, not Bayesian credible intervals — posterior inference over expression structures is an open research problem. This tool freezes the expression chosen by the caller and bootstraps only its numeric constants; uncertainty about *which* expression is correct is not quantified. Bootstrap semantics: - If y_sigma is supplied, uses parametric bootstrap (y_b = y + Normal(0, y_sigma)). CI reflects user-stated measurement noise. - Otherwise uses residual bootstrap: fit once, resample residuals. CI reflects estimated-from-residuals noise. Only Float constants in the expression become free parameters. Integers stay structural (the 2 in x**2 is a function-class choice, not a fit constant). Expressions with no Float constants (e.g. "x + y") will be rejected with a validation error. Expression grammar: the `expression` string is parsed by sympy. Accepted operators are the same set pysr_run emits: unary `sin`, `cos`, `tan`, `exp`, `log`, `log2`, `log10`, `sqrt`, `abs`, `sinh`, `cosh`, `tanh`; binary `+`, `-`, `*`, `/`, `^` (or `**`). Whitespace and parenthesization are free. Every free symbol in the expression must correspond to an entry in `feature_names` — an unrecognised symbol is silently treated as a fresh sympy Symbol and the fit will fail downstream rather than reject early. Parse failures (syntax errors, malformed operators) surface as tool errors. If `feature_names` is supplied, its length must equal the number of columns in `X`; a mismatch is rejected with a validation error. Pricing: always free, regardless of dataset size. This tool has no `payment` parameter and is never subject to the x402/Stripe gate. Large bootstrap jobs still count against the shared rate limit below, so budget `n_resamples` accordingly. Rate limit: 10 requests/hour per IP, 200/hour global, max queue depth 20 (shared with sindy_run and pysr_run).

    Annotations the server declares

    • title: Bootstrap uncertainty for a PySR expression
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • sindy_runSparse Identification of Nonlinear Dynamics (SINDy).4 findings

    Why it is in this group

    • The name "sindy_run" says "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...requests; paid requests without a valid credential receive a `payment_required` result..."

      What this check looks for
    • Info

      The input schema at properties.payment.description mentions "credential".

      Matched text

      inputSchema.properties.payment.description: "Payment credential. Accepts either a JSON object or a JSON..."

      What this check looks for
    • Info

      The description is 2,178 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...ld=0.1 Policy: occam://privacy-policy — Citation: occam://citation-info"

      What this check looks for
    • Warn

      The server marks "sindy_run" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "sindy_run" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Sparse Identification of Nonlinear Dynamics (SINDy). Recovers governing differential equations (dx/dt = f(x)) from time series data. Returns human-readable sparse expressions. Fast (seconds). For algebraic y = f(x) relationships without time structure, use pysr_run instead. Pricing: free tier up to 100 rows and 8 variables. Beyond that, $0.05 + $0.01 per 100 extra rows + $0.01 per extra variable squared, via x402 (USDC on Base) or MPP/Stripe. MPP/Stripe adds a flat $0.35 per-transaction fee (Stripe processing), so the MPP challenge amount in a `payment_required` response is $0.35 higher than the x402 amount for the same base price; x402 gets the lower rate. Omit `payment` for free-tier requests; paid requests without a valid credential receive a `payment_required` result with pricing and accepted schemes. Full pricing table as structured JSON: occam://pricing Advisory limits: jobs over 500,000 rows or 50 variables are accepted but may not converge within the time budget; the response carries a top-level `warning` the agent should surface and treat as tentative. If `feature_names` is supplied, its length must equal the number of data columns; a mismatch is rejected with a validation error. Rate limit: 10 requests/hour per IP, 200/hour global, max queue depth 20 (shared with pysr_run and pysr_uncertainty). Response (success) includes `equations[]` (each with `variable`, `equation`, `expression`, `expression_latex`, `r2`), `library_terms`, `nonzero_terms`, `elapsed_seconds`, `canonical_match` (dict with `system`, `form`, `variable_map`, `parameter_map`, `confidence` if the discovered system matches one of Lorenz / Lotka-Volterra / Van der Pol / Duffing; `null` otherwise), optional `warning`, optional `_meta` (MPP receipt on paid calls). Full response and payment-required schemas: occam://tool-schemas Example request: data=[[1.0, 0.0], [0.95, -0.31], [0.81, -0.59]], t=[0.0, 0.1, 0.2], feature_names=["x", "y"], poly_degree=2, threshold=0.1 Policy: occam://privacy-policy — Citation: occam://citation-info

    Annotations the server declares

    • title: Run SINDy
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:54 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://occam.fit/mcp/: tools/list returned 4 tools to an anonymous client, including feature_request (write), sindy_run (write), pysr_run (write), pysr_uncertainty (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 warn7 info
  • The server marks "sindy_run" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "sindy_run" says "run": a word for a change.

    What this check looks for
  • The server marks "pysr_run" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "pysr_run" says "run": a word for a change.

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "...requests; paid requests without a valid credential receive a `payment_required` result..."

    What this check looks for
  • The input schema at properties.payment.description mentions "credential".

    Matched text

    inputSchema.properties.payment.description: "Payment credential. Accepts either a JSON object or a JSON..."

    What this check looks for
  • The description is 2,178 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...ld=0.1 Policy: occam://privacy-policy — Citation: occam://citation-info"

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "...requests; paid requests without a valid credential receive a `payment_required` result..."

    What this check looks for
Show 3 more findings
  • The input schema at properties.payment.description mentions "credential".

    Matched text

    inputSchema.properties.payment.description: "Payment credential. Accepts either a JSON object or a JSON..."

    What this check looks for
  • The description is 3,202 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...nds=15 Policy: occam://privacy-policy — Citation: occam://citation-info"

    What this check looks for
  • The description is 2,377 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...00/hour global, max queue depth 20 (shared with sindy_run and pysr_run)."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http occam https://occam.fit/mcp/
claude mcp add --transport http occam https://occam.fit/mcp/

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__occam__feature_request",
      "mcp__occam__sindy_run",
      "mcp__occam__pysr_run",
      "mcp__occam__pysr_uncertainty"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as occam. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/fit.occam/occam/verify?hash=51d4ecaefdbd5730788adccad0560d28a933db2da952e84cea149a34044339d3" | jq -e '.changed == false'

Pinned hash 51d4ecaefdbd, from Nov 15, 2026, 09:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/fit.occam/occam/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for fit.occam/occam
[![Anlyon Radar](https://radar.anlyon.com/badge/fit.occam/occam.svg)](https://radar.anlyon.com/servers/fit.occam/occam)

Source: MCP Registry. Synced Oct 21, 2026, 18:12 UTC.

Occam MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Occam MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 4 of which can change, send or delete something, and 9 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Occam MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Occam MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Occam MCP server have?

4 tools: 4 write. feature_request, sindy_run, pysr_run and pysr_uncertainty.

Does the Occam MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Occam MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Occam MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.