Design
oods-foundry.com
Provides read-only access to OODS Foundry health, component catalog entries, object definitions, registry snapshots, and structured component, token, or manifest datasets.
ENDPOINT 1
https://oods-foundry.com/mcp
MCP server metadata
- Name
- oods-foundry-site
- Version
- 0.8.0
Read-only tools from @oods/foundry@0.8.0. Local stdio (npx -y @oods/foundry@0.8.0) is authoritative. Tool replies include exact local reproduction calls. design_preview looks up recorded screens; artifact_certify takes chart input and certifies the route's own normalized spec.
Known tools 9
health_checkCheck 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.
Inferred read-onlyregistry_snapshotRead 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.
Inferred read-onlystructured_data_fetchFetch one registry dataset as a single export: dataset components (the live registry’s components, objects and traits), tokens or manifest.
Inferred read-onlyartifact_certifyCertify 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.
Inferred read-onlydesign_previewFind 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.
Inferred read-onlytool_schemaRead 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.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
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.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for oods-foundry.com was fetched 2026-10-14T05:19:41.693Z.
oods-foundry.com is assessed as Trusted: Domain runs a meaningful technology spend, consistent with a real business.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.