Public record
Software health reportschema 0.23.0 · metrics 2.10.0 · 2026-07-21 21:11 UTC

jacob-bd / perplexity-web-mcp

MCP server and Anthropic API-compatible interface for Perplexity AI web interface

JavaScriptMIT★ 149 stars⑂ 21 forkssince Feb 2026View on GitHub ↗
KindMCP serverLibraryNetwork serviceCommand-line toolhow this is determined

jacob-bd/perplexity-web-mcp holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Vitality (82/100) and lowest on Security (27/100). It was last updated today. A single contributor accounts for most of its recent work.

65
overall / 100
Good

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

65
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 60 is calibrated to 65 on the published index scale (record calibration 2026-08-02).

Ownership

Jacob BDPersonal account
336 followers19 public repossince Feb 2019

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIperplexity-web-mcp-cli0.14.21,799456 days agoperplexityaimcpanthropicapiclient

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

82Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
12.5/36Commit cadence18/52 weeks with commits
18/18Commit volume148 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 13 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year148
human_commit_share1
days_since_last_push0
active_weeks_last_year18
How it's scored
27/27Ships releases47 releases published
36/36Release recencylatest release 6 days ago
27/27Release cadencea release every ~7.3 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count47
latest_release_tagv0.14.2
releases_from_tagsno
days_since_latest_release6
mean_days_between_releases7.3

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

49Weak · 17% of overall
How it's scored
35.2/60Stars149 stars
10.8/25Forks21 forks
0/15Watchers2 watchers
Inputs used
forks21
stars149
watchers2
growth_stateorganic
growth_factor_pct100
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
43.4/80Monthly downloads1,799 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesperplexity-web-mcp-cli
dependents
ecosystemspypi
total_downloads
monthly_downloads1,799
unverified_packages_excluded
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

59Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
42/42Issue resolution100% of issues closed
30/30PR acceptance2/2 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 1/30 approved changesets -- score normalized to 0
Inputs used
merged_prs2
open_issues0
closed_issues14
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs0
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
18.2/25Owner reach336 followers of jacob-bd
21.5/25Track record19 public repos, account ~7 yr old
Inputs used
followers336
owner_typeUser
is_verified
owner_loginjacob-bd
public_repos19
account_age_days2,714
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on pypi
35/35Publish recencylatest publish 6 days ago
20/20Version history45 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesperplexity-web-mcp-cli
ecosystemspypi
any_deprecatedno
min_days_since_publish6

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter config
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 1 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

27At Risk · 16% of overall
How it's scored
0/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Tests0 out of 1 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 1/30 approved changesets -- score normalized to 0
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 13 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
6.8/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities48 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate2.7
Excluded from scoring (no data or not applicable): Packaging. Remaining weights renormalized.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

72Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history89 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.89
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes3,987
How it's scored
18/18One-command bootstrapJustfile
22/22Automated tests
11/11Lint / format config
11/11Static type checkingpyrightconfig.json, src/perplexity_web_mcp/py.typed
10/10Reproducible environmentlockfile
10/10Demonstrated agent practice19 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_filesJustfile
has_devcontainerno
has_linter_configyes
typecheck_configspyrightconfig.json, src/perplexity_web_mcp/py.typed
agent_commit_share0.19
toolchain_manifests
dependency_bot_commit_share0
How it's scored
27/45Type-checkable codeJavaScript with type-check config (pyrightconfig.json, src/perplexity_web_mcp/py.typed)
43.7/55Manageable file sizes404/1,966 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes4,197,994
source_files_sampled1,966
oversized_source_files404
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs
has_mcp_signalyes
api_schema_files
interfaces_expected_ofnetwork-service

Key facts

149GitHub stars
1contributors
148commits, last 12 months
0days since last push
47releases
1bus factor
0open issues
PyPIpackage ecosystems

Data collection warnings

  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • deps.dev does not index pypi:perplexity-web-mcp-cli@0.14.2; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 149 ★ / 21 ⇿
149Stars
21Forks
21Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

025507510012515014921122026-032026-052026-07
Major 0Minor 5Patch 16
OpenSSF Scorecard 2.7 / 10
2.7aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-07-21 21:10 UTC

0Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 1 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/30 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 13 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities48 existing vulnerabilities detected
Direct dependencies 13
RegistryPackageVersion constraintManifest
PyPIcurl-cffi>=0.15.0,<1.0pyproject.toml
PyPIloguru>=0.7.3,<1.0pyproject.toml
PyPIorjson>=3.11.6,<4.0pyproject.toml
PyPIpydantic>=2.12.5,<3.0pyproject.toml
PyPItenacity>=9.1.2,<10.0pyproject.toml
PyPItomli>=2.0.0,<3.0pyproject.toml
PyPIpython-dotenv>=1.0.0,<2.0pyproject.toml
PyPIrich>=13.0.0,<15.0pyproject.toml
PyPIrich-click>=1.8pyproject.toml
PyPIfastmcp>=2.14.4,<3.0pyproject.toml
PyPIfastapi>=0.115.0,<1.0pyproject.toml
PyPIuvicorn>=0.30.0,<1.0pyproject.toml
PyPIhttpx>=0.27.0,<1.0pyproject.toml
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.23.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsPyPI.