updated 2026-10-11 04:08 UTC

Perplexity MCP Server

Repository Website

The official MCP server implementation for the Perplexity API Platform

MCP Servers TypeScript Listed MIT

Is Perplexity MCP Server safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.9 / 10
Provenance None
Signed commits 28%
Last push 16d ago
Compare Perplexity MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Perplexity MCP Server scores 52.2/100 (Grade C), ranked #914 of 1371 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.9/10; 28% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How Perplexity MCP Server could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Perplexity MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/perplexityai/modelcontextprotocol, MIT, last pushed 2026-09-25. 28% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.9/10 (scanned Oct 2, 2026). The checks that decide who can get a change released:

    • Code Review4
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies6
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 4
    Contributors 6
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 6
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages None

    No registry package. Perplexity MCP Server is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Perplexity MCP Server.

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Perplexity MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Perplexity MCP Server compares in MCP Servers

  1. #513 Mac Control MCP 52.3 +0.1
  2. #514 Pulsemcp MCP Servers 52.3 +0.1
  3. #515 Perplexity MCP Server 52.2 this agent
  4. #516 MCP Server Zotero Dev 52.2 ±0
  5. #517 Ble MCP Server 52.1 −0.1

Bars show each HVTrust score; the tick marks Perplexity MCP Server’s 52.2.

Where the 52.2 comes from

HVTrust dimensions vs the MCP Servers average

52.2 / 100 · 100.0% confidence

Perplexity MCP Server MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.5 / 25
2.9 below avg 10.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
12.7 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
12.8 / 20
0.6 above avg 12.2
AdoptionLog-scaled stars · package downloads
8.2 / 20
0.8 above avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-09
Rank Moved
Rank dropped 14 spots (#888 → #902)
2026-10-04
Rank Moved
Rank rose 24 spots (#897 → #873)
2026-09-30
Rank Moved
Rank dropped 11 spots (#877 → #888)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.9/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for Perplexity MCP Server View MCP Servers Report missing data
61.3
Activity sub-score · out of 100
#515
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-11 04:08 UTC · Repo last pushed 16 days ago

Rank Trend

2026-09-29 2026-10-11

Activity & Reach

Stars
2.6k
Forks
381
Last Push
2026-09-25
16 days ago
Commits (4 wk)
2
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
6
Rank Change
▼6
was #908

Analysis

Activity Inputs

61.3 / 100
StarsRepository reach
20.4 / 30
FreshnessLast push recency
22.8 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
12.0 / 20

Common questions about Perplexity MCP Server

Public trust evidence for Perplexity MCP Server is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Perplexity MCP Server publish package provenance?
No published build provenance is currently detected for Perplexity MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Perplexity MCP Server have an OpenSSF Scorecard?
Perplexity MCP Server has an OpenSSF Scorecard score of 4.9/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Perplexity MCP Server actively maintained?
Maintained. Last push was 16 days ago.
What license does Perplexity MCP Server use?
Perplexity MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Perplexity MCP Server's commits signed?
28% of the last 100 commits to Perplexity MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Perplexity MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Perplexity MCP Server?

For maintainers

HVTrust scores Perplexity MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 33Score 2HVTrust 1Grade 1
2026-10-09
Rank Moved
Rank dropped 14 spots (#888 → #902)
2026-10-04
Rank Moved
Rank rose 24 spots (#897 → #873)
2026-09-30
Rank Moved
Rank dropped 11 spots (#877 → #888)
2026-09-26
Rank Moved
Rank dropped 16 spots (#858 → #874)
2026-09-25
Rank Moved
Rank rose 19 spots (#877 → #858)
2026-09-25
Activity Score Changed
Activity score up 6pts (62 → 68)
2026-09-24
Rank Moved
Rank dropped 16 spots (#861 → #877)
2026-09-23
Rank Moved
Rank dropped 546 spots (#315 → #861)
2026-09-22
Rank Moved
Rank dropped 10 spots (#305 → #315)
2026-09-21
Rank Moved
Rank rose 549 spots (#854 → #305)
2026-09-16
Rank Moved
Rank dropped 22 spots (#811 → #833)
2026-09-11
Rank Moved
Rank dropped 12 spots (#783 → #795)
2026-09-09
Rank Moved
Rank dropped 14 spots (#764 → #778)
2026-09-07
Rank Moved
Rank dropped 46 spots (#713 → #759)
2026-09-05
Rank Moved
Rank dropped 74 spots (#630 → #704)
2026-09-04
Rank Moved
Rank dropped 26 spots (#604 → #630)
2026-09-03
Rank Moved
Rank dropped 49 spots (#555 → #604)
2026-09-02
Rank Moved
Rank dropped 16 spots (#539 → #555)
2026-09-01
Rank Moved
Rank dropped 20 spots (#519 → #539)
2026-08-31
Rank Moved
Rank dropped 30 spots (#489 → #519)
2026-08-29
Rank Moved
Rank dropped 59 spots (#437 → #496)
2026-08-26
Rank Moved
Rank dropped 58 spots (#375 → #433)
2026-08-24
Rank Moved
Rank dropped 10 spots (#363 → #373)
2026-08-22
Rank Moved
Rank rose 14 spots (#378 → #364)
2026-08-19
Rank Moved
Rank dropped 15 spots (#364 → #379)
2026-08-17
Rank Moved
Rank rose 34 spots (#406 → #372)
2026-08-16
Rank Moved
Rank dropped 10 spots (#396 → #406)
2026-08-13
Rank Moved
Rank dropped 17 spots (#378 → #395)
2026-08-12
Rank Moved
Rank rose 15 spots (#393 → #378)
2026-08-10
Rank Moved
Rank dropped 20 spots (#372 → #392)
2026-08-08
Rank Moved
Rank dropped 90 spots (#280 → #370)
2026-07-27
Grade Changed
Trust grade D → C
2026-07-27
Rank Moved
Rank rose 48 spots (#327 → #279)
2026-07-27
HVTrust Changed
HVTrust up 7.3pts (46.2 → 53.5)
2026-07-27
Activity Score Changed
Activity score up 20pts (52 → 72)
2026-07-15
Rank Moved
Rank dropped 26 spots (#285 → #311)
2026-07-14
Rank Moved
Rank dropped 16 spots (#269 → #285)
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 52.2 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/perplexity-mcp-server.svg)](https://hvtracker.net/agents/perplexity-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/perplexity-mcp-server"><img src="https://hvtracker.net/badge/perplexity-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON