简洁的测试平台日志,波形(FSDB/VCD),根因分析MCP Server. A Simple and Universal MCP Server to Debug Testbench Simulation Failures Via Log Parsing And Waveform Analysis (FSDB/VCD)
MCPpedia last refreshed this data
This server has been archived and is no longer actively maintained.
TraceWeave is an MCP server that 简洁的测试平台日志,波形(FSDB/VCD),根因分析MCP Server. A Simple and Universal MCP Server to Debug Testbench Simulation Failures Via Log Parsing And Waveform Analysis (FSDB/VCD). Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 73/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"TraceWeave": {
"env": {
"PATH": "/tools/synopsys/verdi/O-2018.09-SP2-11/bin:/tools/synopsys/vcs/O-2018.09-SP2-11/bin:/tools/cadence/XCELIUM1803/tools/bin:/usr/local/bin:/usr/bin:/bin",
"VCS_HOME": "/tools/synopsys/vcs/O-2018.09-SP2-11",
"XLM_ROOT": "/tools/cadence/XCELIUM1803",
"VERDI_HOME": "/tools/synopsys/verdi/O-2018.09-SP2-11"
},
"args": [
"/home/robin/Projects/mcp/TraceWeave/server.py"
],
"command": "python3.11"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
TraceWeave is a workflow-oriented debug server rather than a loose collection of parsers. It combines:
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
uvx 'mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
MCP Python SDK: WebSocket server transport does not support Host/Origin validation
### Summary In affected versions, the deprecated WebSocket server transport (`mcp.server.websocket.websocket_server`) accepted the WebSocket handshake without applying any `Host` or `Origin` header validation. The `TransportSecuritySettings` mechanism that the SSE and Streamable HTTP transports use for this purpose was not wired into the WebSocket transport, so there was no SDK-level way to restrict which origins could connect. ### Am I affected? Only if a developer's application server exposes
MCP Python SDK: HTTP transports serve session requests without verifying the authenticated principal
### Summary In affected versions, the SSE and Streamable HTTP server transports routed incoming requests to an existing session based only on the session identifier, without verifying that the request was authenticated as the same principal that created the session. Anyone who learned or guessed a session ID could send JSON-RPC messages on that session, regardless of which bearer token the request carried. ### Am I affected? Only if a developer's application server uses an HTTP transport (SSE,
MCP Python SDK: Experimental task handlers allow any client to access and cancel other clients' tasks
### Summary In affected versions, the default request handlers installed by the experimental tasks feature (`server.experimental.enable_tasks()`) did not check which session created a task before acting on it. On a server with more than one connected client, any client could observe, read results from, and cancel tasks belonging to other clients. ### Am I affected? Only if the developer's application server calls `server.experimental.enable_tasks()`. If `grep -r enable_tasks` over their codebas
Model Context Protocol (MCP) Python SDK does not enable DNS rebinding protection by default
### Description The Model Context Protocol (MCP) Python SDK does not enable DNS rebinding protection by default for HTTP-based servers. When an HTTP-based MCP server is run on localhost without authentication using `FastMCP` with streamable HTTP or SSE transport, and has not configured `TransportSecuritySettings`, a malicious website could exploit DNS rebinding to bypass same-origin policy restrictions and send requests to the local MCP server. This could allow an attacker to invoke tools or ac
MCP Python SDK vulnerability in the FastMCP Server causes validation error, leading to DoS
A validation error in the MCP SDK can cause an unhandled exception when processing malformed requests, resulting in service unavailability (500 errors) until manually restarted. Impact may vary depending on the deployment conditions, and presence of infrastructure-level resilience measures. Thank you to Rich Harang for reporting this issue.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in developer-tools / data
Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors
MCP server for using the GitLab API
Manage Supabase projects — databases, auth, storage, and edge functions
Chrome DevTools for coding agents
MCP Security Weekly
Get CVE alerts and security updates for TraceWeave and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
English · 简体中文
MCP server for simulation-failure debug through log parsing and waveform analysis
What sets TraceWeave apart: when a Verdi license is available it engages KDB/NPI for accurate cross-hierarchy driver / load / connectivity analysis; without a license it still locates issues via the built-in Static backend, log parsing, and VCD/FSDB waveform reads. It supports driver backtracking, load/fanout lookup, value-at-time queries, cycle-aligned sampling, arbitrary signal-window queries, lightweight X/Z tracing, structural risk scanning, and failure-group diffing — and emits structured next-step debug recommendations for MCP clients.
Workflow illustration; timing and speedup depend on project scale and waveform availability.
TraceWeave is a workflow-oriented debug server rather than a loose collection of parsers. It combines:
Architecture · Installation · Client Setup · Standard MCP Workflow · Tool Quick Reference · Testing · WeChat
TraceWeave is not a universal speedup, and it is honest about that. In blind benchmarking against a capable LLM that only reads source and text logs:
When the RTL is readable and the bug is a source-visible logic error, an
LLM reading the source is already fast. Here TraceWeave mainly confirms the
hypothesis from the waveform — and scan_structural_risks can statically pin
the offending line. Useful, but not where the moat is.
TraceWeave becomes the decisive — sometimes the only — way to localize when the answer is not in readable source:
In those cases the clock-sampled waveform facts — cycle-aligned sampling,
inspect_handshake, suggest_protocol_bundles, sweep_handshakes,
reconstruct_transactions, verify_window, diff_first_divergence,
period, trace_x_source, structural scanning — localize the failing stage
and time directly, where
reading source or grepping cannot reach. Reading the source is a strong
baseline; T