Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-18 23:50 UTC

pab1it0 / prometheus-mcp-server

A Model Context Protocol (MCP) server that enables AI agents and LLMs to query and analyze Prometheus metrics through standardized interfaces.

PythonMIT★ 519 stars⑂ 104 forkssince Mar 2025View on GitHub ↗
KindNetwork serviceCommand-line toolMCP serverLibraryhow this is determined

pab1it0/prometheus-mcp-server holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Vitality (88/100) and lowest on AI Readiness (44/100). It was last updated 7 days ago. A single contributor accounts for most of its recent work.

83
overall / 100
Excellent

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.

83
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 70 is calibrated to 83 on the published index scale (record calibration 2026-08-02).

Ownership

Pavel ShklovskyPersonal account
41 followers40 public repossince Mar 2015

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 publish
PyPIprometheus_mcp_server1.6.218,8833576 days ago

Metrics by category

Vitality

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

88Excellent · 21% of overall
How it's scored
36/36Push recency — last push 7 days ago
18.7/36Commit cadence — 27/52 weeks with commits
17.1/18Commit volume — 79 commits in the last year
10/10OpenSSF Scorecard: Maintained — 15 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year79
human_commit_share0.69
days_since_last_push7
active_weeks_last_year27

Release discipline

98Exceptional
How it's scored
27/27Ships releases — 34 releases published
36/36Release recency — latest release 76 days ago
27/27Release cadence — a release every ~31 days
8/10OpenSSF Scorecard: Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts.
Inputs used
releases_count34
latest_release_tagv1.6.2
releases_from_tagsno
days_since_latest_release76
mean_days_between_releases31

Community & Adoption

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

68Good · 17% of overall
How it's scored
44/60Stars — 519 stars
16.8/25Forks — 104 forks
4.7/15Watchers — 8 watchers
Inputs used
forks104
stars519
watchers8
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges7
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, shields.io
has_pull_request_templateno

Sustainability & Governance

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

64Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
3.6/22.5Commit distribution — top contributor authored 84% of commits
13.5/13.5Contributor breadth — 18 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled18
top_contributor_share0.838
How it's scored
42/42Issue resolution — 100% of issues closed
25.5/30PR acceptance — 129/152 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
6/15OpenSSF Scorecard: Code-Review — Found 5/12 approved changesets -- score normalized to 4
Inputs used
merged_prs129
open_issues0
closed_issues36
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio1
closed_unmerged_prs23
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
11.7/25Owner reach — 41 followers of pab1it0
23.7/25Track record — 40 public repos, account ~11 yr old
Inputs used
followers41
owner_typeUser
is_verified—
owner_loginpab1it0
public_repos40
account_age_days4,220
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 76 days ago
20/20Version history — 35 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesprometheus_mcp_server
ecosystemspypi
any_deprecatedno
min_days_since_publish76

Engineering Quality

Are baseline engineering and documentation practices in place?

65Good · 19% of overall
How it's scored
24/24CI workflows — 9 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 6 topics
10/10Wiki
Inputs used
topicsai, devops, llm, mcp, prometheus, model-context-protocol
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

72Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3/7.5Code-Review — Found 5/12 approved changesets -- score normalized to 4
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflow — no data
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 15 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — no data
0/5SAST — no data
0/5Security-Policy — security policy file not detected
6/7.5Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts.
0/7.5Token-Permissions — no data
6.8/7.5Vulnerabilities — 1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate6.5
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Pinned-Dependencies, SAST, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages73
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the pypi:prometheus_mcp_server@1.6.2 runtime dependency closure — what installing the published package pulls in — 73 packages. Reachability is not analyzed.

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.

44Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 66 of 69 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.957
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
8/10Demonstrated agent practice — 4 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 31 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.04
toolchain_manifests—
dependency_bot_commit_share0.31
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — Python without a type-check config
55/55Manageable file sizes — 0/12 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes27,136
source_files_sampled12
oversized_source_files0
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

519GitHub stars
18contributors
79commits, last 12 months
7days since last push
34releases
1bus factor
0open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 104 ⇿
0Stars
104Forks
34Releases

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.

02040608010012010442025-032026-012026-10
Major 1Minor 6Patch 27

Each point covers 2 days.

OpenSSF Scorecard 6.5 / 10
6.5aggregate

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-10-18 23:50 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 5/12 approved changesets -- score normalized to 4
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowinternal error: internal error: invalid GitHub workflow: :427:0: could not parse as YAML: could not find expected ':' [syntax-check]
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained15 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
n/aPinned-Dependenciesinternal error: internal error: invalid GitHub workflow: :427:0: could not parse as YAML: could not find expected ':' [syntax-check]
n/aSASTinternal error: internal error: invalid GitHub workflow: :427:0: could not parse as YAML: could not find expected ':' [syntax-check]
0Security-Policysecurity policy file not detected
8Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
n/aToken-Permissionsinternal error: internal error: invalid GitHub workflow: :427:0: could not parse as YAML: could not find expected ':' [syntax-check]
9Vulnerabilities1 existing vulnerabilities detected
Direct dependencies 5
RegistryPackageVersion constraintManifest
PyPIpython-dotenv—pyproject.toml
PyPIrequests—pyproject.toml
PyPIstarlette—pyproject.toml
PyPIstructlog>=23.0.0pyproject.toml
PyPIfastmcp>=3.1.0pyproject.toml
All dependencies 89

Full resolved dependency set from the GitHub dependency graph: 5 direct and 84 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
PyPIfastmcp3.2.0direct
PyPIpython-dotenv1.2.2direct
PyPIrequests2.33.0direct
PyPIstarlette1.3.1direct
PyPIstructlog25.4.0direct
PyPIaiofile3.9.0indirect
PyPIannotated-types0.7.0indirect
PyPIanyio4.14.2indirect
PyPIattrs25.3.0indirect
PyPIauthlib1.6.12indirect
PyPIbackports-asyncio-runner1.2.0indirect
PyPIbackports-tarfile1.2.0indirect
PyPIbeartype0.22.9indirect
PyPIcachetools6.2.4indirect
PyPIcaio0.9.25indirect
PyPIcertifi2025.8.3indirect
PyPIcffi2.0.0indirect
PyPIcharset-normalizer3.4.3indirect
PyPIclick8.2.1indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.10.5indirect
PyPIcryptography50.0.0indirect
PyPIcyclopts4.5.0indirect
PyPIdnspython2.7.0indirect
PyPIdocker7.1.0indirect
PyPIdocstring-parser0.17.0indirect
PyPIdocutils0.22indirect
PyPIemail-validator2.3.0indirect
PyPIexceptiongroup1.3.0indirect
PyPIh110.16.0indirect
PyPIhttpcore1.0.9indirect
PyPIhttpx0.28.1indirect
PyPIhttpx-sse0.4.1indirect
PyPIidna3.15indirect
PyPIimportlib-metadata8.7.1indirect
PyPIiniconfig2.1.0indirect
PyPIjaraco-classes3.4.0indirect
PyPIjaraco-context6.1.0indirect
PyPIjaraco-functools4.4.0indirect
PyPIjeepney0.9.0indirect
PyPIjsonref1.1.0indirect
PyPIjsonschema4.25.1indirect
PyPIjsonschema-path0.3.4indirect
PyPIjsonschema-specifications2025.4.1indirect
PyPIkeyring25.7.0indirect
PyPImarkdown-it-py4.0.0indirect
PyPImcp1.28.1indirect
PyPImdurl0.1.2indirect
PyPImore-itertools10.7.0indirect
PyPIopenapi-pydantic0.5.1indirect
PyPIopentelemetry-api1.39.1indirect
PyPIpackaging25.0indirect
PyPIpathable0.4.4indirect
PyPIplatformdirs4.5.1indirect
PyPIpluggy1.6.0indirect
PyPIprometheus-mcp-server1.6.2indirect
PyPIpy-key-value-aio0.4.4indirect
PyPIpycparser2.22indirect
PyPIpydantic2.11.7indirect
PyPIpydantic2.13.4indirect
PyPIpydantic-core2.33.2indirect
PyPIpydantic-core2.46.4indirect
PyPIpydantic-settings2.10.1indirect
PyPIpygments2.20.0indirect
PyPIpyjwt2.15.0indirect
PyPIpyperclip1.9.0indirect
PyPIpytest9.0.3indirect
PyPIpytest-asyncio1.3.0indirect
PyPIpytest-cov6.2.1indirect
PyPIpython-multipart0.0.31indirect
PyPIpywin32311indirect
PyPIpywin32-ctypes0.2.3indirect
PyPIpyyaml6.0.2indirect
PyPIreferencing0.36.2indirect
PyPIrich14.1.0indirect
PyPIrich-rst1.3.1indirect
PyPIrpds-py0.27.0indirect
PyPIsecretstorage3.5.0indirect
PyPIsse-starlette3.0.2indirect
PyPItomli2.2.1indirect
PyPItyping-extensions4.15.0indirect
PyPItyping-inspection0.4.1indirect
PyPItyping-inspection0.4.2indirect
PyPIuncalled-for0.2.0indirect
PyPIurllib32.8.0indirect
PyPIuvicorn0.35.0indirect
PyPIwatchfiles1.1.1indirect
PyPIwebsockets16.0indirect
PyPIzipp3.23.0indirect
Dependency advisories 0

Installing pypi:prometheus_mcp_server@1.6.2 pulls in 73 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — PyPI.