AIHawk vs Hyperbrowser
AIHawk is an MCP server published by feder-cr. Marketplaces we read that list it: 1 (Official MCP Registry). Hyperbrowser is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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 |  AIHawk |  Hyperbrowser |
|---|---|---|
| Official MCP Registry | Listed Version: 0.69.2 Forks (GitHub): 4 942 Stars (GitHub): 32 182 Not marked · First seen |
Listed Version: 0.1.2 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 | AIHawk | Hyperbrowser |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 32 182 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 4 942 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (aihawk) | Remote server (gateway.pipeworx.io/hyperbrowser/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/feder-cr/aihawk_mcp_server | github.com/pipeworx-io/mcp-hyperbrowser |
| 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
AIHawk
AI browser agent: browses, clicks, types, and reads real web pages from plain-English instructions.
Hyperbrowser
Hyperbrowser MCP — wraps the Hyperbrowser AI-agent browsing API
How to run each
AIHawk As a local MCP server: PyPI package
claude mcp add --transport stdio aihawk -- uvx aihawkHyperbrowser As a remote MCP server
claude mcp add --transport http hyperbrowser https://gateway.pipeworx.io/hyperbrowser/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Hyperbrowser 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: AIHawk · What it can do: Hyperbrowser · 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.