Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Vivado Red MCP

PYPI · VIVADO-RED-MCP

Drive AMD Vivado from AI assistants, with Red Pitaya STEMlab 125-14 build and deploy flows.

Available components

52 Trust /100

Last scanned (1 hour ago)

Scores higher than 56% of PyPI servers

Category Developer Tools

Trust breakdown (7 categories)

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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 2 of 39 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 6014 tokens (~64/item across 93 items; 93 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 80% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_breakpoints" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 93 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

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.

  • 5 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 3 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 52

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Analysed pypi/vivado-red-mcp@0.5.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 39 packages
Packages resolved 39
Stale 2
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 93 exposed · ~6,014 tokens

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 →

Tool Tokens
add_breakpoint ~32

Add a breakpoint on signal edge or change.

NameTypeReqDescription
conditionstring––
signalstringyes–

No output schema declared.

No examples provided.

add_constraints ~49

Add XDC constraint files to the current project.

NameTypeReqDescription
filesarrayyesAbsolute paths to .xdc files
filesetstring–Target fileset (default: constrs_1)

No output schema declared.

No examples provided.

add_ip_to_bd ~133

Add an IP core to the current block design (`create_bd_cell -type ip -vlnv ...`). If `config` is provided, the CONFIG.* keys are applied via set_property -dict.

NameTypeReqDescription
cell_namestringyesInstance name (e.g. 'processing_system7_0')
configobject–Dict of CONFIG.* properties (e.g. {'CONFIG.PCW_USE_M_AXI_GP0': '1'})
vlnvstringyesVendor:Library:Name:Version (e.g. 'xilinx.com:ip:processing_system7:5.5')

No output schema declared.

No examples provided.

add_module_to_bd ~126

Add an RTL module (Verilog/VHDL already in the project, see add_sources) to the current block design as a module-reference cell (`create_bd_cell -type module -reference`). Optional `config` sets its parameters, e.g. {'CONFIG.WIDTH': '8'}; string parameters keep their quotes, e.g. {'CONFIG.init': '"0011"'}.

NameTypeReqDescription
cell_namestringyesInstance name in the BD
configobject–Dict of CONFIG.* parameters
modulestringyesTop module name of the RTL

No output schema declared.

No examples provided.

add_signals_to_wave ~25

Add signals to the waveform viewer.

NameTypeReqDescription
signalsarrayyes–

No output schema declared.

No examples provided.

add_sources ~86

Add HDL source files (.v/.sv/.vhd) to the current project. Optionally sets the top module and updates compile order.

NameTypeReqDescription
filesarrayyesAbsolute paths to HDL source files
filesetstring–Target fileset (default: sources_1)
set_topstring–If given, set this module as project top after adding files

No output schema declared.

No examples provided.

apply_ps7_preset ~102

Apply the Zynq-7000 processing_system7 board preset to a PS7 cell — wires FIXED_IO / DDR / clocks per the board definition. Equivalent to clicking 'Run Block Automation' on a freshly added PS7 in the GUI.

NameTypeReqDescription
apply_board_presetboolean–Whether to apply the current board preset (default: true)
cellstring–PS7 cell name (default: 'processing_system7_0')

No output schema declared.

No examples provided.

assign_bd_address ~23

Auto-assign addresses in the BD address editor (assign_bd_address).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

auto_connect_axi ~98

Use `apply_bd_automation -rule xilinx.com:bd_rule:axi4` to wire an AXI master to a slave (inserts AXI interconnect + clock/reset hookups).

NameTypeReqDescription
masterstringyesAXI master intf pin
optionsobject–Optional extra -config key/value pairs (e.g. {'Clk_master': 'Auto'})
slavestringyesAXI slave intf pin

No output schema declared.

No examples provided.

check_session_health ~47

Verify the Vivado process is responsive. With auto_recover=true the session is restarted if it hangs.

NameTypeReqDescription
auto_recoverboolean–Restart session if unhealthy (default: true)

No output schema declared.

No examples provided.

close_bd_design ~19

Close the currently open block design (without deleting).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

close_hw_manager ~14

Close the Hardware Manager.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

close_project ~14

Close the currently open project.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

close_simulation ~14

Close the current simulation.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

configure_bd_cell ~89

Set CONFIG.* properties on an existing block-design cell (set_property -dict). Use for settings that must be applied after creation or in a separate step, e.g. importing a PS7 board preset: {'CONFIG.PCW_IMPORT_BOARD_PRESET': '<path>/red_pitaya.xml'}.

NameTypeReqDescription
cell_namestringyes–
configobjectyesDict of CONFIG.* properties

No output schema declared.

No examples provided.

configure_ip ~57

Set CONFIG.* properties on an existing IP via set_property -dict.

NameTypeReqDescription
configobjectyesDict of CONFIG.* keys to values (e.g. {'CONFIG.PRIM_IN_FREQ': '125'})
module_namestringyes–

No output schema declared.

No examples provided.

connect_bd_intf_net ~64

Connect two AXI/interface pins in the current block design.

NameTypeReqDescription
intf_fromstringyese.g. 'processing_system7_0/M_AXI_GP0'
intf_tostringyese.g. 'axi_gpio_0/S_AXI'

No output schema declared.

No examples provided.

connect_bd_net ~62

Connect two scalar pins/ports in the current block design.

NameTypeReqDescription
pin_fromstringyese.g. 'processing_system7_0/FCLK_CLK0'
pin_tostringyese.g. 'axi_gpio_0/s_axi_aclk'

No output schema declared.

No examples provided.

connect_hw_server ~54

Connect to a hw_server (cs_server). Default URL is localhost:3121 — the value Vivado uses when running hw_server locally.

NameTypeReqDescription
urlstring–host:port (default: localhost:3121)

No output schema declared.

No examples provided.

create_bd_port ~221

Create a top-level port on the current block design. Scalar or vector (`from`/`to`) via create_bd_port, or an interface port when `vlnv` is given (create_bd_intf_port, e.g. the XADC 'xilinx.com:interface:diff_analog_io_rtl:1.0'). Port names must match the constraints (XDC) of the board.

NameTypeReqDescription
directionstring–Direction for a plain port (default: I)
frominteger–MSB index for a vector port (e.g. 7)
modestring–Interface mode (default: Slave): Master, Slave, ...
namestringyesPort name (e.g. 'led_o')
tointeger–LSB index for a vector port (default: 0)
typestring–Optional port type: clk, rst, ce, intr, data, undef
vlnvstring–Interface VLNV: creates an interface port instead

No output schema declared.

No examples provided.

create_block_design ~94

Create a new block design and make it current. Optionally sets the board_part property on the project beforehand (board_part requires the BSP to be installed in Vivado).

NameTypeReqDescription
board_partstring–Optional vendor:board:part string (e.g. 'digilentinc.com:arty-a7-35:part0:1.0')
namestringyesBlock design name (no .bd)

No output schema declared.

No examples provided.

create_ip ~126

Create an IP from the Xilinx IP catalog. Generates a .xci file in the project's IP sources fileset. Use configure_ip + generate_ip_target afterwards, then run synth_ip if you want out-of-context synthesis.

NameTypeReqDescription
ip_namestringyesCatalog name (e.g. 'clk_wiz')
librarystring–default: ip
module_namestringyesInstance/module name on disk (e.g. 'clk_wiz_0')
vendorstring–default: xilinx.com
versionstring–Optional explicit version

No output schema declared.

No examples provided.

create_project ~140

Create a new Vivado project on disk in project mode. Defaults to the Red Pitaya STEMlab 125-14 part (xc7z010clg400-1). Call add_sources / add_constraints next, then run_synthesis.

NameTypeReqDescription
directorystringyesParent directory; project created at <directory>/<name>
forceboolean–Overwrite existing project (default: true)
namestringyesProject name
partstring–Xilinx part number (default: xc7z010clg400-1)
target_languagestring–Verilog or VHDL (default: Verilog)

No output schema declared.

No examples provided.

create_redpitaya_project_rtl ~151

One-shot composite: create project -> add HDL sources -> apply XDC -> synth -> impl -> write_bitstream -> generate .bit.bin. Stops on the first failing stage and returns a structured payload.

NameTypeReqDescription
boardstring–default: red_pitaya_125_14
directorystringyes–
extra_xdc_filesarray––
impl_timeoutinteger––
jobsinteger––
namestringyes–
synth_flagsstring––
synth_timeoutinteger––
top_modulestringyes–
verilog_filesarrayyes–
xdc_variantstring––

No output schema declared.

No examples provided.

deploy_to_redpitaya ~293

Copy a .bit.bin to a Red Pitaya over SSH/SCP and load it into the FPGA. Uses /dev/xdevcfg (works on Red Pitaya OS 1.04 + 2.00) or fpgautil (OS 2.00). No Vivado session required.

NameTypeReqDescription
bit_bin_pathstringyesAbsolute path to the local .bit.bin produced by generate_cfgmem
connect_timeoutinteger–SSH connect timeout in seconds (default: 10)
hoststringyesRed Pitaya IP or hostname (e.g. '192.168.1.100' or 'rp-f0abcd.local')
keep_remoteboolean–Leave the .bit.bin on the board after loading (default: false → rm)
key_filenamestring–Path to an SSH private key. If set, overrides password auth.
methodstring–Loader: 'xdevcfg' (default, both OS) or 'fpgautil' (OS 2.00)
passwordstring–SSH password (default: 'root' — Red Pitaya factory default)
portinteger–SSH port (default: 22)
remote_pathstring–Remote .bit.bin path (default: /tmp/<basename>)
userstring–SSH user (default: 'root')

No output schema declared.

No examples provided.

generate_bd_wrapper ~108

Generate the HDL wrapper for a block design and (by default) add it to sources_1 and set it as project top. Implements the canonical pattern: make_wrapper -files <bd> -top; add_files -norecurse <wrapper>; set_property top <wrapper> [current_fileset]; update_compile_order.

NameTypeReqDescription
bd_namestringyesBlock design name (no .bd)
set_topboolean–Also set the wrapper as project top (default: true)

No output schema declared.

No examples provided.

generate_bitstream ~59

Generate bitstream — `launch_runs impl_1 -to_step write_bitstream` -> wait_on_run. Returns ground-truth run status and the .bit path.

NameTypeReqDescription
timeoutinteger–Timeout in seconds (default: 3600)

No output schema declared.

No examples provided.

generate_cfgmem ~76

Convert a .bit into a raw binary image (.bit.bin) loadable via /dev/xdevcfg on the Red Pitaya. Use after generate_bitstream.

NameTypeReqDescription
bit_filestringyesAbsolute path to input .bit
outputstring–Output .bit.bin path (default: <bit_file>.bin)

No output schema declared.

No examples provided.

generate_full_report ~81

Generate a full Vivado report to a file. Use when inline reports get truncated or you need the complete output. Returns a report_id usable with read_report_section.

NameTypeReqDescription
optionsobject–Report-specific options (e.g. {hierarchical: true})
output_filestring–Optional custom output path
report_typestringyes–

No output schema declared.

No examples provided.

generate_ip_target ~44

Generate IP output products (synthesis + simulation by default).

NameTypeReqDescription
module_namestringyes–
targetsarray–default: ['synthesis', 'simulation']

No output schema declared.

No examples provided.

get_board_info ~69

Get bundled metadata for a board: part, LED pinout, absolute XDC paths, default synth flags. Use the returned absolute_path values with add_constraints. No Vivado session required.

NameTypeReqDescription
boardstringyesBoard identifier, e.g. 'red_pitaya_125_14'

No output schema declared.

No examples provided.

get_cells ~44

Search for cells/instances by pattern.

NameTypeReqDescription
limitinteger–Max results (default: 100)
patternstring–Wildcard pattern (default: '*')

No output schema declared.

No examples provided.

get_clocks ~19

Get clock information and constraints (report_clocks).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_design_hierarchy ~62

Get the design hierarchy (modules and instances), optionally filtered.

NameTypeReqDescription
instance_patternstring–Wildcard pattern (e.g., '*cpu*', 'core/alu/*')
max_depthinteger–Max hierarchy depth (default: 3)

No output schema declared.

No examples provided.

get_host_status ~33

Get host hostname, free memory, and session state. Useful to check there is enough RAM before launching synthesis/implementation.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_messages ~40

Get Vivado messages filtered by severity (error/critical/warning/all).

NameTypeReqDescription
severitystring–all (default) | error | critical | warning

No output schema declared.

No examples provided.

get_nets ~46

Search for nets by pattern (default '*').

NameTypeReqDescription
limitinteger–Max results (default: 100)
patternstring–Wildcard pattern (default: '*')

No output schema declared.

No examples provided.

get_ports ~18

Get top-level I/O ports of the design.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_project_info ~23

Get name, part, target language, directory of the open project.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_scopes ~29

List child scopes (hierarchy) in the simulation.

NameTypeReqDescription
parentstring–default: /

No output schema declared.

No examples provided.

get_signal_value ~42

Get current value of a signal in simulation.

NameTypeReqDescription
radixstring–Display radix (default: hex)
signalstringyesHierarchical signal path

No output schema declared.

No examples provided.

get_signal_values ~47

Get values of multiple signals matching a wildcard pattern (max 50).

NameTypeReqDescription
patternstringyesSignal pattern, e.g. /tb/dut/*
radixstring––

No output schema declared.

No examples provided.

get_simulation_messages ~25

Get simulation log messages filtered by severity.

NameTypeReqDescription
severitystring––

No output schema declared.

No examples provided.

get_simulation_objects ~38

List simulation objects in a scope (signals/ports/internal).

NameTypeReqDescription
filterstring––
scopestring–default: /

No output schema declared.

No examples provided.

get_simulation_time ~19

Get the current simulation time (current_time).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_synthesis_errors_parsed ~83

Return structured errors and critical warnings from a run's log (default: synth_1), plus those of every failed run (e.g. out-of-context IP runs). Use after run_synthesis fails to get a clean actionable list.

NameTypeReqDescription
max_itemsinteger–default: 50
runstring–default: synth_1

No output schema declared.

No examples provided.

get_timing_paths ~151

Get failing/critical timing paths. Returns structured summary by default; use detail_level=standard|full for the raw text too.

NameTypeReqDescription
clockstring–Filter by clock domain
detail_levelstring–summary (default) | standard | full
from_pinstring–Filter -from pattern
num_pathsinteger–Number of paths (default: 10)
path_typestring–setup (default) or hold
slack_thresholdnumber–Only show paths with slack < this (default: 0 = failing paths)
throughstring–Filter -through pattern
to_pinstring–Filter -to pattern

No output schema declared.

No examples provided.

get_timing_summary ~78

Get timing summary (WNS, TNS, WHS, THS). Returns parsed metrics by default. Use generate_full_report for raw output.

NameTypeReqDescription
detail_levelstring–summary | standard (+ truncated raw) | full (+ complete raw)
report_typestring–summary (default), setup, hold, or all

No output schema declared.

No examples provided.

get_utilization ~81

Resource utilization (LUT/FF/BRAM/DSP/IO). Parsed only by default.

NameTypeReqDescription
detail_levelstring––
hierarchicalboolean–Hierarchical breakdown (default: false)
module_filterstring–Wildcard for hierarchical filter
threshold_percentnumber–Mark resources below this util%% as below_threshold

No output schema declared.

No examples provided.

get_vivado_doc ~130

Look up a topical Vivado documentation summary bundled with this server. Returns markdown content + upstream URL. Known topics: block_design, ps7_zynq, timing_constraints, synthesis_strategies, simulation_xsim, red_pitaya_125_14, redpitaya_ps_pl_flow, tcl_quoting, hw_manager, ip_integrator, pitfalls_2020_1.

NameTypeReqDescription
topicstringyesTopic name; see KNOWN_TOPICS in the tool description
versionstring–Target Vivado version (cosmetic, default '2020.1')

No output schema declared.

No examples provided.

Install

How do I install the Vivado Red MCP server?

Vivado Red MCP runs locally as a PyPI package, launched with uvx vivado-red-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · vivado-red-mcp

# add to Claude Code
claude mcp add sinemortal-vivado-red-mcp -- uvx vivado-red-mcp
Common questions

What is the Vivado Red MCP server?

Vivado Red MCP is listed in the public MCP registry as io.github.sinemortal/vivado-red-mcp. Drive AMD Vivado from AI assistants, with Red Pitaya STEMlab 125-14 build and deploy flows. This page covers its PyPI package (vivado-red-mcp).

Is the Vivado Red MCP server safe to use?

Vivado Red MCP scores 52 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 Vivado Red MCP server expose?

Vivado Red MCP exposes 93 tools: start_session, stop_session, session_status, check_session_health, get_host_status, and 88 more. Their descriptions and schemas cost roughly 6,014 tokens of context every time the server is loaded.

Is the Vivado Red MCP server still maintained?

Vivado Red MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Vivado Red MCP server under?

Vivado Red MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.