Skip to content

Neumann MCP server

io.github.Kromatic-Innovation/neumannKromatic-Innovationstreamable-httpv0.2.106Scanned

Monte Carlo ranges for uncertain plans: project cost, budget, timeline, capacity, NPV/IRR/payback.

17 tools: 3 can delete or cancel things, 1 do something that can't be undone, 9 change things and 4 only read.

Tools: 3 delete, 1 irreversible, 9 write, 4 read.

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here can delete or cancel things and 1 does something that can't be undone. 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 Neumann MCP server can do

The Neumann MCP server is published by the GitHub account Kromatic-Innovation. It has 17 tools. It can delete or cancel things (3 tools: buy_credits, delete_graph and delete_run), do things that cannot be undone, such as sending, paying or publishing (send_feedback) and create or change data (9 tools: run_monte_carlo_simulation, rank_inputs_by_impact, summarize_outcome_scenarios, check_simulation_model and 5 more). 4 tools only read.

3 tools bring in text other people can write (send_feedback, buy_credits and create_result_share_link); 1 tool can send data out of your system (send_feedback).

The fixed checks matched 19 findings, 2 of them high severity (long-description, annotation-conflict, credentials-mention and model-directed-text). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 10 times since Anlyon Radar first saw them.

Last scanned Nov 21, 2026, version 0.2.106.

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.

17 tools

Deletes or cancels 3Claude Code: deny
  • buy_creditsCharges the payment card saved on the user's account to buy Neumann credits; without a saved card it charges nothing and returns a checkout link instead.Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "charge": a word that usually means money moves, which cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...in the Authorization header as a Bearer credential. No Neumann tool takes an api_key argum..."

      What this check looks for
    Description, as the server wrote it
    Charges the payment card saved on the user's account to buy Neumann credits; without a saved card it charges nothing and returns a checkout link instead. One call buys at most 100 credits ($50.00 at today's price); a request for more is refused and charges nothing. When the user asks for more than that, do not call it yet: tell them the limit and ask how many to buy now. A second purchase needs the user's agreement again. Credits pay for runs once the free runs for the day are used up, or for a model too large to run free. Use this when an account is low on credits and the user has agreed to the purchase; to see the balance and the live price first, call check_account_and_credits. When no card is saved yet, it returns payment_status checkout_required and a checkout_url, which the user opens in a browser to save a card before you call this tool again. It returns the credits bought, the new balance, the payment status and, when a card is needed, the checkout_url. It needs a Neumann account: send your key, or your signed-in token, in the Authorization header as a Bearer credential. No Neumann tool takes an api_key argument. When you are signed in rather than using a key, the sign-in must include billing access (the neumann:billing scope); without it the call is refused with insufficient_scope and charges nothing, and the user signs in again to grant it. Cost: charges the payment card saved on your account for each credit, currently $0.50 per credit (check_account_and_credits shows the live price). It needs an account, and credits are what a run costs once your free runs for the day are gone -- 1 credit for a small run or 5 for a large one.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false
    • title: Buy Neumann credits with your saved card
  • delete_graphDeletes one graph you saved, together with the runs of it.2 findings

    Why it is in this group

    • The name "delete_graph" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • High

      The description contains "do not tell the user", an instruction to keep something from the user.

      Matched text

      description: "...it, through any tool or any request, so do not tell the user it can be recovered. Neumann clears the..."

      What this check looks for
    • Info

      The description mentions "credential".

      Matched text

      description: "...in the Authorization header as a Bearer credential. No Neumann tool takes an api_key argum..."

      What this check looks for
    Description, as the server wrote it
    Deletes one graph you saved, together with the runs of it. Use this when the user has explicitly asked for that model to be removed, and not otherwise. Confirm which one first with list_graphs or get_graph, because the graph_id is the only thing that says which model goes. Deletion is final as soon as this returns: nothing can restore it, through any tool or any request, so do not tell the user it can be recovered. Neumann clears the stored data within 30 days. Deleting the same graph twice changes nothing and does not extend the 30 days. To stop using a graph without removing it, just leave it saved and do not pass its graph_id. It returns the graph_id, what kind of thing was deleted, the time it was deleted and the date it is purged for good. It needs a Neumann account: send your key, or your signed-in token, in the Authorization header as a Bearer credential. No Neumann tool takes an api_key argument. Cost: free -- it debits no credits and spends none of your free daily runs -- but it needs an account; an anonymous caller gets authentication_required.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Delete a model you saved
  • delete_runDeletes one of your own runs -- one result -- and its share link, leaving the model it came from alone.2 findings

    Why it is in this group

    • The name "delete_run" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • High

      The description contains "do not tell the user", an instruction to keep something from the user.

      Matched text

      description: "...it, through any tool or any request, so do not tell the user it can be recovered. Neumann clears the..."

      What this check looks for
    • Info

      The description mentions "credential".

      Matched text

      description: "...in the Authorization header as a Bearer credential. No Neumann tool takes an api_key argum..."

      What this check looks for
    Description, as the server wrote it
    Deletes one of your own runs -- one result -- and its share link, leaving the model it came from alone. It works on any run_id you can read, whether the run came from a model you passed inline or from one you saved; afterwards get_simulation_results can no longer read it. Use this when the user has explicitly asked for that result to be removed, and not otherwise. To remove a saved model and all of its runs at once, use delete_graph. Deletion is final as soon as this returns: nothing can restore it, through any tool or any request, so do not tell the user it can be recovered. Neumann clears the stored data within 30 days. Deleting the same run twice changes nothing and does not extend the 30 days. It returns the run_id, what kind of thing was deleted, the time it was deleted and the date it is purged for good. It needs a Neumann account: send your key, or your signed-in token, in the Authorization header as a Bearer credential. No Neumann tool takes an api_key argument. Cost: free -- it debits no credits and spends none of your free daily runs -- but it needs an account; an anonymous caller gets authentication_required.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Delete a result you saved
Can't be undone 1Claude Code: ask
  • send_feedbackSends a short report about Neumann to the team that builds it.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "send_feedback" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "send_feedback" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Sends a short report about Neumann to the team that builds it. Use this when the user wants to report a problem, a wrong result, a confusing message or a missing feature (including asking you to pass a request or suggestion on to the team), or has agreed to your offer to send one. Send only after the user agrees: when a tool fails, first tell the user what happened and ask, and do not call this tool until they say yes. Good moments to offer: a tool returned an error or a result that looks wrong, the user needed something Neumann could not do, or the work with Neumann is wrapping up and the user might want to say what worked. Offer it as a question, for example: 'Want me to send Neumann's team a short note about this?' The team reads every report. Do not offer after each routine successful call. Put several points in one report: a signed-in account may send 5 per hour and 20 per day, and callers without an account share 60 per hour and 300 per day. Only message is required. Fill in the other fields that apply so the team can act without guessing. Write in your own words. Never include personal data (names, email addresses, company names), the user's own numbers (inputs or results), secrets or keys, or the conversation transcript; describe the task and any wrong result in general terms instead. Add sender_email only if the user wants a reply. If you are signed in, your account id is included. No account is needed. It returns status "sent". Cost: free, with or without an account -- it debits no credits and spends none of your free daily runs.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false
    • title: Send feedback or a bug report to the Neumann team
Changes things 9Claude Code: ask
  • check_simulation_modelChecks a model you hold inline for mistakes, before you save or run it, and lists every problem it finds.No findings

    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.
    Description, as the server wrote it
    Checks a model you hold inline for mistakes, before you save or run it, and lists every problem it finds. It looks for loops with no delay, nodes that are not connected, unknown distributions, missing or invalid distribution parameters, and broken formulas. A loop, including an edge from a node to itself, is allowed and is not an error when at least one edge in it has delay 1 or more. Use this when you have built or edited a model and want to fix it without spending a run. It takes the model inline, not a graph_id: to check a saved model, read it with get_graph and pass what that returns. It does not run or rank anything, and it does not say what a run will cost (use estimate_simulation_size_and_cost for that). It returns is_valid and a list of issues. A draft input with no distribution yet (distribution_type null) is not rejected: it comes back as an issue with severity error naming that input, and is_valid is false, so the model is not ready to run until each such input has a distribution. You do not need this tool to learn that an input with only a low-high guess cannot run: it cannot, and convert_range_to_distribution turns the guess into a distribution. Each issue gives the rule broken, a severity (error, warning or info, where info is only a note), a message, and the node and edge ids involved. If an edge points at a node that does not exist, or the model is over your tier's size limit, you get an error message instead of the list. Cost: free, with or without an account -- it debits no credits and spends none of your free daily runs. Without an account, a model over 1,000 trials or 20 nodes is rejected, also at no cost.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Check a simulation model for errors before running it
  • convert_distribution_to_rangeTurns a distribution's parameters into the low and high ends of the range that holds a chosen share of outcomes, by default the middle 90%.1 finding

    Why it is in this group

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

    Findings

    • Warn

      The server marks "convert_distribution_to_range" 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 "convert_distribution_to_range" says "convert": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Turns a distribution's parameters into the low and high ends of the range that holds a chosen share of outcomes, by default the middle 90%. It also gives the mean, median, mode, standard deviation and any percentiles you ask for. If you give a threshold, it gives the chance of landing below and above it. Use this when you have distribution parameters, from a model or from fermi (a companion forecasting server from Kromatic, the company behind Neumann, whose estimates carry next_steps.simulate.root_node), and want to know what they mean in plain numbers. Its reverse is convert_range_to_distribution, and the range it returns can be passed straight back to it. Values that do not apply, such as a uniform distribution's mode, come back as null with a note explaining why. Cost: free, with or without an account -- it debits no credits and spends none of your free daily runs.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Turn distribution parameters into a min–max range
  • convert_range_to_distributionTurns a low-to-high guess, such as "between 80 and 120, 90% sure", into the exact parameters a model input needs.1 finding

    Why it is in this group

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

    Findings

    • Warn

      The server marks "convert_range_to_distribution" 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 "convert_range_to_distribution" says "convert": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Turns a low-to-high guess, such as "between 80 and 120, 90% sure", into the exact parameters a model input needs. A distribution is the shape of the uncertainty, for example normal (a bell curve), log_normal (skewed and never negative), triangle or uniform. The low and high values are the edges of the range you are that sure of, not hard limits. Use this when you have a rough estimate and need distribution parameters instead of guessing them: an input with only a low-high guess has no distribution yet and cannot run until it has one. You do not need it for a three-point low / most likely / high estimate: that goes straight into the model as a triangle input (min_val, mode_val, max_val), so call run_monte_carlo_simulation directly. Its reverse is convert_distribution_to_range. It returns the distribution type and its parameters, ready to use as a model input's distribution_params. The distribution_type parameter explains which type fits which kind of quantity. Supported types: normal, log_normal, uniform, triangle, beta, gamma, exponential, binomial, discrete_normal, discrete_lognormal, discrete_gamma, constant and bernoulli. Not supported: poisson, categorical, dirichlet, multivariate_normal and constant_array. For beta, give low and high as fractions (2% is 0.02). Cost: free, with or without an account -- it debits no credits and spends none of your free daily runs.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Turn a min–max guess into distribution parameters
  • estimate_simulation_size_and_costPredicts how large a run of a model will be and how many credits it will cost, without running it.No findings

    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.
    Description, as the server wrote it
    Predicts how large a run of a model will be and how many credits it will cost, without running it. Use this before running a large or unfamiliar model, or to check that an account can afford it. It does not look for mistakes; use check_simulation_model for that. It returns the number of trials, time periods, nodes and edges, the estimated peak memory in MB, a complexity score, the size tier (small or large), the credit cost for an account, and a rough run time in seconds for run_monte_carlo_simulation and for rank_inputs_by_impact (which runs the model many times). Runs over about 40 seconds continue in the background and are collected with get_simulation_results. A run is small when trials × nodes × time periods is at most 100,000, and large otherwise. Accounts have no fixed trial or node limit. That cost is what run_monte_carlo_simulation, summarize_outcome_scenarios and rank_inputs_by_impact each charge for this model. A model with mistakes returns an error instead of an estimate. Cost: free, with or without an account -- it debits no credits and spends none of your free daily runs. Without an account, a model over 1,000 trials or 20 nodes is rejected, also at no cost.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Estimate a simulation's cost and size before running it
  • rank_inputs_by_impactRanks a model's uncertain inputs by how much each one moves a chosen outcome, and returns the data for a tornado chart (a bar chart with one horizontal bar per input, the biggest s…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.

    Findings

    • Info

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

      Matched text

      description ends: "...and not given back; a signed-in free run is given back; credits are not charged."

      What this check looks for
    Description, as the server wrote it
    Ranks a model's uncertain inputs by how much each one moves a chosen outcome, and returns the data for a tornado chart (a bar chart with one horizontal bar per input, the biggest swing at the top). This is a one-at-a-time (OAT) sensitivity analysis: it shows how much the outcome changes when each input changes on its own. Every input is held at its median while one input at a time is set to low, middle and high values from its own distribution (by default its 5th, 50th and 95th percentiles). The tool records how the outcome's average changes. Use this when you need to know which assumption matters most, so you know what to research or de-risk first. It returns one entry per input, ranked so rank 1 has the biggest impact. Each entry lists the input values tried, the outcome at each, and an elasticity score. Elasticity is about how many percent the outcome's average moves when the input moves 1 percent, averaged over the values tried. It is never negative: it says how much an input matters, not which way it pushes the outcome; to see the direction, compare the outcome at the input's low and high values. It returns numbers, not an image. Inputs whose distribution produces a list of values are skipped. It always returns a run_id. It runs the model once per input per value tried, so on a big model it can take minutes: if it is not done in about 40 seconds you get status running, and get_simulation_results gives you progress and then the ranking. Cost: it counts as one run per call, however many times it runs the model inside, and it is charged only if the analysis succeeds. Without an account, 1 of your 3 free runs per UTC day, for a model up to 1,000 trials and 20 nodes; that daily allowance is counted per network address and client, so on a shared platform such as Claude.ai or ChatGPT you may find today's free runs already spent by someone else. Signed in with a free Kromatic account, 1 of 10 free runs per UTC day, for a small model (trials x nodes x periods at most 100,000, and within 10,000 trials and 50 nodes), spent before any credits. Beyond that, 1 credit for a small model or 5 for a large one, currently $0.50 per credit; buy_credits tops up. A model that is invalid, or over the limits of the tier you are in, is rejected before running and costs nothing, and so is a saved graph refused with incomplete_model: no credit, no free run, no run recorded. If the analysis fails partway through, it depends on what paid for it: without an account the free run is used up and not given back; a signed-in free run is given back; credits are not charged.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Rank which inputs drive an outcome most (one-at-a-time sensitivity)
  • run_monte_carlo_simulationRuns a Monte Carlo simulation of a model and returns the full range of possible outcomes, not one guessed number.1 finding

    Why it is in this group

    • The name "run_monte_carlo_simulation" says "run": a word for a change.

    Findings

    • Info

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

      Matched text

      description ends: "...ed in on a free run, the free run is given back; on credits, you are not charged."

      What this check looks for
    Description, as the server wrote it
    Runs a Monte Carlo simulation of a model and returns the full range of possible outcomes, not one guessed number. A model is a set of uncertain inputs, the formulas that combine them, and the links between them. The simulation draws random values for every input many times; each draw is a trial, and one call is one run. Use this when you need to know how likely different outcomes are for a plan built on uncertain inputs: a project's total cost or budget (for example from low / most likely / high estimates per line item), a schedule or delivery date, capacity, revenue, or an investment's NPV, IRR or payback. It returns a summary: for each output node (the nodes nothing else depends on, or the ones you list in run_params.output_request.nodes) the mean, the 10th, 50th and 90th percentiles (the value that share of trials fall below), the minimum and maximum in the last time period, and the same per period; plus any metrics you asked for, such as NPV, IRR, payback or the chance of beating a target or budget; and a run_id. Pass that run_id to get_simulation_results for other nodes, periods or percentiles. A run that takes longer than about 40 seconds keeps running in the background: you get status running and a run_id, and get_simulation_results gives you progress and then the result. Cost: without an account, 1 of your 3 free runs per UTC day, for a model up to 1,000 trials and 20 nodes; that daily allowance is counted per network address and client, so on a shared platform such as Claude.ai or ChatGPT you may find today's free runs already spent by someone else. Signed in with a free Kromatic account, 1 of 10 free runs per UTC day, for a small model (trials x nodes x periods at most 100,000, and within 10,000 trials and 50 nodes), spent before any credits. Beyond that -- a larger model, or a day whose free runs are used up -- 1 credit for a small run or 5 for a large one, currently $0.50 per credit; buy_credits tops up. A model that is invalid, or over the limits of the tier you are in, is rejected before running and costs nothing. If it fails mid-run, it depends on the tier: without an account the free run is still used up and not given back; signed in on a free run, the free run is given back; on credits, you are not charged.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Run a Monte Carlo simulation of a model
  • save_graphSaves a model to your Neumann account so you can come back to it instead of describing it again.2 findings

    Why it is in this group

    • The name "save_graph" says "save": a word for a change.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...in the Authorization header as a Bearer credential. No Neumann tool takes an api_key argum..."

      What this check looks for
    • Info

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

      Matched text

      description ends: "...uns -- but it needs an account; an anonymous caller gets authentication_required."

      What this check looks for
    Description, as the server wrote it
    Saves a model to your Neumann account so you can come back to it instead of describing it again. A saved model is called a graph: its uncertain inputs, the formulas that combine them, and the links between them. Use this when the user will revisit this model -- a budget, a plan, a business case they will update -- or when you want to re-analyse it later without resending it; for a one-off question, pass the model inline to run_monte_carlo_simulation and save nothing. Omit graph_id to save a new graph. Pass the graph_id of a graph you saved before to replace that same graph with this version; the earlier versions are kept, so replacing is not losing anything. An input may be saved before it has a distribution, so you can build a draft model over a conversation; a graph with such an input cannot be run or analysed until each input has one. An input can also be given as an estimated range (estimate: worst, best, most likely) with a distribution_type and no params: the save fits the params to the range. Changing a saved input's range re-fits its params, and changing only its params works the range out again. If a range cannot be fitted, the error estimate_fit_failed names the input and nothing at all is saved: not that input, not the rest of the model, and a graph you were replacing keeps its last saved version. So after that error there is nothing new to read back with get_graph; tell the user which range could not be fitted and fix it. It returns the graph_id to use later, the version_id of the version it just stored, the name, and when it was last updated. Use that graph_id with get_graph to read the model back, with rank_inputs_by_impact or summarize_outcome_scenarios in place of an inline graph, and with delete_graph to remove it. run_monte_carlo_simulation does not take a graph_id: read the graph with get_graph and pass it inline. It needs a Neumann account: send your key, or your signed-in token, in the Authorization header as a Bearer credential. No Neumann tool takes an api_key argument. Cost: free -- it debits no credits and spends none of your free daily runs -- but it needs an account; an anonymous caller gets authentication_required.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Save a model to your account
  • summarize_outcome_scenariosReports one outcome's worst, median and best cases from one run of a model.2 findings

    Why it is in this group

    • The name "summarize_outcome_scenarios" says "summarize": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    Findings

    • Info

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

      Matched text

      description ends: "...ed in on a free run, the free run is given back; on credits, you are not charged."

      What this check looks for
    • Warn

      The server marks "summarize_outcome_scenarios" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "summarize_outcome_scenarios" says "summarize": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Reports one outcome's worst, median and best cases from one run of a model. By default, worst is the lowest value in any trial, median is the middle value, and best is the highest value. Those labels assume higher is better. For a cost or a duration, where lower is better, swap them when you tell the user: the scenario labelled worst is the cheapest or fastest case, which is the good outcome, and the one labelled best is the most expensive or slowest. You can ask for other percentiles instead, such as the 10th and 90th, or the 80th for a P80 total. Use this when you want a short worst, typical and best case story. For the range or the odds of outcomes (what range it could land in, how likely something is), use run_monte_carlo_simulation instead; to find which input matters most, use rank_inputs_by_impact. It takes the model inline in graph, or a saved model by graph_id directly, so you do not need get_graph first. If an input in the saved graph has no distribution yet, the call is refused with incomplete_model and costs nothing. It returns each scenario's outcome value and every input's own value at the same percentile of that input's distribution. Those input values are an estimate, not the exact inputs of that trial. It also returns a run_id; a long run comes back as status running, and get_simulation_results gives you progress and then the result. Cost: without an account, 1 of your 3 free runs per UTC day, for a model up to 1,000 trials and 20 nodes; that daily allowance is counted per network address and client, so on a shared platform such as Claude.ai or ChatGPT you may find today's free runs already spent by someone else. Signed in with a free Kromatic account, 1 of 10 free runs per UTC day, for a small model (trials x nodes x periods at most 100,000, and within 10,000 trials and 50 nodes), spent before any credits. Beyond that -- a larger model, or a day whose free runs are used up -- 1 credit for a small run or 5 for a large one, currently $0.50 per credit; buy_credits tops up. A model that is invalid, or over the limits of the tier you are in, is rejected before running and costs nothing. If it fails mid-run, it depends on the tier: without an account the free run is still used up and not given back; signed in on a free run, the free run is given back; on credits, you are not charged.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Summarize worst, median and best outcomes
Only reads 4Show 4 read-only tools
  • check_account_and_creditsShows who Neumann thinks you are and what you can still do: your free runs left today and when they reset, and your credit balance if you have an account.1 finding

    Why it is in this group

    • The description's first verb is "show": a word for reading.

    Findings

    • Info

      The description mentions "Credentials".

      Matched text

      description: "...get_graph without calling list_graphs. Credentials go in the Authorization header as a Bea..."

      What this check looks for
    Description, as the server wrote it
    Shows who Neumann thinks you are and what you can still do: your free runs left today and when they reset, and your credit balance if you have an account. Use this when you need to know, before or after a run, whether the next call will be free or spend credits, how much is left, or whether you are signed in -- and when a run was refused for want of runs or credits, so you can tell the user which it was. There are three tiers. Without an account you get 3 free runs per UTC day; you are recognized by network address and client, so on a hosted platform such as Claude.ai or ChatGPT many callers share one identity and today's free runs may already be spent by someone else. Signed in with a free Kromatic account you get your own 10 free runs per UTC day, spent before any credits. After those, runs cost credits. An account created with POST https://neumann.kromatic.com/api/v1/accounts authenticates you and starts with 5 free credits, but it carries no free daily runs -- only signing in with a Kromatic account does. It returns whether you are anonymous or an account, your account id and status, credit balance, free runs left today with the reset time and the size limits that apply to you, the price of one credit in US dollars, and your last 10 credit transactions. With an account it also returns how many models are saved on your account and the three most recently updated, each with its graph_id, so when the user mentions a saved model you can often go straight to get_graph without calling list_graphs. Credentials go in the Authorization header as a Bearer credential and nowhere else; no Neumann tool takes an api_key argument, and a credential that is not recognized returns an unauthorized error. This tool itself needs no account -- it is how a caller without one finds that out. Setup docs: https://kromatic.com/mcp/neumann. Cost: free, with or without an account -- it debits no credits and spends none of your free daily runs.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Check your account, credits and free runs left
  • get_graphReads one graph you saved earlier, by its graph_id, and returns the whole model in the same shape the run tools accept; an input saved without a distribution comes back with distri…1 finding

    Why it is in this group

    • The name "get_graph" says "get": a word for reading.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...in the Authorization header as a Bearer credential. No Neumann tool takes an api_key argum..."

      What this check looks for
    Description, as the server wrote it
    Reads one graph you saved earlier, by its graph_id, and returns the whole model in the same shape the run tools accept; an input saved without a distribution comes back with distribution_type null and distribution_params {}. Use this when you want to show the user what is in a saved model, edit it before running it again, or run it with run_monte_carlo_simulation, which takes the model inline and not a graph_id. To find a graph_id first, call list_graphs. It returns the graph_id, the name, when it was last updated, and the graph itself: its uncertain inputs with their distributions, the formula nodes, the links between them and the run settings. It reads the model, not any result of running it. After a save_graph error there is nothing new to read: a failed save stores nothing. It needs a Neumann account: send your key, or your signed-in token, in the Authorization header as a Bearer credential. No Neumann tool takes an api_key argument. Cost: free -- it debits no credits and spends none of your free daily runs -- but it needs an account; an anonymous caller gets authentication_required.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Read a model you saved
  • get_simulation_resultsChecks on, and reads, a run you started with run_monte_carlo_simulation, rank_inputs_by_impact or summarize_outcome_scenarios, using its run_id.1 finding

    Why it is in this group

    • The name "get_simulation_results" says "get": a word for reading.

    Findings

    • Info

      The description mentions "Credentials".

      Matched text

      description: "...ns that are not tied to one connection. Credentials go in the Authorization header as a Bea..."

      What this check looks for
    Description, as the server wrote it
    Checks on, and reads, a run you started with run_monte_carlo_simulation, rank_inputs_by_impact or summarize_outcome_scenarios, using its run_id. Use this when a run tool returned status running or queued: it waits up to 30 seconds for the run to finish, then returns its status and percent done, or the finished result, so call it again until status is completed. Use it also to get specific numbers from a finished simulation without running it again (a finished run keeps every node's and edge's statistics for every period): pass nodes (node, edge or metric ids), periods, percentiles such as 0.05 or 0.95, a threshold to get the chance a value is at least or at most some number, or histogram for the distribution's shape. Without those it returns the summary (or the ranking, or the scenarios). A failed run returns its error and is not charged. Only the caller who started the run can read it, and only with the run_id, which is returned to that caller alone. A run started without an account can be read for 24 hours and only from the same network address and client, because a caller without an account is recognized by them; sign in with a free Kromatic account for runs that are not tied to one connection. Credentials go in the Authorization header as a Bearer credential; no Neumann tool takes an api_key argument. Cost: free, with or without an account -- it debits no credits and spends none of your free daily runs.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Get the results of a simulation you already ran
  • list_graphsLists the graphs saved on your Neumann account, the most recently updated first.1 finding

    Why it is in this group

    • The name "list_graphs" says "list": a word for reading.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...in the Authorization header as a Bearer credential. No Neumann tool takes an api_key argum..."

      What this check looks for
    Description, as the server wrote it
    Lists the graphs saved on your Neumann account, the most recently updated first. Use this when the user refers to a saved model that is not among the newest ones check_account_and_credits shows, or to page through all of them; it is how you find the id that get_graph, rank_inputs_by_impact, summarize_outcome_scenarios and delete_graph need. It does not list runs or results -- it lists the models themselves. It returns one entry per graph with its graph_id, name, when it was last updated and how many input and formula nodes it has, plus next_offset when there are more to page through. It needs a Neumann account: send your key, or your signed-in token, in the Authorization header as a Bearer credential. No Neumann tool takes an api_key argument. Cost: free -- it debits no credits and spends none of your free daily runs -- but it needs an account; an anonymous caller gets authentication_required.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: List the models saved on your account

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.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
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 19, 2026, 17:24 UTC, unchanged since Nov 19, 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
13
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://neumann.kromatic.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://api.kromatic.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

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

    Matched text

    https://neumann.kromatic.com/mcp: tools/list returned 17 tools to an anonymous client, including buy_credits (destructive), delete_graph (destructive), delete_run (destructive), send_feedback (irreversible), run_monte_carlo_simulation (write) and 8 more

    What this check looks for

Posture changes

  1. Nov 19, 2026
    • Tools that change things, listed without credentials: 9 to 13
  2. Nov 5, 2026
    • Tools that change things, listed without credentials: 8 to 9
    • RFC 9728 protected resource metadata: none to https://neumann.kromatic.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://api.kromatic.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes

Findings

Matches of fixed checks, with the text they matched.

2 high3 warn14 info
  • The description contains "do not tell the user", an instruction to keep something from the user.

    Matched text

    description: "...it, through any tool or any request, so do not tell the user it can be recovered. Neumann clears the..."

    What this check looks for
  • The description contains "do not tell the user", an instruction to keep something from the user.

    Matched text

    description: "...it, through any tool or any request, so do not tell the user it can be recovered. Neumann clears the..."

    What this check looks for
  • The server marks "summarize_outcome_scenarios" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "summarize_outcome_scenarios" says "summarize": a word for reading.

    What this check looks for
  • The server marks "convert_range_to_distribution" 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 "convert_range_to_distribution" says "convert": a word for a change.

    What this check looks for
  • The server marks "convert_distribution_to_range" 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 "convert_distribution_to_range" says "convert": a word for a change.

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

    Matched text

    description ends: "...ed in on a free run, the free run is given back; on credits, you are not charged."

    What this check looks for
Show 13 more findings

History

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

  1. Tools5 changed.~5 changedView diff
  2. Tools2 changed.~2 changedView diff
  3. Tools8 changed.~8 changedView diff
  4. PostureRemote posture changed. Tools that change things, listed without credentials: 9 -> 13.View diff
    • Tools that change things, listed without credentials: 9 to 13
  5. Tools5 changed.~5 changedView diff
  6. Tools5 changed.~5 changedView diff
  7. Tools2 changed.~2 changedView diff
  8. Tools6 added, 11 changed.+6 added~11 changedView diff
  9. Tools2 changed.~2 changedView diff
  10. PostureRemote posture changed. Tools that change things, listed without credentials: 8 -> 9; RFC 9728 protected resource metadata: none -> https://neumann.kromatic.com/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https:…View diff
    • Tools that change things, listed without credentials: 8 to 9
    • RFC 9728 protected resource metadata: none to https://neumann.kromatic.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://api.kromatic.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes

Install

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

claude mcp add --transport http neumann https://neumann.kromatic.com/mcp
claude mcp add --transport http neumann https://neumann.kromatic.com/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": [
      "mcp__neumann__get_simulation_results",
      "mcp__neumann__check_account_and_credits",
      "mcp__neumann__list_graphs",
      "mcp__neumann__get_graph"
    ],
    "ask": [
      "mcp__neumann__run_monte_carlo_simulation",
      "mcp__neumann__rank_inputs_by_impact",
      "mcp__neumann__summarize_outcome_scenarios",
      "mcp__neumann__check_simulation_model",
      "mcp__neumann__estimate_simulation_size_and_cost",
      "mcp__neumann__convert_range_to_distribution",
      "mcp__neumann__convert_distribution_to_range",
      "mcp__neumann__send_feedback",
      "mcp__neumann__create_result_share_link",
      "mcp__neumann__save_graph"
    ],
    "deny": [
      "mcp__neumann__buy_credits",
      "mcp__neumann__delete_graph",
      "mcp__neumann__delete_run"
    ]
  }
}

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 neumann. Review it before you use it.

Capability tags behind 3 rules
  • mcp__neumann__send_feedback untrusted-input, outbound
  • mcp__neumann__buy_credits untrusted-input
  • mcp__neumann__create_result_share_link untrusted-input

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/io.github.Kromatic-Innovation/neumann/verify?hash=b403f727ebddee8a3eb22630a07f5e41d7a0ba81693654adb1d062d3c56d4a79" | jq -e '.changed == false'

Pinned hash b403f727ebdd, from Nov 21, 2026, 14:18 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.Kromatic-Innovation/neumann/changes.xml

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

Badge

Anlyon Radar badge for io.github.Kromatic-Innovation/neumann
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.Kromatic-Innovation/neumann.svg)](https://radar.anlyon.com/servers/io.github.Kromatic-Innovation/neumann)

Source: MCP Registry. Synced Nov 21, 2026, 14:18 UTC.

Neumann MCP server: questions and answers

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

Is the Neumann MCP server safe?

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

Can the Neumann MCP server delete data?

Yes. 3 tools can delete, cancel or revoke something: buy_credits, delete_graph and delete_run.

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

Yes. 1 tool can send, pay, publish or merge: send_feedback.

What tools does the Neumann MCP server have?

17 tools: 3 destructive, 1 irreversible, 9 write, 4 read. buy_credits, delete_graph, delete_run, send_feedback, run_monte_carlo_simulation, rank_inputs_by_impact, summarize_outcome_scenarios, check_simulation_model and 9 more.

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

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

Does the Neumann MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_feedback.

Has the Neumann MCP server changed its tools?

Yes, 10 times since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.