MCP Safety Board

← All servers

MCP Safety Board · server report · November 2026

openags/paper-search-mcp

A
90 / 100
Grade A · ★ 3,090 · Python checked by hand

How the score was worked out

Starts at 100. Each line shows a check from the method and the points it took off.
CheckWhat was foundPoints
Risky tools labelledAll 1 tools that look like they delete, write or run things declare destructiveHint or readOnlyHint.0
Tools with any label74 of 74 tools (100%) carry any annotation; half or more.0
README install commandThe README tells users to launch the server with npx / bunx / uvx / pnpm dlx without a pinned version (or with @latest).−10
Committed configNo committed MCP config with an unpinned package, a moving tag, a broad filesystem root, a privileged docker server or plain http.0
Score100 minus the penalties above (never below 0).90

Changes that would raise this grade

  1. +10Pin the version in the README install command (pkg@1.2.3 or pkg==1.2.3, not @latest). Alone, this gives 100 (A).

What was checked

Commit checked
cab1b5cc276a
Repository
github.com/openags/paper-search-mcp
Tools found
74, of which 74 carry any label (100%)
Risky tools
1, of which 1 labelled
README install
not pinned
Last push
2026-10-02

Static reading of this one commit. No code was installed or run. This is a hygiene grade, not a security audit.

Maintainer?

Fixed something, or think a count is wrong? Request a re-check (opens a GitHub issue). Re-checks run on the latest commit.

README badge

MCP safety: A
[![MCP safety: A](https://mcp-safety-board.pages.dev/badge/openags--paper-search-mcp.svg)](https://mcp-safety-board.pages.dev/s/openags--paper-search-mcp.html)

Want a written review of your agent's tools and permissions?

48-hour written review. Which tools your agent can call, what each one can change, which need a confirmation step, and what to lock down first. Send a message to start.