accueil / serveurs / Données & BDD / com.oods-foundry/foundry
com.oods-foundry/foundry
serveur MCP (Model Context Protocol) · oods-foundry-site 0.11.2
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que com.oods-foundry/foundry est sûr ?
Au dernier audit MCP Hub, le serveur MCP « com.oods-foundry/foundry » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 9 outils
- artifact_certify≈ 1503 tokens
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.
Paramètres, retour & exemple (2)
Paramètreschart· object · requisreproduce· boolean · optionnel
Include the command and calls for reproducing this result.
Exemple d'appel{"name": "artifact_certify", "arguments": {"chart": {}}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - catalog_list≈ 579 tokens
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.
Paramètres, retour & exemple (9)
Paramètrespage· integer · optionnel
1-based page index for pagination.trait· string · optionnel
Filter components by trait (e.g., 'Editable', 'Searchable')detail· string · optionnel · brief | summary | full
Defaults to brief unfiltered, full with filters. Both defaults are paged (filtered: 10 entries). summary adds tags, contexts, regions and traits; full includes evidence. Explicit detail without paging preserves the unbounded legacy request.status· string · optionnel · stable | beta | planned
Filter by legacy static-HTML status only: 'stable' = mapped HTML renderer; 'planned' = HTML fallback. Consult productReality.surfaces for React/Vue, generated-consumer and maturity evidence.context· string · optionnel
Filter components by context (e.g., 'detail', 'list')category· string · optionnel
Filter components by category (e.g., 'core', 'lifecycle', 'visual')pageSize· integer · optionnel
Components per page. Filtered calls without detail default to 10; nextPage gives the next call.reproduce· boolean · optionnel
Include the command and calls for reproducing this result.includeInternal· boolean · optionnel
Also list OODS Foundry's internal (non-business) objects in registry.objects, after the business objects. Without it they are left out and registry.hiddenInternal counts them.
Exemple d'appel{"name": "catalog_list", "arguments": {"page": 1, "trait": "texte", "detail": "brief", "status": "stable", "context": "texte", "category": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - design_preview≈ 328 tokens
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.
Paramètres, retour & exemple (4)
Paramètresobject· string · requis · Article | Invoice | Media | Organization | Plan | Product | Relationship | Subscription
An object with recorded screens at this version.context· string · optionnel · detail | list | form | timeline | card | inline | workflow
The context the screen was composed for.framework· string · optionnel · react | vue
The framework of the generated app.reproduce· boolean · optionnel
Include the command and calls for reproducing this result.
Exemple d'appel{"name": "design_preview", "arguments": {"object": "Article"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - health_check≈ 266 tokens
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.
Paramètres, retour & exemple (3)
Paramètresreproduce· boolean · optionnel
Include the command and calls for reproducing this result.sinceVersion· string · optionnel
When provided with includeChangelog, only return changelog entries since this version.includeChangelog· boolean · optionnel
When true, include DSL version changelog in the response.
Exemple d'appel{"name": "health_check", "arguments": {"reproduce": true, "sinceVersion": "texte", "includeChangelog": true}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - object_registry≈ 488 tokens
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.
Paramètres, retour & exemple (8)
Paramètresname· string · optionnel
Object name to look up (e.g. 'User', 'Product', 'Invoice')trait· string · optionnel
Filter to objects composing a given trait (e.g. 'Priceable', 'lifecycle/Stateful')action· string · requis · list | show
List objects or show one composed definition.domain· string · optionnel
Filter to objects in a specific domain (e.g. 'core.identity', 'saas.billing')context· string · optionnel
Optional: filter view_extensions to a single context (e.g. 'detail', 'list', 'form', 'timeline', 'card', 'inline')maturity· string · optionnel · draft | alpha | beta | stable
Filter by metadata maturity levelreproduce· boolean · optionnel
Include the command and calls for reproducing this result.includeInternal· boolean · optionnel
Also list OODS Foundry's internal (non-business) objects, after the business objects. Without it they are left out and hiddenInternal counts them.
Exemple d'appel{"name": "object_registry", "arguments": {"action": "list"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - registry_snapshot≈ 457 tokens
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.
Paramètres, retour & exemple (4)
Paramètresnames· array · optionnel
Exact trait and object names; misses go in notFound.detail· string · optionnel · summary | full
summary (default), or full definitions, best with names.reproduce· boolean · optionnel
Include the command and calls for reproducing this result.includeInternal· boolean · optionnel
Also list OODS Foundry's internal (non-business) objects, after the business objects. Without it they are left out and registry.hiddenInternal counts them.
Exemple d'appel{"name": "registry_snapshot", "arguments": {"names": [], "detail": "summary", "reproduce": true, "includeInternal": true}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - structured_data_fetch≈ 577 tokens
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.
Paramètres, retour & exemple (9)
Paramètrespage· integer · optionnel
Dataset only: read a 1-based page of lossless JSON Pointer entries, each reply below 100,000 characters. Omit for full data.detail· string · optionnel · summary | full
Dataset only. summary returns section counts and the call for page 1; full (default) preserves the dataset.dataset· string · requis · tokens | manifest
Registry dataset to return.version· string · optionnel
Request a specific date-stamped version (e.g., '2026-02-24'). Omit for latest. Applies to dataset mode only.pageSize· integer · optionnel
Dataset entries per page, default 10, also bounded by serialized size. Reply meta gives next and full calls.reproduce· boolean · optionnel
Include the command and calls for reproducing this result.ifNoneMatch· string · optionnel
Return matched=true without payload when the ETag matches.listVersions· boolean · optionnel
When true, return available version dates instead of payload.includePayload· boolean · optionnel
When false, omit payload even if no ETag match occurs.
Exemple d'appel{"name": "structured_data_fetch", "arguments": {"dataset": "tokens"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - tool_schema≈ 365 tokens
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.
Paramètres, retour & exemple (3)
Paramètreskind· string · optionnel · input | output
The tool's input schema or its output schema.name· string · requis · tokens_build | structured_data_fetch | brand_apply | brand_create | brand_read | catalog_list | code_generate | design_compose
Any OODS Foundry tool at this version, local-only tools included.reproduce· boolean · optionnel
Include the command and calls for reproducing this result.
Exemple d'appel{"name": "tool_schema", "arguments": {"name": "tokens_build"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - viz_render≈ 1520 tokens
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.
Paramètres, retour & exemple (20)
Paramètresid· string · optionnel
Optional stable identifier for the produced spec.geo· object · optionnel
Inline geojson or topojson with topoObjectName, rows, join and valueField; optional point or flow fields. tool_schema gives the full contract.name· string · optionnel
Optional human-friendly chart title.rows· array · optionnel
Inline flat data rows.brand· string · optionnel · A | B
Token brand for drawing and certification.chord· object · optionnel
Chord input: {nodes:[{name}],links:[{source,target,value}]}; links refer to node names; each directed pair must be unique.theme· string · optionnel · light | dark | hc
Colour theme for drawing and certification.intent· object · optionnel
Structured request: goal, measures and dimensions, with optional chartFamily; uses rows instead of explicit chartType and encodings.output· object · optionnel
Optional outputs; default reply has hashes and certification.sankey· object · optionnel
Sankey input: {nodes:[{name}],links:[{source,target,value}]}; links refer to node names. Use chartType:"sankey".network· object · optionnel
Force graph: nodes [{id,group}] and links [{source,target,value}], at most 250 nodes.opacity· number · optionnel
Constant mark opacity for Cartesian charts only; omission keeps renderer defaults.pattern· string · optionnel · pattern:viz:bubble-distribution | pattern:viz:correlation-matrix | pattern:viz:correlation-scatter | pattern:viz:detail-overview-bar | pattern:viz:diverging-bar | pattern:viz:drilldown-stacked-bar | pattern:viz:facet-small-multiples-line | pattern:viz:facet-target-band
Exact registered pattern identity; preserves source data and presentation. Cannot combine with chartType, data, intent or identity/presentation overrides.chartType· string · optionnel · bar | line | area | scatter | heatmap | treemap | sunburst | sankey
Chart family; Cartesian types need rows and encodings, others their named input. Omit to suggest from rows.encodings· object · optionnel
Cartesian bindings: each needs field; optional type, aggregate, title, format (d3-format), currency (ISO 4217).hierarchy· object · optionnel
Treemap/sunburst: {type:"nested",data:{name,value,children}} or {type:"adjacency_list",data:[{id,parentId,value}]}. See full schema.reproduce· boolean · optionnel
Include the command and calls for reproducing this result.description· string · optionnel
Optional override for the synthesized accessibility description. When omitted, a non-empty description is generated from the encodings.strictFields· boolean · optionnel
Warn about unresolved fields and unmatched map joins (OODS-V131/V134). Default false preserves existing behavior.a11yEquivalence· boolean · optionnel
Check Vega-Lite accessible equivalents (default true). Errors stop rendering; warnings are returned. ECharts-primary scaffolds are not checked here.
Exemple d'appel{"name": "viz_render", "arguments": {"id": "texte", "geo": {}, "name": "texte", "rows": [], "brand": "A", "chord": {}}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».