Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 08:25 UTC

PDBeurope / PDBe-MCP-Servers

PDBe MCP Servers integrate Protein Data Bank Europe resources with LLMs via Model Context Protocol. Provides seamless access to protein structure data through API tools and graph database schema assistance for intelligent Cypher query generation, bridging structural biology and AI research.

PythonApache-2.0★ 39 stars⑂ 1 forksince Jun 2025View on GitHub ↗
KindCommand-line toolMCP serverLibraryNetwork servicehow this is determined

PDBeurope/PDBe-MCP-Servers holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Engineering Quality (78/100) and lowest on Community & Adoption (47/100). It was last updated 42 days ago. A single contributor accounts for most of its recent work.

71
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.

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

Ownership

PDBe EMBL-EBIOrganization
88 followers49 public repossince Sep 2014

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIpdbe-mcp-server1.1.63001742 days agoautomationfetchhttpllmmcpstatelessstreamableweb

Metrics by category

Vitality

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

67Good · 21% of overall
How it's scored
18/36Push recency — last push 42 days ago
11.1/36Commit cadence — 16/52 weeks with commits
12.7/18Commit volume — 25 commits in the last year
3/10OpenSSF Scorecard: Maintained — 4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
Inputs used
commits_last_year25
human_commit_share0.969
days_since_last_push42
active_weeks_last_year16

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 18 releases published
36/36Release recency — latest release 42 days ago
27/27Release cadence — a release every ~10.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count18
latest_release_tagv1.1.7
releases_from_tagsno
days_since_latest_release42
mean_days_between_releases10.2
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

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

47Weak · 17% of overall
How it's scored
25.6/60Stars — 39 stars
0/25Forks — 1 forks
0/15Watchers — 0 watchers
Inputs used
forks1
stars39
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno

Sustainability & Governance

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

56Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
28/42Issue resolution — 67% of issues closed
21.9/30PR acceptance — 27/37 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/27 approved changesets -- score normalized to 0
Inputs used
merged_prs27
open_issues1
closed_issues2
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.667
closed_unmerged_prs10
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
14/25Owner reach — 88 followers of PDBeurope
24.4/25Track record — 49 public repos, account ~11 yr old
Inputs used
followers88
owner_typeOrganization
is_verifiedno
owner_loginPDBeurope
public_repos49
account_age_days4,375

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff]), ruff.toml
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests — 24 out of 27 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 10 topics
10/10Wiki
Inputs used
topicsai-integration, api-server, bioinformatics, knowledge-graph, llm-tools, mcp, pdbe, protein-structures, python, structural-biology
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?

65Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2/2.5CI-Tests — 24 out of 27 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/27 approved changesets -- score normalized to 0
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
2.2/7.5Maintained — 4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
2/5SAST — SAST tool is not run on all commits -- score normalized to 4
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
3/7.5Vulnerabilities — 6 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.6
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. 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_packages38
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:pdbe-mcp-server@1.1.6 runtime dependency closure — what installing the published package pulls in — 38 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.

68Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://antigravity.google/llms.txt)
40/40Legible commit history — 25 of 31 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://antigravity.google/llms.txt
legible_history_share0.806
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff]), ruff.toml
11/11Static type checking — pdbe_mcp_server/py.typed
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 3 of the last 32 commits agent-authored or agent-credited
8/8Automated maintenance — 1 of the last 32 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configspdbe_mcp_server/py.typed
agent_commit_share0.094
toolchain_manifests—
dependency_bot_commit_share0.031
How it's scored
27/45Type-checkable code — Python with type-check config (pdbe_mcp_server/py.typed)
55/55Manageable file sizes — 0/15 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes28,927
source_files_sampled15
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

39GitHub stars
1contributors
25commits, last 12 months
42days since last push
18releases
1bus factor
1open issues
PyPIpackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 5.6 / 10
5.6aggregate

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-09-10 08:24 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
8CI-Tests24 out of 27 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/27 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
3Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
4SASTSAST tool is not run on all commits -- score normalized to 4
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
4Vulnerabilities6 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
PyPIanyio>=4.5,<5pyproject.toml
PyPIclick>=8.1,<9pyproject.toml
PyPIhttpx>=0.27,<1pyproject.toml
PyPImcp>=1.23,<2pyproject.toml
PyPIneo4j>=5,<6pyproject.toml
PyPIomegaconf>=2.3,<3pyproject.toml
PyPIpython-toon>=0.1.3,<0.2pyproject.toml
PyPIrequests>=2.33,<3pyproject.toml
PyPIstarlette>=1.0.1,<2pyproject.toml
PyPIuvicorn>=0.30,<1pyproject.toml
All dependencies 79

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

RegistryPackageVersionRelation
PyPIanyio4.9.0direct
PyPIclick8.2.1direct
PyPIhttpx0.28.1direct
PyPImcp1.27.2direct
PyPIneo4j5.28.4direct
PyPIomegaconf2.3.0direct
PyPIpython-toon0.1.3direct
PyPIrequests2.34.2direct
PyPIstarlette1.3.1direct
PyPIuvicorn0.34.3direct
PyPIannotated-types0.7.0indirect
PyPIantlr4-python3-runtime4.9.3indirect
PyPIattrs26.1.0indirect
PyPIbackports-asyncio-runner1.2.0indirect
PyPIbackports-tarfile1.2.0indirect
PyPIcertifi2025.4.26indirect
PyPIcffi2.0.0indirect
PyPIcharset-normalizer3.4.2indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.11.0indirect
PyPIcryptography48.0.1indirect
PyPIdocutils0.22.2indirect
PyPIexceptiongroup1.3.0indirect
PyPIh110.16.0indirect
PyPIhttpcore1.0.9indirect
PyPIhttpx-sse0.4.0indirect
PyPIid1.5.0indirect
PyPIidna3.18indirect
PyPIimportlib-metadata8.7.0indirect
PyPIiniconfig2.1.0indirect
PyPIjaraco-classes3.4.0indirect
PyPIjaraco-context6.0.1indirect
PyPIjaraco-functools4.3.0indirect
PyPIjeepney0.9.0indirect
PyPIjsonschema4.26.0indirect
PyPIjsonschema-specifications2025.9.1indirect
PyPIkeyring25.6.0indirect
PyPImarkdown-it-py4.0.0indirect
PyPImdurl0.1.2indirect
PyPImore-itertools10.8.0indirect
PyPInh30.3.2indirect
PyPInodeenv1.9.1indirect
PyPIpackaging25.0indirect
PyPIpdbe-mcp-server1.1.5indirect
PyPIpluggy1.6.0indirect
PyPIpycparser2.23indirect
PyPIpydantic2.11.5indirect
PyPIpydantic-core2.33.2indirect
PyPIpydantic-settings2.9.1indirect
PyPIpygments2.20.0indirect
PyPIpyjwt2.13.0indirect
PyPIpyright1.1.401indirect
PyPIpytest9.0.3indirect
PyPIpytest-asyncio1.4.0indirect
PyPIpytest-cov7.0.0indirect
PyPIpytest-mock3.15.1indirect
PyPIpython-dotenv1.2.2indirect
PyPIpython-multipart0.0.32indirect
PyPIpytz2026.1.post1indirect
PyPIpywin32312indirect
PyPIpywin32-ctypes0.2.3indirect
PyPIpyyaml6.0.3indirect
PyPIreadme-renderer44.0indirect
PyPIreferencing0.37.0indirect
PyPIrequests-toolbelt1.0.0indirect
PyPIrfc39862.0.0indirect
PyPIrich14.2.0indirect
PyPIrpds-py0.30.0indirect
PyPIrpds-py2026.5.1indirect
PyPIruff0.11.12indirect
PyPIsecretstorage3.4.0indirect
PyPIsniffio1.3.1indirect
PyPIsse-starlette2.3.6indirect
PyPItomli2.2.1indirect
PyPItwine6.2.0indirect
PyPItyping-extensions4.14.0indirect
PyPItyping-inspection0.4.1indirect
PyPIurllib32.7.0indirect
PyPIzipp3.23.0indirect
Dependency advisories 0

Installing pypi:pdbe-mcp-server@1.1.6 pulls in 38 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.