Research Toolkit
Related Servers
Alternatives to Research Toolkit
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceA local MCP server that gives AI agents structured task planning, execution tracking, and guided research workflows.168 npmMIT
- AlicenseAqualityBmaintenanceAn MCP server that transforms books into agent-callable skill packages, enabling AI agents to use books as guides for evidence, procedures, and tutoring.201MIT
- FlicenseNot gradedqualityCmaintenanceA self-extending MCP server that enables AI agents to browse the web, execute shell and Node snippets, automate browser workflows, access files and git, communicate with other agents, and use dozens of domain-specific calculation and research tools.-
- AlicenseBqualityDmaintenanceA standalone MCP server that enables research (web search, URL fetch, news), workspace management (file operations, command execution), and self-extension via markdown-based skills.21MIT
- AlicenseNot gradedqualityDmaintenanceA research MCP server that enables AI agents to query the internet using multiple sources like SearXNG, GitHub, Reddit, and YouTube, and returns synthesized answers with citations.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that lets AI agents search, view, install, and validate skills from the skillhub registry through tool calls.MIT
TDQS
Scored across 8 tools
Most tools target clearly distinct stages (start, save, review, finish, check_draft, check_reviewer). The one soft boundary is research_status vs research_guide, both of which read stage methods, distinguished only by 'with a task' vs 'without a task' — a subtle but workable split.
All tools use a consistent research_ prefix with largely verb-style suffixes (start, save, review, finish, check_draft, check_reviewer). Two are noun-like (status, guide), a minor deviation from the otherwise predictable verb_noun pattern.
Eight tools is well-scoped for a staged research workflow, with each tool mapping to a recognizable step (brief, save, status, guide, review, finish, two local checks). No redundancy or filler.
The set covers the full lifecycle — brief creation, object saving, progress reading, guidance, review, delivery/finish, and local validation checks. It lacks any cleanup/deletion or export/teardown operation, but core workflows have no dead ends.