Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-25 21:01 UTC

ActiveCampaign / postmark-mcp

Official Postmark MCP server by ActiveCampaign — 24 tools to send, template, search, and diagnose transactional email from Claude, Cursor & other AI assistants.

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

ActiveCampaign/postmark-mcp holds a health index of 47 out of 100, placing it in the Weak band. It scores highest on Vitality (67/100) and lowest on Engineering Quality (27/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

ActiveCampaignOrganization
78 followers88 public repossince Jan 2011

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@activecampaign/postmark-mcp2.1.15,8642104 days agopostmarkactivecampaignemailmcpmodel-context-protocolclaudecursorai

Metrics by category

Vitality

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

67Good · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
5.5/36Commit cadence — 8/52 weeks with commits
10.3/18Commit volume — 13 commits in the last year
0/10OpenSSF Scorecard: Maintained — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year13
human_commit_share0.966
days_since_last_push2
active_weeks_last_year8
How it's scored
27/27Ships releases — 4 releases published
27/36Release recency — latest release 104 days ago
27/27Release cadence — a release every ~13.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count4
latest_release_tagv2.1.1
releases_from_tagsno
days_since_latest_release104
mean_days_between_releases13.3
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
28.7/60Stars — 60 stars
10.5/25Forks — 19 forks
2.7/15Watchers — 4 watchers
Inputs used
forks19
stars60
watchers4
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
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
50.2/80Monthly downloads — 5,864 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@activecampaign/postmark-mcp
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads5,864
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?

51Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
8.8/22.5Commit distribution — top contributor authored 61% of commits
5.4/13.5Contributor breadth — 4 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.607
How it's scored
0/42Issue resolution — 0% of issues closed
16.4/30PR acceptance — 12/22 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
7.5/15OpenSSF Scorecard: Code-Review — Found 10/17 approved changesets -- score normalized to 5
Inputs used
merged_prs12
open_issues23
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0
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
13.6/25Owner reach — 78 followers of ActiveCampaign
25/25Track record — 88 public repos, account ~15 yr old
Inputs used
followers78
owner_typeOrganization
is_verifiedno
owner_loginActiveCampaign
public_repos88
account_age_days5,764
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 104 days ago
12/20Version history — 2 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@activecampaign/postmark-mcp
ecosystemsnpm
any_deprecatedno
min_days_since_publish104

Engineering Quality

Are baseline engineering and documentation practices in place?

27At Risk · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 12 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://postmarkapp.com/lp/mcp
10/10Repository description
10/10Topics — 8 topics
0/10Wiki
Inputs used
topicsemail, email-sender, mcp, postmark, activecampaign, ai, claude, model-context-protocol
has_wikino
homepagehttps://postmarkapp.com/lp/mcp
docs_sitehttps://postmarkapp.com/lp/mcp
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

42Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0/2.5CI-Tests — 0 out of 12 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3.8/7.5Code-Review — Found 10/17 approved changesets -- score normalized to 5
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
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
0/7.5Maintained — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
0/7.5Vulnerabilities — 43 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate3.4
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.
How it's scored
9.2/35Direct dependencies free of known advisories — 2 affected: @modelcontextprotocol/sdk 1.29.0 (high 8.6), zod 3.25.76 (high 7.5)
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
40/40No advisories left outstanding — no advisory has been public longer than 90 days
Inputs used
sourceosv
advisories6
affected_packages2
assessed_packages96
unassessed_packages0
affected_by_severityhigh 2
direct_affected_packages2
Matched the npm:@activecampaign/postmark-mcp@2.1.1 runtime dependency closure — what installing the published package pulls in — 96 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.

50Moderate · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://postmarkapp.com/llms.txt)
40/40Legible commit history — 21 of 28 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://postmarkapp.com/llms.txt
legible_history_share0.75
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes8,468
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 29
8/8Automated maintenance — 1 of the last 29 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.034
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
47.1/55Manageable file sizes — 1/7 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes72,294
source_files_sampled7
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

60GitHub stars
4contributors
13commits, last 12 months
2days since last push
4releases
1bus factor
23open 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 ★ / 19 ⇿
0Stars
19Forks
4Releases

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.

0481216201922025-102026-032026-09
Major 2Minor 1Patch 1
OpenSSF Scorecard 3.4 / 10
3.4aggregate

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-25 21:01 UTC

10Binary-Artifactsno binaries found in the repo
1Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests0 out of 12 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 10/17 approved changesets -- score normalized to 5
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities43 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
npm@modelcontextprotocol/sdk1.29.0package.json
npmdotenv16.6.1package.json
npmzod3.25.76package.json
All dependencies 92

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

RegistryPackageVersionRelation
npm@modelcontextprotocol/sdk1.29.0direct
npmdotenv16.6.1direct
npmzod3.25.76direct
npm@hono/node-server1.19.14indirect
npmaccepts2.0.0indirect
npmajv8.18.0indirect
npmajv-formats3.0.1indirect
npmbody-parser2.2.2indirect
npmbytes3.1.2indirect
npmcall-bind-apply-helpers1.0.2indirect
npmcall-bound1.0.4indirect
npmcontent-disposition1.0.1indirect
npmcontent-type1.0.5indirect
npmcookie0.7.2indirect
npmcookie-signature1.2.2indirect
npmcors2.8.6indirect
npmcross-spawn7.0.6indirect
npmdebug4.4.3indirect
npmdepd2.0.0indirect
npmdunder-proto1.0.1indirect
npmee-first1.1.1indirect
npmencodeurl2.0.0indirect
npmes-define-property1.0.1indirect
npmes-errors1.3.0indirect
npmes-object-atoms1.1.1indirect
npmescape-html1.0.3indirect
npmetag1.8.1indirect
npmeventsource3.0.7indirect
npmeventsource-parser3.0.6indirect
npmexpress5.2.1indirect
npmexpress-rate-limit8.5.2indirect
npmfast-deep-equal3.1.3indirect
npmfast-uri3.1.2indirect
npmfinalhandler2.1.1indirect
npmforwarded0.2.0indirect
npmfresh2.0.0indirect
npmfunction-bind1.1.2indirect
npmget-intrinsic1.3.0indirect
npmget-proto1.0.1indirect
npmgopd1.2.0indirect
npmhas-symbols1.1.0indirect
npmhasown2.0.2indirect
npmhono4.12.25indirect
npmhttp-errors2.0.1indirect
npmiconv-lite0.7.2indirect
npminherits2.0.4indirect
npmip-address10.2.0indirect
npmipaddr.js1.9.1indirect
npmis-promise4.0.0indirect
npmisexe2.0.0indirect
npmjose6.2.1indirect
npmjson-schema-traverse1.0.0indirect
npmjson-schema-typed8.0.2indirect
npmmath-intrinsics1.1.0indirect
npmmedia-typer1.1.0indirect
npmmerge-descriptors2.0.0indirect
npmmime-db1.54.0indirect
npmmime-types3.0.2indirect
npmms2.1.3indirect
npmnegotiator1.0.0indirect
npmobject-assign4.1.1indirect
npmobject-inspect1.13.4indirect
npmon-finished2.4.1indirect
npmonce1.4.0indirect
npmparseurl1.3.3indirect
npmpath-key3.1.1indirect
npmpath-to-regexp8.4.2indirect
npmpkce-challenge5.0.1indirect
npmproxy-addr2.0.7indirect
npmqs6.15.2indirect
npmrange-parser1.2.1indirect
npmraw-body3.0.2indirect
npmrequire-from-string2.0.2indirect
npmrouter2.2.0indirect
npmsafer-buffer2.1.2indirect
npmsend1.2.1indirect
npmserve-static2.2.1indirect
npmsetprototypeof1.2.0indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmside-channel1.1.0indirect
npmside-channel-list1.0.0indirect
npmside-channel-map1.0.1indirect
npmside-channel-weakmap1.0.2indirect
npmstatuses2.0.2indirect
npmtoidentifier1.0.1indirect
npmtype-is2.0.1indirect
npmunpipe1.0.0indirect
npmvary1.1.2indirect
npmwhich2.0.2indirect
npmwrappy1.0.2indirect
npmzod-to-json-schema3.25.1indirect
Dependency advisories 2

Installing npm:@activecampaign/postmark-mcp@2.1.1 pulls in 96 packages, direct and transitive: 2 carry known advisories, of which 2 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
@modelcontextprotocol/sdk1.29.0directhigh52.3.1
zod3.25.76directhigh14.6.6

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.