Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-17 02:17 UTC

fastly / mcp

Model Context Protocol (MCP) server for AI-powered Fastly CDN management.

JavaScriptMIT★ 40 stars⑂ 9 forkssince Jun 2025View on GitHub ↗
KindLibraryCommand-line toolMCP serverhow this is determined

fastly/mcp holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Vitality (81/100) and lowest on Community & Adoption (50/100). It was last updated 14 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

FastlyOrganization
456 followers300 public repossince May 2011

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@fastly/mcp2.4.12,3981136 days agofastlycdnapimcpmodel-context-protocolai

Metrics by category

Vitality

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

81Excellent · 21% of overall
How it's scored
28.8/36Push recency — last push 14 days ago
11.1/36Commit cadence — 16/52 weeks with commits
18/18Commit volume — 122 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year122
human_commit_share1
days_since_last_push14
active_weeks_last_year16

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 14 releases published
36/36Release recency — latest release 90 days ago
27/27Release cadence — a release every ~39.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count14
latest_release_tagv2.1.5
releases_from_tagsno
days_since_latest_release90
mean_days_between_releases39.6
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?

50Moderate · 17% of overall
How it's scored
25.8/60Stars — 40 stars
7.5/25Forks — 9 forks
0/15Watchers — 2 watchers
Inputs used
forks9
stars40
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateno
How it's scored
45.1/80Monthly downloads — 2,398 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@fastly/mcp
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads2,398
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?

60Moderate · 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
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
42/42Issue resolution — 100% of issues closed
10/30PR acceptance — 1/3 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs1
open_issues0
closed_issues3
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs2
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
19.1/25Owner reach — 456 followers of fastly
25/25Track record — 300 public repos, account ~15 yr old
Inputs used
followers456
owner_typeOrganization
is_verifiedno
owner_loginfastly
public_repos300
account_age_days5,670

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 36 days ago
20/20Version history — 11 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@fastly/mcp
ecosystemsnpm
any_deprecatedno
min_days_since_publish36

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — biome.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 6 topics
0/10Wiki
Inputs used
topicsfastly-featured, fastly-oss-tier1, tool, fastly, mcp, mcp-server
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?

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

54Moderate · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://www.fastly.com/llms.txt)
6.9/40Legible commit history — 13 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://www.fastly.com/llms.txt
legible_history_share0.13
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes6,009
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — biome.json
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
8/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 8
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
54.4/55Manageable file sizes — 1/88 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes75,539
source_files_sampled88
oversized_source_files1
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalyes
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

40GitHub stars
1contributors
122commits, last 12 months
14days since last push
14releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 9 ⇿
0Stars
9Forks
12Releases

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.

0246810912025-082026-022026-09
Major 0Minor 1Patch 11
OpenSSF Scorecard 5.7 / 10
5.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-11-17 02:16 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
8Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
0SASTno SAST tool detected
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
3Vulnerabilities7 existing vulnerabilities detected
Direct dependencies 5
RegistryPackageVersion constraintManifest
npm@modelcontextprotocol/node^2.1.2package.json
npm@modelcontextprotocol/server^2.4.0package.json
npmfast-cipher0.3.2package.json
npmfastly17.0.0package.json
npmzod^4.6.7package.json
All dependencies 80

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

RegistryPackageVersionRelation
npm@modelcontextprotocol/node2.1.2direct
npm@modelcontextprotocol/server2.4.0direct
npmfast-cipher0.3.2direct
npmfastly17.0.0direct
npmzod4.6.7direct
Gogithub.com/google/jsonschema-gov0.4.2indirect
Gogithub.com/jedisct1/go-fastv0.1.1indirect
Gogithub.com/modelcontextprotocol/go-sdkv1.4.1indirect
Gogithub.com/segmentio/asmv1.2.1indirect
Gogithub.com/segmentio/encodingv0.5.4indirect
Gogithub.com/yosida95/uritemplate/v3v3.0.2indirect
Gogolang.org/x/oauth2v0.36.0indirect
Gogolang.org/x/sysv0.42.0indirect
npm@biomejs/biome2.6.4indirect
npm@biomejs/cli-android-arm642.6.4indirect
npm@biomejs/cli-android-x642.6.4indirect
npm@biomejs/cli-darwin-arm642.6.4indirect
npm@biomejs/cli-darwin-x642.6.4indirect
npm@biomejs/cli-linux-arm642.6.4indirect
npm@biomejs/cli-linux-arm64-musl2.6.4indirect
npm@biomejs/cli-linux-x642.6.4indirect
npm@biomejs/cli-linux-x64-musl2.6.4indirect
npm@biomejs/cli-win32-arm642.6.4indirect
npm@biomejs/cli-win32-x642.6.4indirect
npm@hono/node-server2.1.5indirect
npm@modelcontextprotocol/client2.4.0indirect
npm@modelcontextprotocol/core2.4.0indirect
npmasynckit0.4.0indirect
npmcall-bind-apply-helpers1.0.2indirect
npmcall-bound1.0.4indirect
npmcombined-stream1.0.8indirect
npmcomponent-emitter1.3.1indirect
npmcookiejar2.1.4indirect
npmcross-spawn7.0.6indirect
npmdebug4.4.3indirect
npmdelayed-stream1.0.0indirect
npmdunder-proto1.0.1indirect
npmes-define-property1.0.1indirect
npmes-errors1.3.0indirect
npmes-object-atoms1.1.2indirect
npmes-set-tostringtag2.1.0indirect
npmeventsource3.0.7indirect
npmeventsource-parser3.1.1indirect
npmfast-safe-stringify2.1.1indirect
npmform-data3.0.5indirect
npmformidable1.2.6indirect
npmfunction-bind1.1.2indirect
npmget-intrinsic1.3.0indirect
npmget-proto1.0.1indirect
npmgopd1.2.0indirect
npmhas-symbols1.1.0indirect
npmhas-tostringtag1.0.2indirect
npmhasown2.0.4indirect
npmhono4.13.14indirect
npminherits2.0.4indirect
npmisexe2.0.0indirect
npmjose6.2.14indirect
npmmath-intrinsics1.1.0indirect
npmmethods1.1.2indirect
npmmime2.6.0indirect
npmmime-db1.52.0indirect
npmmime-types2.1.35indirect
npmms2.1.3indirect
npmobject-inspect1.13.4indirect
npmpath-key3.1.1indirect
npmpkce-challenge5.0.1indirect
npmqs6.17.1indirect
npmreadable-stream3.6.2indirect
npmsafe-buffer5.2.1indirect
npmsemver7.8.5indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmside-channel1.1.1indirect
npmside-channel-list1.0.1indirect
npmside-channel-map1.0.1indirect
npmside-channel-weakmap1.0.2indirect
npmstring_decoder1.3.0indirect
npmsuperagent6.1.0indirect
npmutil-deprecate1.0.2indirect
npmwhich2.0.2indirect
Dependency advisories 0

Installing npm:@fastly/mcp@2.4.1 pulls in 53 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 — npm.