Read-only MCP server for one AINDF design-system bundle: look up what it offers, validate screens.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
get-dsIdentity, pin and overview of this design system: roles, components by layer, bindings, AINDF version. Start here; copy `pin` into every screen.Identity, pin and overview of this design system: roles, components by layer, bindings, AINDF version. Start here; copy `pin` into every screen.
No input schema was published for this tool.
list-by-facetAINDF 0.1: components filtered by layer, role and/or renderTarget.AINDF 0.1: components filtered by layer, role and/or renderTarget.
No input schema was published for this tool.
get-componentFull contract of one component: classification, closed props, slots, states, accessibility, good/bad examples.Full contract of one component: classification, closed props, slots, states, accessibility, good/bad examples.
No input schema was published for this tool.
slot-acceptsAINDF 0.1: what a slot of a component accepts (layers, components, cardinality).AINDF 0.1: what a slot of a component accepts (layers, components, cardinality).
No input schema was published for this tool.
applicable-modifiersAINDF 0.1: modifiers applicable to a component.AINDF 0.1: modifiers applicable to a component.
No input schema was published for this tool.
get-presetAINDF 0.1: a pre-composed preset by name (omit name to list).AINDF 0.1: a pre-composed preset by name (omit name to list).
No input schema was published for this tool.
validate-screenAdmission of a ScreenSpec JSON against this exact DS revision. Returns ok or stable error codes with paths. Validation never builds, publishes or accepts anything.Admission of a ScreenSpec JSON against this exact DS revision. Returns ok or stable error codes with paths. Validation never builds, publishes or accepts anything.
No input schema was published for this tool.
submit-screenStage an admitted ScreenSpec as an unaccepted draft for the trusted builder. Requires an author token. Staging is write-once; it never builds, verifies, accepts or releases.Stage an admitted ScreenSpec as an unaccepted draft for the trusted builder. Requires an author token. Staging is write-once; it never builds, verifies, accepts or releases.
No input schema was published for this tool.
request-extensionAsk the DS owner for a missing capability instead of working around the contract. Requires an author token.Ask the DS owner for a missing capability instead of working around the contract. Requires an author token.
No input schema was published for this tool.
9 of 9 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Read-only MCP server for one AINDF design-system bundle: look up what it offers, validate screens.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.