mcpbeat Sign in

OODS Foundry MCP Server

by oods-foundry Your server? Claim it
answering

OODS Foundry is answering right now. Last checked 12 min ago. 281 installs a week from npm. It exposes 9 tools. Last commit 11 Oct 2026.

OODS Foundry is an object-oriented design system that extends the one you already have.

Installs per day peak 640 · avg 190 · -70% w/w
a month agotoday
Uptime history 22 days of history · worst day 99%
22 days agonow
100.0%
Uptime 24h
91 of 91 checks
9
Tools
read from the server
345 ms
Response time
average over 24h
281
Installs / week
npm and PyPI

What changed 69

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 5 October 2026. No other catalogue keeps this.

11 Oct 4 tools changed the parameters they ask for artifact_certify, catalog_list, structured_data_fetch and 1 more
11 Oct 2 tool descriptions were rewritten catalog_list, structured_data_fetch
11 Oct a tool changed version
9 Oct 9 tools changed the parameters they ask for15 times that day artifact_certify, catalog_list, design_preview and 6 more
9 Oct 9 tool descriptions were rewritten artifact_certify, catalog_list, design_preview and 6 more
9 Oct a tool changed version2 times that day
8 Oct 8 tool descriptions were rewritten9 times that day artifact_certify, catalog_list, design_preview and 5 more
8 Oct 7 tools changed the parameters they ask for artifact_certify, catalog_list, design_preview and 4 more
8 Oct a tool changed version2 times that day
7 Oct a tool changed version2 times that day
and 26 more, back to 5 October 2026

What the code does

We read the source, 5 d ago · tools taken from the live server · rules 995398eba69f

A tool parameter reaches a dangerous call

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

A tool parameter reaches a file or shell call object_registry.action → packages/mcp-adapter/index.js:435
        return { contents: [{ uri, mimeType: 'application/schema+json', text: fs.readFileSync(path.join(SCHEMAS_DIR, file), 'utf8') }] };
Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

File ships in the package but is absent from the source [пакет] echarts.js:1
этот файл ставится пользователю, но в репозитории его нет
const { archive } = JSON.parse(fs.readFileSync(path.join(PACKAGE_DIR, 'runtime', manifestFile), 'utf8'));
In the project's build, not in the package

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

      const child = spawn(nodeBin, [this.entry, '--server-cwd', this.serverCwd, '--port', '0'], {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

A tool parameter here reaches a dangerous call

That is not a flaw by itself — but it is where things go wrong when it is not the job. We re-read this code on every release. Watch it and you hear from us the day another one appears.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add foundry --transport http https://oods-foundry.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://oods-foundry.com/mcp
~/.codex/config.toml
[mcp_servers.foundry]
url = "https://oods-foundry.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "foundry": {
      "url": "https://oods-foundry.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "foundry": {
      "type": "http",
      "url": "https://oods-foundry.com/mcp"
    }
  }
}

Available tools 9

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

artifact
artifact_certify
Draw and certify a chart from the input in chart, using matching data, brand and theme. Returns the same result as viz_render: hashes, warnings and the certification verdict, including accessibility equivalence, determinism, contrast and accuracy. Optional chart.output fields add SVG, the accessible table and narrative, or the normalized specification. A verdict can be conformant false; each pillar explains its result.
catalog
catalog_list
Read components a page at a time. category, trait, context and status filter the list; status describes the HTML renderer. detail is brief by default, or full when filtering; summary includes tags, contexts, regions and traits. Brief and summary allow up to 200 entries; full clamps pageSize to 10 and reports the adjustment. totalCount, hasMore and nextPage describe pagination. object_registry reads objects instead.
design
design_preview
Look up a recorded screen by object, context and framework. Returns its running screen URL, content hash, brand and theme. No new screen is generated. object_registry reads the definition behind the screen. Set reproduce true when the command and calls used to generate it are requested.
health
health_check
Read the running service status, pinned version, registry counts, built brands, themes, token scopes and retained proof summaries. Uptime and latency are current process measurements; host paths are omitted. includeChangelog adds the DSL changelog, and sinceVersion keeps entries after that version. catalog_list and object_registry read the definitions behind the counts.
object
object_registry
Read objects from the pinned registry. action list returns names, traits and field counts; domain, trait and maturity filter them, and includeInternal adds internal objects. action show requires name and returns its composed definition; context narrows view extensions. registry_snapshot provides an overview; design_preview looks up recorded screens.
registry
registry_snapshot
Read the registry summary: active objects and traits, loaded names, loader issues, etag and generatedAt. detail full includes definitions; names narrows them. includeInternal adds internal objects. Replies larger than 100,000 characters are refused with their size. object_registry reads one composed object; catalog_list reads components.
structured
structured_data_fetch
Read the tokens or manifest dataset. Full data is the default; detail summary returns section counts and the first page call. page reads lossless JSON Pointer entries; pageSize defaults to 10, at most 100, also bounded by size. meta.next continues and meta.full requests full data. includePayload false returns metadata; listVersions lists dates, version selects one, and ifNoneMatch returns matched true without unchanged payload. catalog_list reads components.
tool
tool_schema
Read a shipped tool schema by name and kind (input or output). Returns its JSON Schema, package-relative file, recorded file hash and source URL. tools/list describes this endpoint’s narrower accepted inputs; the full schema may describe operations outside the hosted tools.
viz
viz_render
Draw and certify a chart from inline data. Provide chartType and encodings with rows, a pattern with its own data, or an intent to recommend a tabular chart. Brand and theme apply to drawing and certification. The compact reply contains hashes, warnings and certification; output.svg adds the SVG drawing, includeA11y adds the table and narrative, and includeNormalizedSpec adds its specification. Request SVG when a displayed chart is needed. Up to 500 rows; optional outputs still share the 100,000-character reply bound. artifact_certify returns the same drawing and checks for an input in chart.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

health
removed 6 Oct 2026
object
removed 6 Oct 2026
structuredData_fetch
removed 6 Oct 2026

Endpoints

URLTransportStateLatencyChecked
https://oods-foundry.com/mcp streamable-http answering 318 ms 12 min ago

Alternatives to OODS Foundry

same job, measured the same way
Roast My Design System
by pencilrebel

Audit your Design System and serve your Agent the rules that keep AI-written UI on-system.

474 installs/wk local only
Roast My Design System
by gregkozakiewicz

Audit your Design System and serve your Agent the rules that keep AI-written UI on-system.

local only
UIcockpit
by uicockpit

Generate a design system from a brief, then verify your AI stays on it.

7 installs/wk local only
Buoy
by ahoybuoy

The design system your coding agents check before they ship: tokens plus exact UI fixes.

410 installs/wk local only
Anima MCP Server
by animaapp

Connect AI coding agents to Anima Playground, Figma, and your design system.

answering
UX Pilot
by uxpilot

UX Pilot's design agent for your AI tools: on-brand UI, design systems and React prototypes

answering
onsystem
by dgesteves

Catches palette colors, native elements and APIs your design system lacks in agent-written React.

469 installs/wk local only
Mzizi MCP
by nyuchi

Read-only MCP over the Mzizi design system registry — nodes, components, ownership.

14 tools answering

OODS Foundry — questions

Answers built from our own checks of this server.

What can OODS Foundry do?
It exposes 9 tools, read directly from the server on our last check. Among them: artifact_certify, catalog_list, design_preview, health_check, object_registry, registry_snapshot and 3 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is OODS Foundry working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 345 ms. The bar chart above shows every period we have measured.
Did OODS Foundry ever remove tools?
Yes. health, object, structuredData_fetch are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
How do I connect OODS Foundry?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does OODS Foundry need an API key?
No. OODS Foundry completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 9 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is OODS Foundry?
It answers our handshake in 345 ms on average, which is faster than 45% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use OODS Foundry?
The npm package @oods/foundry was installed 281 times in the last week. Week over week that is -70%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is OODS Foundry open source?
The code is open source: it is published under the Apache-2.0 licence, written in TypeScript and 2 stars on GitHub. The licence covers the code in the repository, not the hosted service at oods-foundry.com, which runs on its operator's own terms.