WCGW Safety Suite - Functional Safety Requirements and Traceability MCP Server

io.github.vwnbPublished by GitHub account vwnbv1.0.5Updated Nov 7, 2026

Manage functional-safety requirements and lifecycle traceability.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote MCP server for managing functional-safety requirements and their lifecycle traceability, reached over streamable HTTP with OAuth sign-in.

What you can do
  • Manage functional-safety requirements
  • Track lifecycle traceability across those requirements
  • The registry lists no individual tools, so the exact operations are not documented
  • No instructions or README are provided, so capabilities beyond the description are unknown
When to use it
Worth considering if you work with functional-safety requirements and want an assistant to help maintain them and their traceability links. Because no tool list or documentation is published, evaluate it only after confirming what it actually exposes.
Requirements
A remote MCP endpoint over streamable HTTP; OAuth authentication is required. No environment variables or headers are declared, and no local package is needed.
Before you install
OAuth grants the server access tied to your account, so review the scopes requested at sign-in. The published material does not say whether it can create, change or delete requirements, or where your data is stored; confirm this before relying on it for safety-critical records.

Installation

In SourceWeft

  1. Open WCGW Safety Suite - Functional Safety Requirements and Traceability MCP Server in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.vwnb%2Fwcgw.world/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "wcgw-safety-suite-functional-safety-requ": {
      "type": "http",
      "url": "https://safety-requirements-god.vercel.app/wcgwmcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.5LatestNov 7, 2026
  2. v1.0.4Nov 3, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.