elsevier-mcp

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Security

Grade A, and why

elsevier-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Origin

This is a copy

.claude-plugin/plugin.json · 36 lines

What it actually says

{
  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
  "name": "elsevier-mcp",
  "displayName": "Elsevier Research Tools",
  "version": "1.0.0",
  "description": "Give Claude access to Elsevier APIs (Scopus, ScienceDirect, and more). Search scholarly literature, retrieve abstracts and full-text articles, look up journals, authors, citations, and altmetrics.",
  "author": {
    "name": "kemalabut",
    "url": "https://github.com/kemalabuteliyte"
  },
  "homepage": "https://github.com/kemalabuteliyte/elsevier-mcp",
  "repository": "https://github.com/kemalabuteliyte/elsevier-mcp",
  "license": "MIT",
  "keywords": [
    "elsevier",
    "scopus",
    "sciencedirect",
    "academic",
    "research",
    "papers",
    "citations",
    "literature"
  ],
  "mcpServers": {
    "elsevier": {
      "command": "node",
      "args": ["${CLAUDE_PLUGIN_ROOT}/dist/bundle.cjs"],
      "env": {
        "ELSEVIER_API_KEY": "${ELSEVIER_API_KEY}",
        "ELSEVIER_INST_TOKEN": "${ELSEVIER_INST_TOKEN}",
        "ELSEVIER_ENABLE_ALL_TOOLS": "${ELSEVIER_ENABLE_ALL_TOOLS}"
      }
    }
  }
}

Contents

What it installs

The manifest is a name and a version. 1 skill, 1 MCP server travel with it, and installing the plugin installs all of them — 42 tokens a session between them. Each is measured on its own page, and each can be installed alone.

Files

What ships with it

1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

Related

Other plugins, from other repositories