com.mcparmory/linkup vs Agent-readiness check
com.mcparmory/linkup is an MCP server published by mcparmory.com. Marketplaces we read that list it: 1 (Official MCP Registry). Agent-readiness check is an MCP server published by wondaverse.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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 |  com.mcparmory/linkup | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.2 Downloads/month (PyPI): 805 Downloads/week (PyPI): 152 Forks (GitHub): 4 Stars (GitHub): 32 Not marked · First seen |
Listed Version: 1.0.0 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 | com.mcparmory/linkup | Agent-readiness check |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 32 | No figure on GitHub |
| Forks (GitHub) (differs) | 4 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcparmory-linkup) | Remote server (wondaverse.com/check/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/mcparmory/registry | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-30 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 16 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
com.mcparmory/linkup
Search the web and fetch pages with sourced results, optimized for AI agents
Agent-readiness check
Checks a website for AI agents: robots.txt, llms.txt, MCP, A2A. Ranked fixes, text to paste.
How to run each
com.mcparmory/linkup As a local MCP server: PyPI package
claude mcp add --transport stdio linkup -- uvx mcparmory-linkupAgent-readiness check As a remote MCP server
claude mcp add --transport http agent-readiness https://wondaverse.com/check/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Agent-readiness check has a remote endpoint we 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: com.mcparmory/linkup · What it can do: Agent-readiness check · 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.