Brasspage Apify Actors vs io.github.AINative-Studio/ainative-browser-mcp
Brasspage Apify Actors is an MCP server published by brasspage.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.AINative-Studio/ainative-browser-mcp is an MCP server published by AINative-Studio. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-08. 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 |  Brasspage Apify Actors |  io.github.AINative-Studio/ainative-browser-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 1.1.2 Downloads/month (npm): 1 544 Downloads/week (npm): 399 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.1.4 Downloads/month (npm): 1 544 Downloads/week (npm): 399 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 | Brasspage Apify Actors | io.github.AINative-Studio/ainative-browser-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.apify.com) | On your machine (@ainative/browser-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | Not stated | github.com/ainative-studio/ainative-browser-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-22 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded less than an hour ago, requires authentication | 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
Brasspage Apify Actors
Six AI-built Apify Actors: ATS jobs, PDF OCR, Lighthouse audits, transcripts, Sheets, site audits
io.github.AINative-Studio/ainative-browser-mcp
AI-powered browser automation MCP — 6 tools for web interaction, extraction, and validation.
How to run each
Brasspage Apify Actors
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: Authorization header
io.github.AINative-Studio/ainative-browser-mcp As a local MCP server: npm package
claude mcp add --transport stdio ainative-browser-mcp -- npx -y @ainative/browser-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Brasspage Apify Actors 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: Brasspage Apify Actors · What it can do: io.github.AINative-Studio/ainative-browser-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.