Stratta
NPM · @STRATTA/MCP · SCANNED SEP 25
Read the SIA and Eurocode norms your bureau licensed, cited to the section and page.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 125 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (UNLICENSED) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 4 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 9313 tokens (~152/item across 61 items; 59 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management85
- Stability check failed: the tool surface changed between 0.9.2 and 1.16.0: 0 tool removals, 7 breaking changes, 36 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 61 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Stratta MCP server?
Stratta runs locally as an npm package, launched with npx -y @stratta/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @stratta/mcp
claude mcp add ch-stratta-mcp -- npx -y @stratta/mcp
{
"mcpServers": {
"ch-stratta-mcp": {
"command": "npx",
"args": [
"-y",
"@stratta/mcp"
]
}
}
} {
"servers": {
"ch-stratta-mcp": {
"command": "npx",
"args": [
"-y",
"@stratta/mcp"
]
}
}
} codex mcp add ch-stratta-mcp -- npx -y @stratta/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ch-stratta-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@stratta/mcp"
],
"enabled": true
}
}
} openclaw mcp add ch-stratta-mcp --command npx --arg -y --arg @stratta/mcp
mcp_servers:
ch-stratta-mcp:
command: "npx"
args: ["-y", "@stratta/mcp"] {
"McpServers": {
"ch-stratta-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@stratta/mcp"
]
}
}
} assistant mcp add ch-stratta-mcp -t stdio -c npx -a -y @stratta/mcp
{
"mcpServers": {
"ch-stratta-mcp": {
"command": "npx",
"args": [
"-y",
"@stratta/mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 71 to 75.
- 20 Sept 26 +1
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Schema quality: 8460 → 9313 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 1.15.0 → 1.16.0 functional
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 58 to 61.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 51 to 55.
- 15 Sept 26 +15
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.14.0 → 1.15.0 functional
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Schema quality: 5470 → 8396 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.13.1 → 0.14.0 functional
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 41 to 45.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Analysed npm/@stratta/mcp@1.16.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 125 packages
| Packages resolved | 125 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
scan_site Scan a site ~204
Collect what public Swiss registers know about a building site: municipality, parcel, ground elevation, geology, nearby boreholes with their strata, polluted sites, groundwater protection, natural hazards, noise sensitivity. Give a Swiss address; it is geocoded server-side against swisstopo, so do not pass coordinates you inferred. Open the dossier first with open_dossier: one site per dossier. The scan runs in the background and takes a few seconds; read the result with get_site_context. It is a survey of public registers, never a geotechnical study.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The street address in Switzerland, as the user wrote it: "Av. de Rhodanie 58, Lausanne". |
| dossierId | string | yes | Dossier id returned by open_dossier or list_dossiers. |
| radius | integer | – | How far around the site to look for boreholes and constraints, in metres (50 to 1000, default 300). |
No output schema declared.
No examples provided.
search_corpus Search all norms ~145
Full-text search across every norm the organization can read, grouped by norm, heading hits from any norm ahead of body hits. Use it first when the question does not name its norm: it tells which norms speak of the subject before any table of contents is opened. Same matching as search_in_norm. Returns, per norm, its code and title and a few hits; continue with get_section on the paths that look relevant.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | Search terms in the language of the norms, accents optional. Several words find sections containing all of them. |
| limit | integer | – | Maximum number of hits across all norms, 1 to 40. Default 20. |
No output schema declared.
No examples provided.
search_in_dossier Search the attachments ~102
Full-text search over the attachments of one dossier, accents and case ignored, matching per term. Returns the attachment, the page and a snippet for each hit; read the page with read_attachment before quoting it.
| Name | Type | Req | Description |
|---|---|---|---|
| dossierId | string | yes | The dossier whose attachments to search. |
| keyword | string | yes | Search terms in the language of the documents. |
| limit | integer | – | Maximum number of hits, 1 to 30. Default 10. |
No output schema declared.
No examples provided.
search_in_norm Search a norm ~234
Full-text search inside one norm, ranked, a hit in a heading outranking a hit in the body. Use it when the table of contents suggests no obvious section. Matching is per term, not per substring, in the language of the norm: search "charges" in a French norm, not "loads"; accents and case do not matter. A clause number as keyword returns that clause. Returns paths, titles and snippets; read the promising ones with get_section.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Norm code exactly as list_norms returns it, e.g. "SIA 261", "SIA 267", "EN 1997-1". |
| edition | string | – | Edition of the norm when the organization holds several ("2013", "2020"). Default: the most recent published edition; list_norms names them. |
| keyword | string | yes | Search terms in the language of the norm, accents optional. Several words find sections containing all of them; a clause number finds that clause. |
| limit | integer | – | Maximum number of hits, 1 to 50. Default 20. |
No output schema declared.
No examples provided.
update_entry Correct an entry ~259
Correct a piece of evidence or a decision in place: its wording, its value, its confidence, or the citation (norm, section path, page, edition) when the wrong clause was cited. Pass only the fields to change; pass page null to clear it. The kind and the question do not change here (attach_entry moves an entry). Only when the user asked for the correction; never rewrite what a colleague wrote without saying so.
| Name | Type | Req | Description |
|---|---|---|---|
| confidence | string | – | established, judgement or to_confirm. |
| detail | string | – | The reasoning in one or two sentences. |
| entryId | string | yes | Entry id from get_question or load_dossier. |
| normCode | string | – | Norm the entry comes from, e.g. "SIA 267". |
| normEdition | string | – | The edition cited, e.g. "2013". |
| page | – | – | Page in the norm. null clears it. |
| sectionPath | string | – | Exact section path, e.g. "9.5.2.1". |
| title | string | – | The fact in one line, as an engineer would write it in a report. |
| value | string | – | The retained value with its unit, e.g. "30 deg". |
No output schema declared.
No examples provided.
update_option Edit an option ~144
Rename or describe an option of a question, or mark it as the one retained. Retaining one option releases the others: a choice has one answer. Retaining here does not settle the question; call record_decision for that, which names the retained option itself. Pass only the fields to change. Only when the user asked for it.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | The new description. |
| name | string | – | The new name of the option. |
| optionId | string | yes | Option id from get_question, list_questions or load_dossier. |
| retained | boolean | – | true to mark this option as retained (the others are released), false to release it. |
No output schema declared.
No examples provided.
update_question Edit a question ~194
Reword a question, rewrite what is at stake, assign it to a member of the organization by e-mail address, or set its due date. Pass only the fields to change; pass null to clear the assignee or the due date. Status changes go through record_decision and resolve_question, not here. Only when the user asked for the change.
| Name | Type | Req | Description |
|---|---|---|---|
| assigneeEmail | – | – | E-mail address of the member to assign the question to. null removes the assignee. |
| body | string | – | What is at stake and why it is not settled, in two or three sentences. |
| dueAt | – | – | Due date as an ISO day, e.g. "2026-10-15". null removes it. |
| questionId | string | yes | Question id from list_questions, load_dossier or open_question. |
| title | string | – | The new wording, in one line, phrased as a question. |
No output schema declared.
No examples provided.
whoami Connected account ~55
Report which organization this connection reads from, the signed-in role, the plan name and how many norms are available. Use it to confirm the connection points at the intended workspace before starting, or when a norm the user expects is missing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
write_section Write a section ~329
Write one section of a deliverable: the text as it would be printed, and what it rests on. Every sentence of substance must come from a source the section lists: a decision or piece of evidence of the dossier (kind entry, ref the entry id), a fact of the site (kind fact, ref the fact key such as groundwater.level), a clause read in a norm (kind clause, ref the norm code and the section path as in "SIA 267 s. 9.5.2"), a page of an attachment (kind attachment, ref the id with #p12), or a reading recorded by the dossier (kind reading, ref the reading id). A section without a source is refused; when the dossier has nothing for it, pass gap true with a body that says what is missing, and the section is printed as something to establish. Replaces what the section held. Never invent a value: a section written from memory is worse than a gap.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The text of the section, plain prose or Markdown, up to 12000 characters. |
| deliverableId | string | yes | The deliverable id from draft_deliverable. |
| gap | boolean | – | true when the dossier holds nothing for this section; the body then says what is missing. |
| path | string | yes | The section path from the plan, e.g. "2" or "3.1". |
| sources | array | yes | What the text rests on: a list of {kind, ref, label?}. At least one unless gap is true. |
No output schema declared.
No examples provided.
What is the Stratta MCP server?
Stratta is an MCP server listed in the public MCP registry as ch.stratta/mcp. Read the SIA and Eurocode norms your bureau licensed, cited to the section and page. This page covers its npm package (@stratta/mcp).
Is the Stratta MCP server safe to use?
Stratta scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Stratta MCP server expose?
Stratta exposes 59 tools: get_methodology, whoami, list_norms, get_toc, get_subtree, and 54 more. Their descriptions and schemas cost roughly 9,196 tokens of context every time the server is loaded.
Is the Stratta MCP server still maintained?
Stratta is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Stratta MCP server under?
Stratta declares the UNLICENSED licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.