INDIVIDUAL MCP TOOL

object_registry

Read the pinned registry’s objects.

oods-foundry.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://oods-foundry.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for object_registry and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.oods-foundry-site]
url = "https://oods-foundry.com/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: oods-foundry-site
Remote MCP URL: https://oods-foundry.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "oods-foundry-site": {
      "url": "https://oods-foundry.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "oods-foundry-site",
  "transport": "streamable-http",
  "url": "https://oods-foundry.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

health_check — Check the OODS Foundry process behind these tools: its status, package version and uptime, registry counts (components, objects, traits), the built brands, themes and token scopes, and the retained proof summaries, each naming the release it measured.
catalog_list — List the pinned registry’s components, a page at a time.
registry_snapshot — Read the whole pinned registry in one reply: every active object (fields, semantics, tokens, traits) and every trait’s full definition, keyed by name, with the recorded component mappings (none on this hosted process), a canonical etag and generatedAt.
structured_data_fetch — Fetch one registry dataset as a single export: dataset components (the live registry’s components, objects and traits), tokens or manifest.
viz_render — Draw a chart with the pinned OODS Foundry and certify it, in one call.
artifact_certify — Certify a chart from its viz_render input, given as chart: the pinned package draws it and certifies the normalizedSpec it returns, in the same brand and theme, with the matching data for an ECharts type.
design_preview — Find a screen OODS Foundry generated at the pinned version: object and context pick one of the recorded object screens, and framework its React or Vue app.
tool_schema — Read the full JSON Schema of any OODS Foundry tool at the pinned version, as the package ships it: name is any of its tools, local-only ones included, and kind is input (the default) or output.