scibot-mcp
Related Servers
Alternatives to scibot-mcp
No user-submitted related servers found.
Related Servers
FlicenseNot gradedqualityBmaintenanceConnects AI agents to a hosted remote MCP endpoint that searches academic papers, verifies references and retraction status, retrieves research datasets, grants, and biological or chemical data, and generates scientific figures across 50+ upstream sources. Supports OAuth sign-in with per-tool credit accounting, structured error reporting, and source attribution for results.-- AlicenseNot gradedqualityAmaintenanceEnables clients to list and retrieve skateboard-physics benchmark tasks, score submitted answers deterministically, run the benchmark, and inspect provenance via MCP tools.MIT
- AlicenseAqualityCmaintenanceEnables MCP clients to control the local Open Science research application, including creating projects, starting or continuing research sessions, inspecting progress and plans, canceling runs, and reading generated artifacts.12Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables to run structured QuReDec decision briefs from inside MCP-compatible clients, submitting questions and receiving evidence-backed recommendations with citations.18 PyPIMIT
- AlicenseAqualityCmaintenanceMCP server that wraps the Brave Answers API, enabling synchronous Q&A and asynchronous deep research with job submission, status polling, and result retrieval.4MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to interact with a local-first research knowledge workbench, supporting literature search, evidence-grounded Q&A, and reference export.2AGPL 3.0
TDQS
Scored across 14 tools
Most tools have clearly distinct purposes, especially the question lifecycle and deletion operations. Minor overlap exists between scibot_account and scibot_token_history (both report token balance) and between scibot_check_question and scibot_read_answer (both can surface finished answers), but descriptions are enough to disambiguate with careful reading.
All tools share the scibot_ prefix and snake_case, and mutations generally use clear verb_noun names like ask_question, cancel_question, and delete_conversation. The main inconsistency is that read/list operations use plain nouns such as account, settings, conversations, and queue_status instead of a consistent get_ or list_ prefix, and conversation vs. conversations is mildly confusing.
At 14 tools, the server is well-scoped for a service that covers queue-based Q&A, persistent answers, account settings, token history, and conversations. Each tool represents a meaningful operation, and the count is comfortably within the ideal 3-15 range.
The core one-shot question lifecycle is well covered: ask, check, cancel, read, list, delete, and visibility. However, the conversation feature is incomplete: the server can list, read, and delete conversations but provides no tool to create or continue one, leaving that part of the surface as a dead end.