Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-20 21:29 UTC

anyproto / anytype-mcp

An MCP server enabling AI assistants to interact with Anytype - your encrypted, local and collaborative wiki - to organize objects, lists, and more through natural language.

TypeScriptMIT★ 534 stars⑂ 63 forkssince Apr 2025View on GitHub ↗
KindMCP serverCommand-line toolLibraryhow this is determined

anyproto/anytype-mcp holds a health index of 89 out of 100, placing it in the Excellent band. It scores highest on Vitality (92/100) and lowest on Sustainability & Governance (59/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Any AssociationOrganization
6,349 followers96 public repossince Mar 2023

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@anyproto/anytype-mcp2.0.18,6492431 days agoanytypeapimcpserver

Metrics by category

Vitality

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

92Excellent · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
22.2/36Commit cadence — 32/52 weeks with commits
18/18Commit volume — 183 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_year183
human_commit_share0.68
days_since_last_push1
active_weeks_last_year32

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 24 releases published
36/36Release recency — latest release 31 days ago
27/27Release cadence — a release every ~22.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count24
latest_release_tagv2.0.1
releases_from_tagsno
days_since_latest_release31
mean_days_between_releases22.4
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?

75Good · 17% of overall
How it's scored
44.2/60Stars — 534 stars
14.9/25Forks — 63 forks
5.6/15Watchers — 11 watchers
Inputs used
forks63
stars534
watchers11
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
52.5/80Monthly downloads — 8,649 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@anyproto/anytype-mcp
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads8,649
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?

59Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
3.7/22.5Commit distribution — top contributor authored 84% of commits
8.1/13.5Contributor breadth — 6 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled6
top_contributor_share0.836
How it's scored
19.8/42Issue resolution — 47% of issues closed
17/30PR acceptance — 64/113 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/10 approved changesets -- score normalized to 0
Inputs used
merged_prs64
open_issues19
closed_issues17
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.472
closed_unmerged_prs49
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
25/25Owner reach — 6,349 followers of anyproto
20.2/25Track record — 96 public repos, account ~3 yr old
Inputs used
followers6,349
owner_typeOrganization
is_verifiedno
owner_loginanyproto
public_repos96
account_age_days1,314

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://npmjs.com/package/@anyproto/anytype-mcp
10/10Repository description
10/10Topics — 5 topics
0/10Wiki
Inputs used
topicsmcp, mcp-server, modelcontextprotocol, anytype, api
has_wikino
homepagehttps://npmjs.com/package/@anyproto/anytype-mcp
docs_sitehttps://npmjs.com/package/@anyproto/anytype-mcp
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

62Moderate · 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 — 9 out of 9 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
0/7.5Code-Review — Found 0/10 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
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 — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
5/5SAST — SAST tool is run on all commits
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 36 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.9
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.
How it's scored
9.1/35Direct dependencies free of known advisories — 2 affected: @modelcontextprotocol/sdk 1.30.0 (high 8.6), axios 1.18.1 (high 8.2)
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
advisories17
affected_packages2
assessed_packages122
unassessed_packages0
affected_by_severityhigh 2
direct_affected_packages2
Matched the npm:@anyproto/anytype-mcp@2.0.1 runtime dependency closure — what installing the published package pulls in — 122 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.

70Good · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 51 of 68 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.75
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes3,414
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.js
11/11Static type checking — tsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 32 of the last 100 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
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.32
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
53.7/55Manageable file sizes — 1/41 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes62,218
source_files_sampled41
oversized_source_files1
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — scripts/openapi.json
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalyes
api_schema_filesscripts/openapi.json
interfaces_expected_of—

Key facts

534GitHub stars
6contributors
183commits, last 12 months
1days since last push
24releases
1bus factor
19open 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 ★ / 63 ⇿
0Stars
63Forks
23Releases

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.

01325385063756322025-052026-022026-10
Major 1Minor 2Patch 20

Each point covers 2 days.

OpenSSF Scorecard 5.9 / 10
5.9aggregate

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-20 21:28 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests9 out of 9 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/10 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate 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
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities36 existing vulnerabilities detected
Direct dependencies 9
RegistryPackageVersion constraintManifest
npm@modelcontextprotocol/sdk1.32.0package.json
npmaxios1.20.0package.json
npmform-data4.0.6package.json
npmmustache4.2.0package.json
npmnode-fetch3.3.2package.json
npmopenapi-client-axios7.9.1package.json
npmopenapi-schema-validator12.1.3package.json
npmopenapi-types12.1.3package.json
npmzod4.6.5package.json
All dependencies 26

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

RegistryPackageVersionRelation
npm@modelcontextprotocol/sdk1.32.0direct
npmaxios1.20.0direct
npmform-data4.0.6direct
npmmustache4.2.0direct
npmnode-fetch3.3.2direct
npmopenapi-client-axios7.9.1direct
npmopenapi-schema-validator12.1.3direct
npmopenapi-types12.1.3direct
npmzod4.6.5direct
npm@anthropic-ai/sdk0.131.0indirect
npm@eslint/js10.0.1indirect
npm@types/json-schema7.0.15indirect
npm@types/mustache4.2.6indirect
npm@types/node26.6.4indirect
npm@types/which3.0.4indirect
npm@typescript-eslint/eslint-plugin8.71.0indirect
npm@typescript-eslint/parser8.71.0indirect
npm@vitest/coverage-v85.0.3indirect
npmesbuild0.28.2indirect
npmeslint10.12.0indirect
npmopenai7.27.0indirect
npmprettier3.9.9indirect
npmprettier-plugin-organize-imports4.3.0indirect
npmtsx4.23.15indirect
npmtypescript6.0.3indirect
npmvitest5.0.3indirect
Dependency advisories 2

Installing npm:@anyproto/anytype-mcp@2.0.1 pulls in 122 packages, direct and transitive: 2 carry known advisories, of which 2 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
@modelcontextprotocol/sdk1.30.0directhigh52.3.1
axios1.18.1directhigh121.20.0

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.