mcp-server-ollama-deep-researcher

Related Servers

Alternatives to mcp-server-ollama-deep-researcher

No user-submitted related servers found.

Related Servers

research
Web Scraping Search Research & Data
id5463
A
license
Not graded
quality
D
maintenance
Multi-purpose research MCP server integrating web search, deep research, web scraping, research methodology routing, and GPT Researcher report generation.
Updated 3 months ago (2026-07-10 05:02 UTC)
MIT
myscrape
Browser Automation Web Scraping Search
Bonifatius94
A
license
Not graded
quality
C
maintenance
A self-contained web-research MCP server that lets local LLM agents search, fetch, and synthesize web content using tools like web_search, web_fetch, and web_research.
Updated 5 days ago (2026-09-23 18:33 UTC)
2
MIT
deep-research
Agent Orchestration Autonomous Agents
troyhantech
A
license
Not graded
quality
D
maintenance
Enables deep research tasks using a multi-agent architecture that integrates any LLM and MCP tools. Available via MCP stdio, streamable HTTP, and SSE transports.
Updated 3 months ago (2026-06-15 01:55 UTC)
17
MIT
bathys
Browser Automation Search RAG Systems
Korrnals
A
license
A
quality
A
maintenance
Enables AI agents to run local deep-research workflows via a single MCP stdio server, combining web search, page extraction, query-aware distillation, and caching without cloud quotas. It exposes tools for deep research, search, and single or batch URL reading.
Updated 13 days ago (2026-09-15 21:25 UTC)
6
119 PyPI
MIT
tavily_mcp_server_for_all
Search Web Scraping Research & Data
La0bALanG
F
license
Not graded
quality
C
maintenance
MCP server exposing 8 Tavily tools (web search, fetch, crawl, map, QnA, context, and deep research) via Streamable HTTP for AI assistants to perform live web retrieval and research.
Updated a month ago (2026-08-19 03:12 UTC)
1
-
WebQuest MCP
Browser Automation Web Scraping
mustafametesengul
A
license
Not graded
quality
B
maintenance
A Model Context Protocol server that exposes powerful web search and scraping tools to AI agents and MCP-compatible clients.
Updated 8 months ago (2026-02-12 20:56 UTC)
Apache 2.0

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.3/5.0

Scored 2026-04-18 11:35 across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: configure sets parameters, get_status checks progress, and research initiates the core workflow. An agent can easily distinguish between setup, monitoring, and execution functions.

Naming Consistency5/5

All three tools follow a consistent verb_noun pattern (configure, get_status, research), with clear and predictable naming. There are no deviations in style or convention across the set.

Tool Count3/5

With only 3 tools, the server feels thin for a 'deep researcher' domain that might benefit from more granular operations like refining queries or managing results. However, the core workflow is covered, making it borderline appropriate.

Completeness3/5

The tools cover the basic research lifecycle (configure, execute, monitor), but there are notable gaps such as no way to retrieve or export past research results, modify parameters mid-research, or handle errors. This could limit agent effectiveness in complex scenarios.