Is Perplexity MCP Server safe to use?

Perplexity MCP Server has an HVTrust score of 56.5/100 (Grade C), ranked #372 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Perplexity MCP Server?

Perplexity MCP Server scores 56.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 2.4k GitHub stars and is categorized under MCP Servers.

Perplexity MCP Server

perplexityai/modelcontextprotocol

The official MCP server implementation for the Perplexity API Platform

MCP Servers TypeScript Grade C Listed MIT

56.5/100

Rank #372 of 1204

Compare Perplexity MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-07-30 · 10d ago

Recent change

Rank +2

Is Perplexity MCP Server safe? Perplexity MCP Server scores 56.5/100 (Grade C), ranked #372 of 1204 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.8/10; 33% of recent commits are signed; last pushed 2026-07-30. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#118 Windows MCP — 56.9 (C) → #119 Qdrant MCP Server — 56.7 (C) → #121 Xcode: MCP Bridge Wrapper for Cursor — 56.5 (C) → #122 GPU MCP Server — 56.1 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-08

Rank Moved

Rank dropped 90 spots (#280 → #370)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → declared

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, Perplexity

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.8/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

74.2

Activity sub-score · out of 100

#120

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 →

Activity & Reach

Stars

2.4k

Forks

367

Last Push

2026-07-30

10 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #370

Analysis

HVTrust Dimensions vs MCP Servers

56.5 / 100 · 100.0% confidence

Perplexity MCP Server MCP Servers average (718 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

7.6 / 25

2.5 above avg 5.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.5 below avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

12.6 / 17

3.8 above avg 8.8

Maintenance60% last-push freshness · 40% commit activity

17.2 / 20

4.7 above avg 12.5

AdoptionLog-scaled stars · package downloads

8.1 / 20

2.6 above avg 5.5

Activity Inputs

74.2 / 100

StarsRepository reach

20.3 / 30

FreshnessLast push recency

23.6 / 25

ActivityRecent commits

18.2 / 25

CommunityFork signal

11.9 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.8 / 10

OpenSSF Scorecard · scanned Aug 9, 2026

Signed Commits

33%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 9

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

Is Perplexity MCP Server safe?

Perplexity MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

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.8/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 10 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?

33% 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

How this surface has changed

Detected changes to Perplexity MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → declared

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, Perplexity

2026-07-13

Tool Surface Changed

Detected tool/plugin surface changed: none → marketplace

2026-07-13

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-07-13

Activity Resumed

Activity resumed

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

2026-08-08

Rank Moved

Rank dropped 90 spots (#280 → #370)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → declared

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, Perplexity

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)

2026-07-13

Tool Surface Changed

Detected tool/plugin surface changed: none → marketplace

2026-07-13

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-07-13

Activity Resumed

Activity resumed

2026-07-13

Rank Moved

Rank rose 65 spots (#334 → #269)

2026-07-13

HVTrust Changed

HVTrust up 38.5pts (11.4 → 49.9)

2026-07-13

Activity Score Changed

Activity score up 61pts (0 → 61)

2026-07-12

Newly Listed

First tracked at rank #334

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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.2 · Raw JSON