Skip to content
OODS Foundry logo

OODS Foundry MCP server

Which MCP servers are OODS Foundry's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-22

← Back to OODS Foundry

Whose server it is
  • Registry namecom.oods-foundry/foundryverified in the MCP registry

The registry name sits under oods-foundry.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-22
  • Stateanswerschecked 2026-10-22
  • Tools9
  • Server calls itselfoods-foundry-site
  • Server version0.11.2
  • Protocol version2025-06-18

On 2026-10-22 the server answered initialize and tools/list without a sign-in. First answer in 85 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 11, the first on 2026-10-22
  • INITE MCP score91 of 100answers 100 · definitions 98 · context 84 · use 53 · connects 100
  • Use426 npm downloads a week2 GitHub stars
  • Answered100% of days11 of 11 daily checks
  • Median first answer164 ms
  • Space in an agent's context≈ 5,463 tokensthe definitions of all its tools (9), which an agent carries on every turn
  • Tool definitionsA · 98 of 100
  • Typed results0 of 9 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 1 of 9

What an agent can do with it

  • not sure · generate subscription detail screens from a schema file
  • cannot · change a shared trait once and rebuild affected screens
  • not sure · check generated screens against object rules and receipts

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers9 tools · read 2026-10-22
  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "foundry": {
      "type": "http",
      "url": "https://oods-foundry.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http oods-foundry https://oods-foundry.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://oods-foundry.com/mcp as a custom connector in the settings.

Also shipped through: npm

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.