ToolsMCP
sendblue-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
- sendblue-api (GitHub)
- Prerequisites
- Install sendblue-browser-mcp from npm (stdio transport). Declares 1 secret input. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 0.2.3 · updated
- Official links
Publisher’s description
Drive a stealth-patched Chromium daemon: navigate, screenshot, eval JS, attach over CDP.
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 0.2.3, registry status active. 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- sendblue-api (GitHub)
- Version observed
- 0.2.3
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.sendblue-api%2Fsendblue-browser-mcp/versions/0.2.3
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Automate a web browser | Publisher description mentions “browser”, “chromium”, “navigate”, “screenshot”. | No connection check or task run. Capability is as described by the publisher. | Rule browser-automation matched: “browser”, “chromium”, “navigate”, “screenshot”. 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
sendblue-browser-mcp(npm, stdio, 1 secret input)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.sendblue-api/sendblue-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.