Octagon Deep Research MCP vs Scite

A side-by-side look at the Octagon Deep Research MCP and Scite MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Octagon Deep Research MCP logoOctagon Deep Research MCPResearch · Local subprocess (stdio)Lightning-Fast, High-Accuracy Deep Research Agent44FairAuth: api key required
S
SciteResearch · Remote HTTP/SSE
Ground answers in scientific literature. Search full text, evaluate trust, access full-text articles38FairAuth: not declared

Verdict: choose Octagon Deep Research MCP for research work as a local process; choose Scite for research over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Octagon Deep Research MCP logoChoose Octagon Deep Research MCP when

  • You need dedicated capabilities in the Research domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: OCTAGON_API_KEY.
Explore Octagon Deep Research MCP

S
Choose Scite when

  • You need dedicated capabilities in the Research domain.
  • You prefer a remote HTTP/SSE transport.
Explore Scite

Feature & specification comparison

Rows where the two servers differ are marked.

SpecOctagon Deep Research MCP logoOctagon Deep Research MCP
S
Scite
CategoryResearchResearch
Quality signal44/100 · Fair38/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthAPI key requiredNot declared
PricingFreemiumNot declared
Required env varsOCTAGON_API_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars94—
Directory activity 2 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Octagon Deep Research MCP tools

No tool names declared yet. Check the project README from the listing page.

Scite 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.

Octagon Deep Research MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "octagonai-octagon-deep-research-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "octagon-deep-research-mcp"
      ],
      "env": {
        "OCTAGON_API_KEY": "YOUR_OCTAGON_API_KEY_HERE"
      }
    }
  }
}

Scite

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "scite": {
      "url": "https://scite.ai/mcp"
    }
  }
}

Frequently asked questions

Octagon Deep Research MCP is categorized under Research and uses a local stdio subprocess. Scite belongs to Research and uses a remote HTTP/SSE transport. Pick Octagon Deep Research MCP for research work and Scite 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.

Octagon Deep Research MCP is listed as freemium — a free tier with paid plans. Auth: api key required. Scite 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 octagonai-octagon-deep-research-mcp and scite as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Octagon Deep Research MCP has a quality signal of 44/100 (Fair) with 2 views, 0 installs and 94 GitHub stars. Scite has 38/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.