The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Webz.io News Search listing page.
Public SDKs for the hosted Webz.io News Search MCP server:
https://news-search-mcp.webz.io/mcp
The MCP server is the source of truth. These packages are thin clients. New filters and tools on the server show up at runtime through tools/list.
| Package | Registry | Path |
|---|---|---|
langchain-webz | PyPI | packages/langchain |
llama-index-tools-webz | PyPI | packages/llamaindex |
ag2-webzio | PyPI | packages/ag2 |
crewai-webzio | PyPI | packages/crewai |
@webz.io/ai-sdk | npm | packages/ai-sdk |
n8n-nodes-webz-news-search | npm | github.com/Webhose/n8n-nodes-webz-news-search |
webz_news_search | Dify Marketplace (.difypkg) | packages/dify |
The bundle in mcp-registry/ publishes the hosted server to
registry.modelcontextprotocol.io as
io.webz/news-search. Aggregators such as PulseMCP and Glama ingest the
official registry, so this listing propagates downstream automatically.
Publishing requires a one-time DNS TXT record on webz.io — see
mcp-registry/PUBLISHING.md.
No package. Groq's Responses API speaks remote MCP itself, so you pass the hosted server in tools and Groq runs tools/list and tools/call server side.
Reference implementation, runnable examples, and the groq-api-cookbook contribution bundle are in packages/groq.
Two paths:
n8n-nodes-webz-news-search): standalone workflows, structured article output, and optional use as an AI Agent tool.n8n/): no install step; connect an AI Agent directly to the MCP server so filters still come from tools/list at runtime.Setup steps and importable workflow templates are in n8n/.
Not a PyPI package. Dify Marketplace installs a .difypkg plugin from packages/dify. After the listing PR is merged, search for Webz News Search on marketplace.dify.ai. Dify v1.6+ can also add https://news-search-mcp.webz.io/mcp under Tools → MCP without a plugin.