Skip to content
Orchis logo

Orchis

Publishes Chris Stockslager's MCP servers, a self-hosted Git forge with pull requests, and a Linux kernel module for shared GPU VRAM.

At a glanceswept 2026-10-12

≈ 1visits/mo

Little sign of use · estimate, read 2026-10-12

  • Orchis1
  • #1 PayPal8.2M
  • Finance median23
For
Teams and individuals who need MCP servers, agentic tooling, or Linux infrastructure built or audited
Price
Price not read
Activity
Activity not read yet
Company
Domain since 2025domain registered
Runs as
Self-hosted
What people do with it
  • audit an MCP server setup for security
  • review architecture before shipping a service
  • code review a service before release
The companyeach fact with its source · read 2026-10-14
  • Domain since2025domain registered
How a program reaches itfound, not claimed · read 2026-10-13
  • MCP serverai.orchis/nimrodverified in the MCP registry
  • Stateanswers, requires sign-inchecked 2026-10-13
  • Address to connectnimrod.orchis.ai/mcp
  • MCP docskicad.orchis.aithe vendor's page ↗

MCP server details →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Most used in Financeby use, among tools still maintained — this tool shares no tags yet

Figure and bar: visits/mo, estimate · year: online since

All Finance tools →

Questions this page answers
  • What is Orchis?

    Publishes Chris Stockslager's MCP servers, a self-hosted Git forge with pull requests, and a Linux kernel module for shared GPU VRAM. It is listed in the Atlas under Finance.

  • Who is Orchis for?

    Teams and individuals who need MCP servers, agentic tooling, or Linux infrastructure built or audited

  • Do people use Orchis?

    Little sign of use: ≈ 1 visits/mo · estimate, 2026-10.

Not quite it? Describe the job

beta

Five tools from the Atlas that fit it, each judged against what you wrote.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.