ToolsMCP
openwebninja-mcp
Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- openweb-ninja (GitHub)
- Prerequisites
- Install @openwebninja/mcp-server from npm (stdio transport). Declares 1 secret input. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 0.1.1 · updated
- Official links
Publisher’s description
Official MCP server for OpenWeb Ninja APIs - 40+ real-time web data and SERP APIs as MCP tools
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.1.1, registry status active. 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- openweb-ninja (GitHub)
- Version observed
- 0.1.1
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.OpenWeb-Ninja%2Fopenwebninja-mcp/versions/0.1.1
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Search the web with sources | Publisher description mentions “serp”. | No connection check or task run. Capability is as described by the publisher. | Rule web-search matched: “serp”. Rule web-search. |
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
@openwebninja/mcp-server(npm, stdio, 1 secret input)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.OpenWeb-Ninja/openwebninja-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.