io.github.lvsmanhole/clearscreen vs ScreenVerity
io.github.lvsmanhole/clearscreen is an MCP server published by lvsmanhole. Marketplaces we read that list it: 1 (Official MCP Registry). ScreenVerity is an MCP server published by williamblakecunningham-max. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.2.1 Downloads/month (npm): 148 Downloads/week (npm): 18 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 | io.github.lvsmanhole/clearscreen | ScreenVerity |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (clearscreen-mcp.mcpize.run/mcp) | On your machine (screenverity-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| 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/lvsmanhole/clearscreen-data | github.com/williamblakecunningham-max/screenverity-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-27 | no remote endpoint we check |
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
io.github.lvsmanhole/clearscreen
Screen people & companies against 12 US sanctions & exclusion lists (OFAC, LEIE, SAM, Medicaid).
ScreenVerity
Free U.S. exclusion, debarment and licence screening with a signed receipt of the lists checked.
How to run each
io.github.lvsmanhole/clearscreen As a remote MCP server
claude mcp add --transport http clearscreen https://clearscreen-mcp.mcpize.run/mcp
ScreenVerity As a local MCP server: npm package
claude mcp add --transport stdio screenverity-mcp -- npx -y screenverity-mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.lvsmanhole/clearscreen 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: io.github.lvsmanhole/clearscreen · What it can do: ScreenVerity · 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.