← MCP server and skill grades

modelcontextprotocol

perplexityai/modelcontextprotocol

A
Type
MCP server
Scanned
Nov 12, 2026
Version
cd1d27cffe56
Files read
30

This MCP server connects an AI assistant to Perplexity's API for live web search, question answering, reasoning, and deep research. Its main risk is in the optional self-hosted HTTP mode, which has no built-in client authentication and lets anyone who can reach the port spend your Perplexity API credits if exposed beyond localhost without an authenticating proxy.

What it can reach

Secrets
Reads PERPLEXITY_API_KEY and optional proxy URLs (PERPLEXITY_PROXY, HTTPS_PROXY, HTTP_PROXY) from environment variables to authenticate outbound API calls.
Network
Sends search queries and conversation messages over HTTPS to api.perplexity.ai (or a custom PERPLEXITY_BASE_URL), and optionally listens on TCP port 8080 when started in HTTP mode.

Findings

2 low
  1. LowSelf-hosted HTTP mode has no client authentication

    src/http.ts:108

    When started in HTTP mode (dist/http.js or Docker), the /mcp endpoint does not require any password, token, or API key from callers. By default it binds to 127.0.0.1 and enforces Host and Origin allowlists so websites and remote machines cannot reach it, only other local processes on the same computer. However, README.md recommends HTTP mode for cloud or shared deployments and shows how to bind to 0.0.0.0 without repeating SECURITY.md's warning that inbound requests are unauthenticated, which would let anyone who can reach the server run queries using your Perplexity API quota.

    Fix: Add optional Bearer token authentication to src/http.ts (for example via an MCP_AUTH_TOKEN environment variable) and warn in README.md's Self-Hosted HTTP Mode section that an authenticating reverse proxy is required when exposing the port.

  2. LowPlugin manifests run an unpinned npm package at startup

    mcp.json:7

    Both mcp.json and .claude-plugin/marketplace.json start the server with npx -y @perplexity-ai/mcp-server without pinning a package version such as @1.4.0. Even when a user installs a specific release of the plugin, npx can download and execute a newer version published to npm later, increasing exposure if a future npm release is ever compromised.

    Fix: Pin the exact version in mcp.json and .claude-plugin/marketplace.json (for example, @perplexity-ai/mcp-server@1.4.0) and check version sync in CI.