Scite vs Tomesphere
A side-by-side look at the Scite and Tomesphere MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
SciteResearch · Remote HTTP/SSEGround answers in scientific literature. Search full text, evaluate trust, access full-text articles38FairAuth: not declaredT
TomesphereResearch · Remote HTTP/SSESearch 8.5M scientific papers with LLM TLDRs, citations, linked entities, figures, and full text.37FairAuth: not declaredVerdict: choose Scite for research work over a hosted endpoint; choose Tomesphere for research over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
SChoose Scite when
- You need dedicated capabilities in the Research domain.
- You prefer a remote HTTP/SSE transport.
TChoose Tomesphere when
- You need dedicated capabilities in the Research domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Scite | T Tomesphere |
|---|---|---|
| Category | Research | Research |
| Quality signal | 38/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | — |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Scite | View Tomesphere |
Tools & capabilities
Scite tools
No tool names declared yet. Check the project README from the listing page.
Tomesphere tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Scite
{
"mcpServers": {
"scite": {
"url": "https://scite.ai/mcp"
}
}
}
Tomesphere
{
"mcpServers": {
"tomesphere": {
"url": "https://tomesphere.com/mcp"
}
}
}
Frequently asked questions
Scite is categorized under Research and uses a remote HTTP/SSE transport. Tomesphere belongs to Research and uses a remote HTTP/SSE transport. Pick Scite for research work and Tomesphere for research.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Scite has no declared pricing — check the project's own site. Tomesphere has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add scite and tomesphere as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Scite has a quality signal of 38/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Tomesphere has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.