dev.turva/turva-mcp vs io.github.robertoyanguas-ops/assay
dev.turva/turva-mcp is an MCP server published by turva.dev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.robertoyanguas-ops/assay is an MCP server published by robertoyanguas-ops. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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 |  dev.turva/turva-mcp | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 0.4.2 No figure published 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 | dev.turva/turva-mcp | io.github.robertoyanguas-ops/assay |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.turva.dev/mcp) | Remote server (assay-207908449630.us-central1.run.app/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository | Not stated | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-16 |
| Endpoint at the last check (differs) | Responded 16 h ago | Responded 2 h ago |
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
dev.turva/turva-mcp
Read-only MCP server for turva.dev, an agent-readiness audit and advisory service.
io.github.robertoyanguas-ops/assay
A2A & MCP Pre-Flight Security: SHA-256 tool schema rug-pull detection and liveness grades.
How to run each
dev.turva/turva-mcp As a remote MCP server
claude mcp add --transport http turva-mcp https://mcp.turva.dev/mcpio.github.robertoyanguas-ops/assay As a remote MCP server
claude mcp add --transport http assay https://assay-207908449630.us-central1.run.app/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: dev.turva/turva-mcp · What it can do: io.github.robertoyanguas-ops/assay · Compare two other plugins
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.