Software health reportschema 0.27.0 · metrics 2.10.0 · 2026-08-02 04:28 UTC

refined-element / lightning-enable-mcp

MCP server enabling AI agents to make Lightning Network payments

C# · PythonMIT★ 9 stars⑂ 2 forkssince Feb 2026View on GitHub ↗

KindMCP serverLibraryhow this is determined

#agentic-commerce #ai-agents #bitcoin #l402 #lightning-network #mcp #mcp-server #model-context-protocol #payments

refined-element/lightning-enable-mcp holds a health index of 48 out of 100, placing it in the Weak band. It scores highest on AI Readiness (72/100) and lowest on Community & Adoption (31/100). It was last updated today. A single contributor accounts for most of its recent work.

overall / 100

Weak

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.

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)

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

Ownership

refined-elementPersonal account

2 followers37 public repossince Sep 2021

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

Package ecosystems

Registry	Package	Version	Downloads / mo	Versions	Last publish	Tags
PyPI	lightning-enable-mcp	1.21.0	-	55	0 days ago	agents ai bitcoin l402 lightning lsat mcp model-context-protocol nostr nwc payments

Metrics by category

Vitality

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

46Weak · 21% of overall

Development activity

76Good

How it's scored

36/36	Push recency — last push 0 days ago
11.8/36	Commit cadence — 17/52 weeks with commits
18/18	Commit volume — 168 commits in the last year
10/10	OpenSSF Scorecard: Maintained — 30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10

Inputs used

commits_last_year	168
human_commit_share	1
days_since_last_push	0
active_weeks_last_year	17

Release discipline

1Critical

How it's scored

0/27	Ships releases — no releases published
0/36	Release recency — no releases
0/27	Release cadence — no releases
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count

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?

31At Risk · 17% of overall

Popularity & adoption

15Critical

How it's scored

14.6/60	Stars — 9 stars
0/25	Forks — 2 forks
0/15	Watchers — 0 watchers

Inputs used

forks	2
stars	9
watchers	0
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

50Moderate

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (MIT)
0/18	CONTRIBUTING guide
0/13.5	Code of conduct
0/7.2	Issue template
0/6.3	PR template

Inputs used

has_readme	yes
has_license	yes
readme_badges	—
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	—
has_pull_request_template	no

Sustainability & Governance

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

48Weak · 23% of overall

Maintainer resilience (bus factor)

10Critical

How it's scored

9/54	Bus factor — 1 contributor(s) cover half of all commits
0/22.5	Commit distribution — top contributor authored 100% of commits
1.4/13.5	Contributor breadth — 1 contributors
0/10	OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0

Inputs used

bus_factor	1
contributors_sampled	1
top_contributor_share	1

Issue & PR responsiveness

55Moderate

How it's scored

21/42	Issue resolution — 50% of issues closed
27.1/30	PR acceptance — 57/63 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15	OpenSSF Scorecard: Code-Review — Found 0/10 approved changesets -- score normalized to 0

Inputs used

merged_prs	57
open_issues	5
closed_issues	5
prs_merged_7d	—
prs_decided_7d	—
prs_merged_30d	—
prs_decided_30d	—
issue_closed_ratio	0.5
closed_unmerged_prs	6
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.

Ownership & stewardship

43Weak

How it's scored

10/30	Ownership backing — personal (user) account
0/20	Verified domain — not applicable to user accounts
3.4/25	Owner reach — 2 followers of refined-element
21.3/25	Track record — 37 public repos, account ~4 yr old

Inputs used

followers	2
owner_type	User
is_verified	—
owner_login	refined-element
public_repos	37
account_age_days	1,794

Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional

How it's scored

25/25	Published & resolvable — 1 package(s) on pypi
35/35	Publish recency — latest publish 0 days ago
20/20	Version history — 55 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	lightning-enable-mcp
ecosystems	pypi
any_deprecated	no
min_days_since_publish	0

Engineering Quality

Are baseline engineering and documentation practices in place?

65Good · 19% of overall

Engineering practices

68Good

How it's scored

24/24	CI workflows — 6 workflow(s)
24/24	Tests present
0/16	Linter config
0/9.6	Pre-commit hooks
0/6.4	.editorconfig
20/20	OpenSSF Scorecard: CI-Tests — 9 out of 9 merged PRs checked by a CI test -- score normalized to 10

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	no
has_linter_config	no
has_precommit_config	no

Documentation

60Moderate

How it's scored

30/30	README
0/25	Documentation directory
0/15	Documentation / homepage site
10/10	Repository description
10/10	Topics — 9 topics
10/10	Wiki

Inputs used

topics	agentic-commerce, ai-agents, bitcoin, l402, lightning-network, mcp, mcp-server, model-context-protocol, payments
has_wiki	yes
homepage	—
docs_site	—
has_readme	yes
has_docs_dir	no
has_description	yes

Security

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

51Moderate · 16% of overall

Security posture

51Moderate

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
0/7.5	Branch-Protection — no data
2.5/2.5	CI-Tests — 9 out of 9 merged PRs checked by a CI test -- score normalized to 10
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5	Code-Review — Found 0/10 approved changesets -- score normalized to 0
0/2.5	Contributors — project has 0 contributing companies or organizations -- score normalized to 0
10/10	Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5	Dependency-Update-Tool — no update tool detected
0/5	Fuzzing — project is not fuzzed
2.5/2.5	License — license file detected
7.5/7.5	Maintained — 30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
5/5	Packaging — packaging workflow detected
0/5	Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
3.5/5	SAST — SAST tool detected but not run on all commits
0/5	Security-Policy — security policy file not detected
0/7.5	Signed-Releases — no data
0/7.5	Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5	Vulnerabilities — 0 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	16
scorecard_version	v5.5.0
checks_inconclusive	2
scorecard_aggregate	5.1

Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. 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

Agent context & guidance

85Excellent

How it's scored

45/45	Agent instructions — CLAUDE.md
0/15	Machine-readable docs (llms.txt)
40/40	Legible commit history — 100 of 100 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	1
agent_instruction_files	CLAUDE.md
agent_instruction_max_bytes	2,239

Verify loop (build / test / typecheck)

66Good

How it's scored

12.6/18	One-command bootstrap — dotnet/src/LightningEnable.Mcp/LightningEnable.Mcp.csproj, dotnet/tests/LightningEnable.Mcp.Tests/LightningEnable.Mcp.Tests.csproj (toolchain convention, no task runner)
22/22	Automated tests
0/11	Lint / format config
11/11	Static type checking — python/lightning-enable-mcp/src/lightning_enable_mcp/py.typed
10/10	Reproducible environment — Dockerfile
10/10	Demonstrated agent practice — 91 of the last 100 commits agent-authored or agent-credited
0/8	Automated maintenance — no automated dependency updates observed
0/10	OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0

Inputs used

has_nix	no
has_tests	yes
lockfiles	—
has_dockerfile	yes
typed_language	yes
bootstrap_files	—
has_devcontainer	no
has_linter_config	no
typecheck_configs	python/lightning-enable-mcp/src/lightning_enable_mcp/py.typed
agent_commit_share	0.91
toolchain_manifests	dotnet/src/LightningEnable.Mcp/LightningEnable.Mcp.csproj, dotnet/tests/LightningEnable.Mcp.Tests/LightningEnable.Mcp.Tests.csproj
dependency_bot_commit_share	0

Code legibility for models

99Exceptional

How it's scored

45/45	Type-checkable code — C# (statically typed)
54.4/55	Manageable file sizes — 2/187 source files over 60KB

Inputs used

primary_language	C#
largest_source_bytes	73,879
source_files_sampled	187
oversized_source_files	2

Machine-readable interfaces

33At Risk

How it's scored

0/40	API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
20/20	MCP server
0/40	Runnable examples

Inputs used

example_dirs	—
has_mcp_signal	yes
api_schema_files	—
interfaces_expected_of	—

Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

9GitHub stars

1contributors

168commits, last 12 months

0days since last push

0releases

1bus factor

5open issues

PyPIpackage ecosystems

Data collection warnings

Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
Could not fetch pypi package 'lightning-enable-mcp-bundle' from its registry
GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
deps.dev does not index pypi:lightning-enable-mcp@1.21.0; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 2 ⇿

0Stars

2Forks

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.

OpenSSF Scorecard 5.1 / 10

5.1aggregate

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-08-02 04:28 UTC

10	Binary-Artifacts	no binaries found in the repo
n/a	Branch-Protection	internal 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
10	CI-Tests	9 out of 9 merged PRs checked by a CI test -- score normalized to 10
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
0	Code-Review	Found 0/10 approved changesets -- score normalized to 0
0	Contributors	project has 0 contributing companies or organizations -- score normalized to 0
10	Dangerous-Workflow	no dangerous workflow patterns detected
0	Dependency-Update-Tool	no update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
10	Maintained	30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
10	Packaging	packaging workflow detected
0	Pinned-Dependencies	dependency not pinned by hash detected -- score normalized to 0
7	SAST	SAST tool detected but not run on all commits
0	Security-Policy	security policy file not detected
n/a	Signed-Releases	no releases found
0	Token-Permissions	detected GitHub workflow tokens with excessive permissions
10	Vulnerabilities	0 existing vulnerabilities detected

Direct dependencies 10

Registry	Package	Version constraint	Manifest
PyPI	lightning-enable-mcp	`==1.21.0`	mcpb/pyproject.toml
PyPI	mcp	`>=1.0.0,<2.0.0`	python/lightning-enable-mcp/pyproject.toml
PyPI	httpx	`>=0.25.0`	python/lightning-enable-mcp/pyproject.toml
PyPI	aiohttp	`>=3.13.4`	python/lightning-enable-mcp/pyproject.toml
PyPI	pydantic	`>=2.0.0`	python/lightning-enable-mcp/pyproject.toml
PyPI	bolt11	`>=2.0.0`	python/lightning-enable-mcp/pyproject.toml
PyPI	websockets	`>=12.0`	python/lightning-enable-mcp/pyproject.toml
PyPI	bech32	`>=1.2.0`	python/lightning-enable-mcp/pyproject.toml
PyPI	cryptography	`>=46.0.7`	python/lightning-enable-mcp/pyproject.toml
PyPI	coincurve	`>=20.0.0`	python/lightning-enable-mcp/pyproject.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.

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

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

Software health index

Score profile

Ownership

Package ecosystems

Metrics by category

Key facts

Data collection warnings

More detail

Feedback

Related records