Model Context Protocol server providing Taiga UI documentation search and scaffolding tools.
S1000D BREX (S1000D Stack) is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Read S1000D BREX business rules and check data modules against them, layer by layer.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user s1000d-brex-s1000d-stack-mcp '--' npx -y @shuji-bonji/s1000d-brex-mcp
# 2 — ask your agent for something these tools do
# explain_brex, lookup_sns, lookup_value and 2 more
S1000D BREX (S1000D Stack) costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts S1000D BREX (S1000D Stack) as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user s1000d-brex-s1000d-stack-mcp '--' npx -y @shuji-bonji/s1000d-brex-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
List the rules of a BREX data module in readable form: for each rule, the target (XPath), whether it is forbidden / required / optional, the allowed values with their meanings, severity, and the schema context it applies to. Also returns the BREX header (DMC, parent BREX, counts). Use "kind" and…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brex | no | — | |
| csdbDirs | no | — | |
| kind | string | no | Rule kind to list (default: all). |
| context | string | no | Only rules that apply to this schema (file name such as "descript", "proced", "pm") plus the common rules. Omit for all contexts. |
| search | string | no | Case-insensitive text to find in objectPath, objectUse, rule id or value meanings. |
| offset | number | no | Index of the first rule to return (default 0). |
| limit | number | no | Maximum rules to return (default 50, max 500). |
Explain what a Standard Numbering System (SNS) code means in a BREX: pass a DMC (the system / subsystem / sub-subsystem / assembly codes are taken from it) or the codes directly. Returns the matched hierarchy with titles; "exact: false" means only a prefix matched.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brex | no | — | |
| csdbDirs | no | — | |
| dmc | string | no | A DMC whose SNS part should be looked up. |
| systemCode | string | no | System code (2-3 characters), when not passing dmc. |
| subSystemCode | string | no | Subsystem code (1 character). |
| subSubSystemCode | string | no | Sub-subsystem code (1 character). |
| assyCode | string | no | Assembly code (2 or 4 characters). |
Explain what a value of an element or attribute means in a BREX, or list the allowed values. Pass "target" as an attribute name (e.g. "securityClassification"), an element name, or an XPath fragment; optionally "value" to check one value. Returns the matching rules with allowed values and their…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brex | no | — | |
| csdbDirs | no | — | |
| target | string | yes | Attribute name ("infoCode", "@infoCode"), element name ("language"), or XPath fragment to match against objectPath. |
| value | string | no | The value to check against the allowed values (optional). |
| context | string | no | Schema file name (e.g. "descript") to pick context-specific rules in addition to common ones. |
List the illustration / multimedia notations (file formats) a BREX allows: the base set (common to all schemas) and the per-schema additions and exclusions. Pass "context" to get the effective rule for one schema: mode "closed" (only the listed notations may be used), "open" (only the excluded…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brex | no | — | |
| csdbDirs | no | — | |
| context | string | no | Schema file name (e.g. "ipd", "proced") to compute the effective set for. |
Check a data module against BREX rules and report violations with location (XPath + line), actual value, rule id, objectUse text and severity. By default follows the data module's brexDmRef chain (project BREX → … → S1000D default BREX found under S1000D_SPEC_DIR) and checks each layer separately;…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | no | File path of the data module to check. |
| xml | string | no | The data module as an XML string (alternative to path; max 5 MB). |
| brex | string | no | A specific BREX (file path or DMC) to check against. With followChain=false it is the only layer; otherwise it is added to the chain. |
| followChain | boolean | no | Follow the brexDmRef chain of the data module (default true). |
| csdbDirs | no | — | |
| includeManualChecks | boolean | no | Include nonContextRules as manualChecks in each layer (default true). |
| maxViolationsPerLayer | number | no | Cap on violations returned per layer (default 200). The total count is always reported. |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install S1000D BREX (S1000D Stack) or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.6.4. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
No release note was published with this version.
No release note was published with this version.
No release note was published with this version.
No release note was published with this version.
No release note was published with this version.
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish S1000D BREX (S1000D Stack) can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.