
simulate-monte-carlo
io.github.encodiPublished by GitHub account encodiv1.0.0Updated Oct 25, 2026
Real Monte Carlo simulation of a compound event/conditional probability. Paid via x402.
Overview
Remote MCP server that estimates compound or conditional probabilities by actually running a Monte Carlo simulation with declared random variables.
- What you can do
- Declare named random variables (uniform, normal, bernoulli, binomial, poisson, exponential, discrete) with an event expression and an optional condition expression to get P(event | condition) by rejection sampling, with real sampling and counting rather than a model guess. Reproduce a run by passing back the returned seed. Expressions are evaluated by a restricted interpreter limited to arithmetic, comparisons, boolean logic, parentheses and min/max/abs, with no code execution path. Each call is self-contained with no database or persistent state.
- When to use it
- Useful when you want a quick numeric probability estimate for a compound or conditional event, such as dice sums or simple risk scenarios, instead of an LLM's guess. Suited to exploratory estimates rather than high-stakes statistical work.
- Requirements
- Remote endpoint over streamable HTTP; no account or API key declared. Each tool call is paid in USDC on Base mainnet via x402, so a client able to pay is needed. Limits apply: max 10 variables, 100 to 100,000 trials, 500-character expressions, and a combined sampling budget.
Installation
In SourceWeft
- Open simulate-monte-carlo in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.encodi%2Fsimulate-monte-carlo/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"simulate-monte-carlo": {
"type": "http",
"url": "https://simulate-monte-carlo.encodari.workers.dev/mcp"
}
}
}README
simulate-monte-carlo
[simulate-monte-carlo MCP server]
Remote MCP server (Cloudflare Workers) with one tool that estimates a compound event or conditional probability by actually running a Monte Carlo simulation:
simulate_monte_carlo— declare named random variables (uniform,normal,bernoulli,binomial,poisson,exponential,discrete), aneventboolean expression over those names (e.g."a > 0.5 && b == 1"), and an optionalconditionexpression to get a conditional probabilityP(event | condition)via rejection sampling. Real random sampling and real counting — not a model guess about what the probability should be.
No database, no persistent state: each call builds a fresh McpServer (see createServer() in src/index.ts) and is self-contained. The PRNG is seedable (mulberry32): pass the seed returned in a previous response to reproduce the exact same result.
Why a hand-written expression interpreter, not eval
event/condition are arbitrary caller-supplied strings. Running them through eval/Function would mean executing untrusted code inside the Worker. Instead, src/tools/monteCarlo.ts includes a small tokenizer + recursive-descent parser + AST interpreter that only understands numbers, declared variable names, arithmetic (+ - * /), comparisons (< <= > >= == !=), boolean logic (&& || !), parentheses, and a three-function whitelist (min, max, abs). There is no code execution path — the interpreter can't do anything beyond evaluate that narrow grammar.
Billing (x402)
Charges per call via x402 — real USDC payment on Base mainnet, against the Coinbase Developer Platform (CDP) facilitator. The payment travels inside the MCP JSON-RPC itself (_meta), not as an HTTP header; see src/payments.ts.
An unpaid tools/call returns isError: true with the accepts (network, amount, payTo) the client needs to pay and retry — not an unexplained exception.
Structure
Resource limits
Set from the start, not bolted on after: max 10 variables, 100–100,000 trials (default 10,000), 500-character expressions, binomial n ≤ 1,000, poisson lambda ≤ 1,000, and a discrete-outcome cap of 20. On top of the individual caps, a combined sampling-budget check (trials × sum(per-variable cost) ≤ 5,000,000) rejects combinations that would be individually within limits but jointly too expensive — e.g. 100,000 trials against a binomial(n=1000) variable.
Running it locally
⚠️ Note on wrangler dev: the real Cloudflare Workers runtime (workerd) requires macOS 13.5+. If your Mac has an older version, wrangler dev (and npm run dev) will fail. This project includes a plain-Node shim that runs the exact same fetch() handler without needing workerd.
1. Install dependencies
2. Run the unit tests
3a. If your wrangler dev works (macOS 13.5+, Linux, Windows)
3b. If wrangler dev fails because of the macOS version
Starts at http://localhost:8787/mcp, reading CDP credentials from ~/.mcp-tools-factory-credentials.env (shared across all tools in this factory).
4. Test with curl
Responses come as Server-Sent Events (event: message + data: {...}); the data: line is the usual JSON-RPC response.
Deploy and listings
Deployed at https://simulate-monte-carlo.encodari.workers.dev/mcp (Cloudflare Workers). Published on the official MCP registry, Smithery, mcp.so, and with an open PR to awesome-mcp-servers.
What it doesn't do (yet)
- Charges on Base mainnet with real money. To switch back to testnet (Base Sepolia,
eip155:84532) during development, changeNETWORKinsrc/payments.ts. - No database or persistent state between calls (beyond the billing config, cached in memory per isolate — see
src/payments.ts). - The 95% confidence interval uses the normal (Wald) approximation, which is imprecise near probabilities close to 0 or 1 — good enough for a quick estimate, not a substitute for exact binomial confidence intervals in high-stakes use.
Source: README.md at commit 1347a3f
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts