Lexicon vs Scopus MCP
A side-by-side look at the Lexicon and Scopus MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Lexicon for research work over a hosted endpoint; choose Scopus MCP for research as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Lexicon when
- You need dedicated capabilities in the Research domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
LEXICON_API_KEY.
Choose Scopus MCP when
- You need dedicated capabilities in the Research domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SCOPUS_API_KEY. - You want tools like
query, count, sort.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Research | Research |
| Quality signal | 36/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | LEXICON_API_KEY | SCOPUS_API_KEY |
| Verified owner | Community listing |
Tools & capabilities
Lexicon tools
No tool names declared yet. Check the project README from the listing page.
Scopus MCP tools 6
querycountsortcoverDatescopus_idauthor_id
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.
Lexicon
{
"mcpServers": {
"lexicon": {
"url": "https://dbssearch.today/mcp/v1"
}
}
}
Scopus MCP
{
"mcpServers": {
"scopus-mcp": {
"command": "uvx",
"args": [
"scopus-mcp"
],
"env": {
"SCOPUS_API_KEY": "YOUR_SCOPUS_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Lexicon is categorized under Research and uses a remote HTTP/SSE transport. Scopus MCP belongs to Research and uses a local stdio subprocess. Pick Lexicon for research work and Scopus MCP 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.
Lexicon has no declared pricing — check the project's own site. Scopus MCP 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 lexicon and scopus-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Lexicon has a quality signal of 36/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Scopus MCP has 53/100 (Good) with 1 views, 0 installs and 46 GitHub stars.