remote-access-mcp vs Vivado Red MCP
remote-access-mcp is an MCP server published by AmirAliManzar. Marketplaces we read that list it: 1 (npm registry (MCP servers)). Vivado Red MCP is an MCP server published by sinemortal. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  remote-access-mcp |  Vivado Red MCP |
|---|---|---|
| npm registry (MCP servers) | Listed Version: 4.6.12 Downloads/month (npm): 513 Downloads/week (npm): 123 Forks (GitHub): 0 Stars (GitHub): 4 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.5.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | remote-access-mcp | Vivado Red MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 4 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (remote-access-mcp) | On your machine (vivado-red-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/amiralimanzar/remote-access-mcp | github.com/sinemortal/vivado-red-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-12 | 2026-11-02 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
remote-access-mcp
Turn any laptop, desktop, VM, or server into a secure AI-agent workspace via MCP. Let ChatGPT, Claude, Grok, Qwen and other MCP clients read and edit files, run commands, test code, inspect systems, and complete real-world tasks.
Vivado Red MCP
Drive AMD Vivado from AI assistants, with Red Pitaya STEMlab 125-14 build and deploy flows.
How to run each
remote-access-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Vivado Red MCP As a local MCP server: PyPI package
claude mcp add --transport stdio vivado-red-mcp -- uvx vivado-red-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of remote-access-mcp publish no settings it asks for, so we do not compare settings.
What it can do: remote-access-mcp · What it can do: Vivado Red MCP · Compare two other plugins
Package data comes from the public npm registry (registry.npmjs.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.