Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

{
  "mcpServers": {
    "regimen": {
      "type": "http",
      "url": "https://regimen-nu.vercel.app/mcp"
    }
  }
}

claude mcp add --transport http regimen https://regimen-nu.vercel.app/mcp

[mcp_servers.regimen]
url = "https://regimen-nu.vercel.app/mcp"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "regimen": {
      "type": "remote",
      "url": "https://regimen-nu.vercel.app/mcp",
      "enabled": true
    }
  }
}

{
  "mcpServers": {
    "regimen": {
      "type": "http",
      "url": "https://regimen-nu.vercel.app/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=regimen&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vcmVnaW1lbi1udS52ZXJjZWwuYXBwL21jcCJ9"
}

{
  "servers": {
    "regimen": {
      "type": "http",
      "url": "https://regimen-nu.vercel.app/mcp"
    }
  }
}

{
  "mcpServers": {
    "regimen": {
      "httpUrl": "https://regimen-nu.vercel.app/mcp"
    }
  }
}

extensions:
  "regimen":
    enabled: true
    name: "regimen"
    type: streamable_http
    uri: "https://regimen-nu.vercel.app/mcp"
    timeout: 300

Quality 100 / 100strong

protocol100 · weight 25

pass
protocol.modernsupports 2026-07-28 (server/discover)
pass
protocol.statelessanswers without a session
pass
protocol.transportstreamable HTTP
pass
protocol.list_ttltool list is cacheable (ttlMs 3600000)

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene100 · weight 30

pass
tools.descriptionsevery tool has a description
pass
tools.description_lengthdescriptions are concise
pass
tools.schemasevery tool has an object input schema
pass
tools.annotations4 of 4 tools declare readOnlyHint or destructiveHint
pass
tools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
pass
tools.token_costabout 2,576 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability100 · weight 15

pass
stability.changesno tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

4 tools, about 2,576 tokens to load them all · tool set 9178e785bb2b · checked 2026-10-20 10:35 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 94 / 100

provenance90

liveness100

freshness85

hygiene100

+repository +namespace-matches-repo +website +reachable +uptime-100% ~updated-31d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://regimen-nu.vercel.app/mcp` streamable-http	none	yes	100%	273 ms	2026-07-28	2026-10-20

Tools (4)

`regimen_describe_factors`read-only	List the market-condition factors Regimen slices performance by, with units, the upstream operation each is read from, and how it is bucketed. Call this when you need to know which factor keys exist or how to explain a bucket to a user. Takes no arguments, reaches no network, never changes.
`regimen_evaluate_track_record`read-only	Answer whether a trading strategy’s measured performance is distinguishable from luck. Returns the Probabilistic Sharpe Ratio (the probability the true Sharpe beats a benchmark, corrected for sample length, skew and fat tails), a bootstrap confidence interval, and the Minimum Track Record Length — how long the record would have to run before the claim could be made at all. Use this whenever someone quotes a Sharpe ratio, a win rate or a return and you need to know whether the number means anything. It will frequently say the evidence is too thin; that is the intended answer, not a failure.
`regimen_regime_map`read-only	Break a strategy’s returns down by the market conditions that held on each date — volatility, funding, open interest, positioning, sentiment, trend state — and report performance per bucket. Each factor also gets a permutation test: the observed best-to-worst spread is compared against spreads produced by randomly reshuffling the regime labels, so a flattering subset cannot pass itself off as a regime effect. Use this after regimen_evaluate_track_record when you need to know WHERE an edge comes from, or whether it is a bet on conditions that could end.
`regimen_self_attack`read-only	Run Regimen’s own analysis against controls whose answer is known in advance: the strategy’s returns with the edge mathematically removed, and a simulated population of strategies with no edge at all. Returns whether the engine correctly found nothing in them, and where the real strategy’s confidence sits among pure-luck strategies of the same length and volatility. Use this when a user is entitled to ask why they should believe the verdict, or before quoting a result as evidence.

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "io.github.RaYYeR220/regimen",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://regimen-nu.vercel.app/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.0.0",
  "repository": {
    "url": "https://github.com/RaYYeR220/regimen",
    "source": "github"
  },
  "websiteUrl": "https://regimen-nu.vercel.app",
  "description": "Tells you whether a trading strategy's edge is distinguishable from luck."
}