MCP server for DeepL translation API
Nothing to run from here
Stackwright Pro 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.
95/100
trust score
1
downloads a day
local
runs on your machine
439
downloads in 30d
What it does
MCP tools for Stackwright Pro - Data Explorer, Security, ISR, and Dashboard generation
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user stackwright-pro-mcp '--' npx -y @stackwright-pro/mcp
# 2 — ask your agent for something these tools do
# stackwright_pro_list_entities, stackwright_pro_generate_filter, stackwright_pro_validate_spec and 59 more
Stackwright Pro costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SPAll 1 server
@stackwright-pro1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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 Stackwright Pro 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.
Claude Codedeclared by this listing
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 stackwright-pro-mcp '--' npx -y @stackwright-pro/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
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.
What you approve
62 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.
List all available API entities from OpenAPI specs or generated Zod schemas. Use this to discover what entities are available before generating endpoint filters. Returns entity names, endpoints, and field counts. Part of the Pro Otter Raft for building API-integrated Stackwright applications.
No parameter schema on file.
Generate endpoint filter configuration from selected entities. Creates include/exclude patterns for stackwright.yml OpenAPI integration. Use this after stackwright_pro_list_entities to select which API endpoints the application needs. Only selected endpoints will generate client code, reducing…
No parameter schema on file.
Validate an OpenAPI spec against the enterprise approved-specs configuration. Checks if the spec URL is on the allowlist and verifies SHA-256 hash integrity. Use this in enterprise environments where only pre-approved API specs are allowed. Fails build if spec is not approved or has been modified.
No parameter schema on file.
Add an OpenAPI spec to the approved-specs allowlist in stackwright.yml. Computes the SHA-256 hash of the spec and adds it to the security configuration. Use this when onboarding a new API in enterprise environments.
No parameter schema on file.
List all specs currently on the approved-specs allowlist. Shows spec names, URLs, and hash prefixes. Use this to audit what APIs are approved in the project.
No parameter schema on file.
Configure Incremental Static Regeneration (ISR) for an API-backed collection. ISR allows API data to be cached and refreshed on a schedule, providing real-time data with the performance of static generation. Use this after stackwright_pro_generate_filter to set revalidation intervals.
No parameter schema on file.
Configure ISR for multiple collections at once. More efficient than calling stackwright_pro_configure_isr multiple times. Provide different revalidation intervals based on data freshness requirements.
No parameter schema on file.
Live data from API
No parameter schema on file.
Generate a detail view page for a single API entity. Creates YAML content for displaying all fields of an individual record. Use this to create detail pages that complement collection listing pages.
No parameter schema on file.
Ask the user for clarification when a specialist otter encounters ambiguity. This is for MID-EXECUTION questions, NOT upfront question collection (use the Question Manifest Protocol for that). Returns a structured response for the foreman to present to the user via ask_user_question…
No parameter schema on file.
Detect when a user's stated preference conflicts with their selected choices. Uses keyword heuristics against known contradiction patterns (minimal vs vibrant, dark vs light, etc). Returns conflict details and resolution options.
No parameter schema on file.
Ensures pro packages are present in a project's package.json. Safe to call multiple times — never overwrites existing version pins. Use this to bootstrap dependencies before specialist otters run. Pass includeBaseline: true to automatically include all required @stackwright-pro/* baseline…
No parameter schema on file.
Adapt manifest-format questions from a specialist otter and present them to the user via ask_user_question. Pass only the phase name — this tool reads questions from .stackwright/question-manifest.json automatically. The questions parameter is optional and only needed if the manifest has not been…
No parameter schema on file.
Returns the next unanswered question for a phase as a plain JSON object — one question at a time. Returns { done: true } when all questions are answered or the phase has no questions. Call this in a loop: present the question in plain chat, get user reply, call record_answer, repeat.
No parameter schema on file.
Records a single answer to a phase question. Appends to .stackwright/answers/{phase}.json incrementally. Idempotent — calling twice for the same questionId overwrites. Call after receiving each user reply in the conversational question loop.
No parameter schema on file.
Save the user's initial build description to .stackwright/build-context.json. Call this once at startup after the user answers the opening "what are you building" question. The saved context is automatically prepended to specialist prompts by stackwright_pro_build_specialist_prompt.
No parameter schema on file.
Parse and validate a specialist otter's QUESTION_COLLECTION_MODE JSON response. Handles JSON extraction from LLM responses (strips markdown, fixes single quotes, trailing commas). Detects the phase from the otter name. Use this immediately after invoke_agent() to get a validated manifest phase…
No parameter schema on file.
Write the question manifest to .stackwright/question-manifest.json. Call this after collecting and parsing questions from all otters via stackwright_pro_parse_otter_response.
No parameter schema on file.
Save user answers for a phase to .stackwright/answers/{phase}.json. Pass rawAnswers directly from ask_user_question and the original manifest questions for label-to-value reverse mapping.
No parameter schema on file.
Read saved answers for a phase from .stackwright/answers/{phase}.json. Returns { missing: true } when no answers exist yet — use this to skip phases safely in the execution loop.
No parameter schema on file.
Get the agent name for a phase (e.g. 'designer' → 'stackwright-pro-designer-otter'). Use this in the execution loop to invoke the correct specialist otter without hardcoding names in the prompt.
No parameter schema on file.
Verify ECDSA P-384 signatures for all pipeline artifacts in .stackwright/artifacts/. Auto-discovers keys from .stackwright/pipeline-keys.json. Returns per-artifact verification status.
No parameter schema on file.
Read ALL route-producing artifacts from the pipeline artifacts directory: *-manifest.json files (pages, dashboard, geo, form-wizard) AND workflow-config.json / workflow-config-*.json (different shape: workflow.route). Deterministically derives protectedRoutes and uncoveredSlugs. Uses the…
No parameter schema on file.
Returns a compact, LLM-friendly summary of a canonical schema derived programmatically from Zod. Includes required/optional fields, types, constraints, and "did you mean?" warnings for common field-name drift. Use before authoring YAML to confirm exact field names.
No parameter schema on file.
Read pipeline state from .stackwright/pipeline-state.json. …
No parameter schema on file.
Atomic read→modify→write pipeline state. …
No parameter schema on file.
Check all phases have answer files in .stackwright/answers/. If phase is provided, check only that phase. …
No parameter schema on file.
Return phases whose dependencies are all satisfied (executed=true). Use to determine which phases can run next — enables wave-based execution. …
No parameter schema on file.
List phase artifacts in .stackwright/artifacts/ with completedCount/totalCount. …
No parameter schema on file.
Parse otter question-collection response → .stackwright/questions/{phase}.json. Specialists may also call this directly with a parsed questions array. …
No parameter schema on file.
Assemble execution prompt from answers + upstream artifacts. Foreman passes verbatim. …
No parameter schema on file.
Validate and write artifact to .stackwright/artifacts/. Returns retryPrompt on failure. …
No parameter schema on file.
Design language artifact
No parameter schema on file.
No parameter schema on file.
Generate authentication middleware and configuration for a Next.js Stackwright application. Writes middleware.ts (or proxy.ts for Next.js >=16) from a secure template, writes a standalone stackwright.auth.yml sibling file, and generates .env.example with required environment variables. ⚠️…
No parameter schema on file.
Verify SHA-256 integrity of all Pro otter agent definitions. Call this at startup before discovering otters. Auto-discovers the otter directory from known paths. Returns verified/failed/unknown lists.
No parameter schema on file.
List API-backed collections available for page generation. Reads from Data Otter artifact (.stackwright/artifacts/data-config.json) or stackwright.yml. Call this before generating pages that bind to data.
No parameter schema on file.
Look up the data freshness strategy configuration from the user's answer. Returns mechanism, revalidation seconds, required packages, and the exact MCP tool call to make. Replaces the strategy table in the data-otter prompt.
No parameter schema on file.
Workflow DSL — step definitions, auth blocks, field types, conditions
No parameter schema on file.
Returns a structured summary of all canonical @stackwright-pro/types schemas, organized by domain. Use this to determine which otter owns a given schema and what artifact key to expect.
No parameter schema on file.
Validates a YAML snippet against a canonical Zod schema before writing to disk. Returns actionable errors with "did you mean?" suggestions for common field-name drift (title vs label, id vs name, style vs theme.variant, etc.). Call this before stackwright_pro_safe_write to catch schema violations…
No parameter schema on file.
Write or update a page's YAML content with Pro content-type awareness. Validates against the Stackwright schema (including Pro types like stats_grid, data_table_pulse, map_pulse, alert_banner). Invalid YAML or schema violations on OSS-type fields are rejected with field-level errors. Use this…
No parameter schema on file.
Remove/rewrite stale scaffold files (blog posts, hardcoded not-found page) after the raft pipeline completes. …
No parameter schema on file.
No parameter schema on file.
Compute the exact WCAG 2.1 contrast ratio between a foreground and background color. Returns the ratio and AA/AAA pass/fail flags. Use this to verify any foreground/background color pair before writing it to the token set. Accepts #RGB, #RRGGBB, hsl(...), or shadcn HSL format ("H S% L%").
No parameter schema on file.
Given a seed color (treated as a background), derive the best accessible foreground (text) color that meets the target contrast ratio. Evaluates #ffffff and #000000 against the seed and picks whichever satisfies the target ratio with the highest contrast. Use this for every {name}-foreground token…
No parameter schema on file.
Compile stackwright.collections.yml → public/stackwright-content/_collections.json. Reads and validates the live-collections sidecar config file and emits the JSON sink consumed at runtime by PulseCollectionProvider.
No parameter schema on file.
Compile stackwright.auth.yml → public/stackwright-content/_auth.json. Reads and validates the auth sidecar config file and emits the JSON sink consumed at app startup to configure auth middleware.
No parameter schema on file.
Compile stackwright.integrations.yml → public/stackwright-content/_integrations.json. If no yml file exists, falls back to extracting integration metadata from _site.json (collections data is excluded — it lives in _collections.json).
No parameter schema on file.
Run all Pro compile sinks (collections + auth + integrations) in sequence. Equivalent to running compile_collections, compile_auth, and compile_integrations individually. Use this for a full Pro prebuild pass.
No parameter schema on file.
Compile stackwright.yml theme config → _theme.json. Delegates to compileTheme from @stackwright/build-scripts installed in the project.
No parameter schema on file.
Compile stackwright.yml → _site.json. Delegates to compileSite from @stackwright/build-scripts installed in the project.
No parameter schema on file.
Compile all pages content.yml files → page JSON files. Delegates to compilePages from @stackwright/build-scripts installed in the project.
No parameter schema on file.
Compile a single page by slug. Delegates to compilePage from @stackwright/build-scripts installed in the project.
No parameter schema on file.
Removes the deprecated top-level integrations[] block from stackwright.yml. The authoritative source for integration config is stackwright.integrations.yml — this tool cleans up legacy entries from older raft runs. Idempotent: no-op if no legacy block present. Preserves all other top-level keys,…
No parameter schema on file.
Emit .env.local + .env.local.example contents from stackwright.integrations.yml and services/*.yml. Deterministic emitter — same project config produces byte-identical output. Call this tool, then write both files with stackwright_pro_safe_write: 1. stackwright_pro_emit_env_local({ cwd }) → {…
No parameter schema on file.
Emit app/_components/providers.tsx from stackwright.integrations.yml. Deterministic emitter — uses LITERAL env access per integration so Next.js can inline NEXT_PUBLIC_* vars at build time. Also registers the map provider (default: Cesium for Pro). ⚠️ CRITICAL: DO NOT compose providers.tsx by…
No parameter schema on file.
Emit mock backend port assignments from stackwright.integrations.yml. Deterministic emitter — assigns consecutive ports starting at 4011 to each integration in declaration order. Skipped integrations (skipMockPort=true) are omitted and do not consume a port number. ⚠️ DO NOT pick mockUrl port…
No parameter schema on file.
Enumerate OpenAPI/AsyncAPI specs in the project's specs/ directory. Returns one entry per spec with integration name (derived from filename), detected format, and size. Used by the foreman to fan out the api phase with one api-otter invocation per spec.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
MCP tools for Stackwright Pro - Data Explorer, Security, ISR, and Dashboard generation
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source is public; its licence metadata reads SEE LICENSE IN LICENSE rather than naming a licence
- 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 Stackwright Pro or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 95 / 100
Release 0.2.0-alpha.130 · scanned 15 Oct 2026
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.
Threat score100
Client score95
Findings5 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationnone
Surface digestfa30285231908a3d31e051e3b0ccc2b766260605d2af0f01dd1076404682e4bf
Score vectorthreat 100 → client 95
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | none | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read | −2 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
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.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (62 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, 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. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| stackwright_pro_verify_otter_integrity | no tags | |
| stackwright_pro_list_entities | no tags | |
| stackwright_pro_generate_filter | no tags | |
| stackwright_pro_validate_spec | no tags | |
| stackwright_pro_add_approved_spec | no tags | |
| stackwright_pro_list_approved_specs | no tags | |
| stackwright_pro_configure_isr | no tags | |
| stackwright_pro_configure_isr_batch | no tags | |
| stackwright_pro_generate_dashboard | no tags | |
| stackwright_pro_generate_detail_page | no tags | |
| stackwright_pro_clarify | no tags | |
| stackwright_pro_detect_conflict | no tags | |
| stackwright_pro_setup_packages | no tags | |
| stackwright_pro_present_phase_questions | no tags | |
| stackwright_pro_get_next_question | no tags | |
| stackwright_pro_record_answer | no tags | |
| stackwright_pro_save_build_context | no tags | |
| stackwright_pro_parse_otter_response | no tags | |
| stackwright_pro_save_manifest | no tags | |
| stackwright_pro_save_phase_answers | no tags | |
| stackwright_pro_read_phase_answers | no tags | |
| stackwright_pro_get_otter_name | no tags | |
| stackwright_pro_verify_artifact_signatures | no tags | |
| stackwright_pro_read_auth_manifests | no tags | |
| stackwright_pro_get_schema | no tags | |
| stackwright_pro_get_pipeline_state | no tags | |
| stackwright_pro_set_pipeline_state | no tags | |
| stackwright_pro_check_execution_ready | no tags | |
| stackwright_pro_get_ready_phases | no tags | |
| stackwright_pro_list_artifacts | no tags | |
| stackwright_pro_write_phase_questions | no tags | |
| stackwright_pro_build_specialist_prompt | no tags | |
| stackwright_pro_validate_artifact | no tags | |
| stackwright_pro_emit_event | no tags | |
| stackwright_pro_safe_write | no tags | |
| stackwright_pro_configure_auth | no tags | |
| stackwright_pro_list_collections | no tags | |
| stackwright_pro_resolve_data_strategy | no tags | |
| stackwright_pro_validate_workflow | no tags | |
| stackwright_pro_get_type_schemas | no tags | |
| stackwright_pro_validate_yaml_fragment | no tags | |
| stackwright_pro_write_page | no tags | |
| stackwright_pro_cleanup_scaffold | no tags | |
| stackwright_pro_write_workflow_container_page | no tags | |
| stackwright_pro_check_contrast | no tags | |
| stackwright_pro_derive_accessible_palette | no tags | |
| stackwright_pro_compile_collections | no tags | |
| stackwright_pro_compile_auth | no tags | |
| stackwright_pro_compile_integrations | no tags | |
| stackwright_pro_compile_all | no tags | |
| stackwright_pro_compile_theme | no tags | |
| stackwright_pro_compile_site | no tags | |
| stackwright_pro_compile_pages | no tags | |
| stackwright_pro_compile_page | no tags | |
| stackwright_pro_strip_legacy_integrations | no tags | |
| stackwright_pro_emit_env_local | no tags | |
| stackwright_pro_emit_providers_file | no tags | |
| stackwright_pro_emit_mock_ports | no tags | |
| stackwright_pro_list_specs | no tags | |
| stackwright_pro_describe_endpoint | no tags | |
| stackwright_pro_consolidate_integrations | no tags | |
| stackwright_pro_reconcile_page_auth_blocks | no tags |
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
Integrityfirst-seen
Surface digestfa30285231908a3d
Scanned2026-10-15
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.2.0-alpha.130. Pin a release below and the command asks for exactly that one.
0.2.0-alpha.130
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish Stackwright Pro can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.