Hyperbrowser vs Tribunal TJSC: Visualizar Certidão
Hyperbrowser is an MCP server published by hyperbrowserai. Marketplaces we read that list it: 1 (Docker MCP Catalog). Tribunal TJSC: Visualizar Certidão is an MCP server published by mcp-dir. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 |  Hyperbrowser |  Tribunal TJSC: Visualizar Certidão |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:11ed80138c33 Forks (GitHub): 75 Pulls (Docker Hub): 41 636 Stars (Docker Hub): 3 Stars (GitHub): 791 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.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 | Hyperbrowser | Tribunal TJSC: Visualizar Certidão |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 791 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 41 636 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 75 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/hyperbrowser) | Remote server (api.mcp.ai/p_tribunal_tjsc_obter_certidao) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 10 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/hyperbrowserai/mcp | github.com/mcp-dir/tribunal_tjsc_obter_certidao-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 days 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
Hyperbrowser
A MCP server implementation for hyperbrowser.
Tribunal TJSC: Visualizar Certidão
Tribunal TJSC: Visualizar Certificate, official-source lookup. Platform-hosted, pay per query with p
How to run each
Hyperbrowser As a local MCP server: Docker image
claude mcp add --env "HYPERBROWSER_API_KEY=<YOUR_HYPERBROWSER_API_KEY>" --transport stdio hyperbrowser -- docker run -i --rm -e HYPERBROWSER_API_KEY mcp/hyperbrowserRequires: HYPERBROWSER_API_KEY (secret)
Tribunal TJSC: Visualizar Certidão As a remote MCP server
claude mcp add --transport http tribunal-tjsc-obter-certidao-mcp https://api.mcp.ai/p_tribunal_tjsc_obter_certidaoCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Tribunal TJSC: Visualizar Certidão has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Tribunal TJSC: Visualizar Certidão publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Tribunal TJSC: Visualizar Certidão publish no settings it asks for, so we do not compare settings.
What it can do: Hyperbrowser · What it can do: Tribunal TJSC: Visualizar Certidão · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.