ToolsMCP
ainative-browser-mcp
Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- ainative-studio (GitHub)
- Prerequisites
- Install @ainative/browser-mcp from npm (stdio transport). Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 1.1.2 · updated
- Official links
Publisher’s description
AI-powered browser automation MCP — 6 tools for web interaction, extraction, and validation.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 1.1.2, registry status active. 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- ainative-studio (GitHub)
- Version observed
- 1.1.2
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.AINative-Studio%2Fainative-browser-mcp/versions/1.1.2
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Automate a web browser | Publisher description mentions “browser”, “automation”. | No connection check or task run. Capability is as described by the publisher. | Rule browser-automation matched: “browser”, “automation”. Rule browser-automation. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
@ainative/browser-mcp(npm, stdio)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.AINative-Studio/ainative-browser-mcp
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.