Evidaxis
Dated record

linkedin-mcp-server

repo · linkedin-mcp-server · paper: not linked · as of

Niche: not yet assigned.

36.2 commits per week averaged over the trailing window. No paper is linked in OpenAlex. deps.dev: 2 direct dependents, below the 5-dependent floor. 4,131 GitHub stars, recorded, not scored. Measured for linkedin-mcp-server as of 2026-11-07; sources: GitHub, OpenAlex and deps.dev where linked.

commits/wk 36.2 averaged, trailing window last commit week 2026-11-01 measured · GitHub ·
citations no paper linked all years, indexed to date no reading · OpenAlex ·
direct dependents 2 weekly axis input; partition 2026-11-07 measured · deps.dev snapshot ·
stars 4,131 recorded, not scored measured · GitHub ·
Download values (CSV) JSON record Follow this system (feed) Report an error

Is linkedin-mcp-server still maintained?

36.2 commits per week averaged over the trailing window.

GitHub averaged 36.2 per week over the trailing window; raw weekly counts below are individual weeks.

Last commit week 2026-11-01.

Commits in the latest captured week vs 4 weeks earlier: -41 · vs 26 weeks earlier: -6 · 52-week range: 0 to 73 commits in an individual week.

line chart: linkedin-mcp-server, weekly commits, 14 in latest week, 2025-11-09 to 2026-11-01
linkedin-mcp-server averaged 36.2 commits a week. GitHub commit_activity · .
Latest eight weeks
Week startingCommits
2026-09-1361
2026-09-2073
2026-09-2767
2026-10-0455
2026-10-1164
2026-10-1812
2026-10-2529
2026-11-0114
heatmap chart: linkedin-mcp-server, weeks with commits, 25 of 26, 2026-05-10 to 2026-11-01
25 of the last 26 captured weeks had commits for linkedin-mcp-server. GitHub commit_activity · .
All 52 weeks
Weekly commits
Week startingCommits
2025-11-090
2025-11-160
2025-11-230
2025-11-300
2025-12-070
2025-12-140
2025-12-219
2025-12-281
2026-01-0412
2026-01-1144
2026-01-1828
2026-01-257
2026-02-0111
2026-02-0822
2026-02-1528
2026-02-222
2026-03-0164
2026-03-0855
2026-03-1529
2026-03-2230
2026-03-2928
2026-04-0522
2026-04-1227
2026-04-193
2026-04-2626
2026-05-0320
2026-05-1011
2026-05-176
2026-05-247
2026-05-315
2026-06-0732
2026-06-140
2026-06-2120
2026-06-284
2026-07-052
2026-07-121
2026-07-1912
2026-07-2632
2026-08-0215
2026-08-0913
2026-08-1612
2026-08-238
2026-08-3022
2026-09-0618
2026-09-1361
2026-09-2073
2026-09-2767
2026-10-0455
2026-10-1164
2026-10-1812
2026-10-2529
2026-11-0114

GitHub commit_activity · period 2025-11-09 to 2026-11-01 · n = 52 weeks · method weekly totals; reconstructed dates · updated · version 868e3c39d9c7-b1 · CSV

Readings

Recorded values and sources
ReadingValueΔ 4 weeksΔ 26 weeks52-week rangeInstrumentDateReproducePrevious reading
Commits per week36.23.98.48.4 to 36.7GitHub, trailing 12 weeks2026-11-07Public query35.9
Citing worksno readingno readingno readingno readingOpenAlex, all years2026-11-07Public queryno reading
Weekly direct dependents2no readingno reading2 to 2Weekly direct dependents2026-11-07Public queryno reading
Daily package dependents (unscored)no readingno readingno readingno readingdeps.dev REST, unscorednot capturedPublic queryno reading
Stars4,131301no reading3,632 to 4,131GitHub stars, unscored2026-11-07Public query4,056

Evidaxis snapshot · period 2026-11-07 · n = 1 system · method source linked readings · updated · version 868e3c39d9c7-b1

How to cite linkedin-mcp-server's record?

Evidaxis. linkedin-mcp-server measurement record. Snapshot 2026-11-07. urn:evidaxis:claim:e_PGBWRZ9DNDW:m5:2026-11-07. CC0-1.0. https://evidaxis.org/e/e_PGBWRZ9DNDW/

Evidaxis · period 2026-11-07 · n = 1 system · method claim URN · updated · version 868e3c39d9c7-b1

Is anyone using linkedin-mcp-server?

deps.dev: 2 direct dependents, below the 5-dependent floor.

Weekly dependents
PartitionDirect dependentsWeekly pointsMethod
no partition21m5 own packages

deps.dev weekly direct dependents of the system's own packages. A package counts when it is declared in the system's own tree, published under that name and not attributed by deps.dev to another repository. Partition dates can repeat across snapshots. Package linkage is not uniformly verified: packages with no repository metadata (no_link) are unverified and remain admitted.

Daily package dependents (unscored): no reading; captured not captured; package: not captured. deps.dev REST count for one identity-verified pinned package, captured daily and never scored. Its package scope differs from the weekly package union; neither value replaces the other. 4,131 GitHub stars, recorded, not scored.

deps.dev · period 2026-11-07 · n = 1 partition · method m5 own packages · updated · version 868e3c39d9c7-b1 · CSV

What changed since the last snapshot?

3 published readings changed between snapshots d1eb0cec0f6a and 868e3c39d9c7.

slope chart: linkedin-mcp-server, changed published values, 2, 2026-10-31 to 2026-11-07
2 published values changed for linkedin-mcp-server since 2026-10-31. Evidaxis snapshots · .
Snapshot values
MetricPreviousCurrentDelta
Commits per week35.936.20.3
Citing worksno readingno readingno reading
Weekly direct dependentsno reading2no reading
Stars4,0564,13175

Evidaxis snapshots · period 2026-10-31 to 2026-11-07 · n = 7 partitions · method paired snapshot values · updated · version 868e3c39d9c7-b1 · History CSV

Take the data or follow changes

Values and captured history are available under CC0-1.0. The system feed records changes to published numbers.

Values CSVHistory CSVJSON recordAtom feedJSON FeedAdd Evidaxis as a preferred source on GoogleReport an error

Evidaxis · period 2026-11-07 · n = 1 system · method CC0-1.0 open export · updated · version 868e3c39d9c7-b1

For teams tracking many systems

Use the cohort CSV, snapshot archive and membership manifest to reproduce observations across systems.

Cohort CSV · Snapshot archive · Membership manifest

Paper and links

Source records identify the system, repository and linked works; no paper authors are published.

    What is not measured for linkedin-mcp-server, and why

    Missing readings describe instrument coverage. A missing value is not a measured zero.

    Unmeasured slots
    ReadingReason
    Citing worksnot linked
    Daily package dependents (unscored)no reading captured

    Gate ETA: never published; Evidaxis makes no public actionable prediction.

    Dependents ecosystem composition: no reading; this field is not present in the snapshot.

    Evidaxis · period 2026-11-07 · n = 1 system · method measurement coverage · updated · version 868e3c39d9c7-b1

    Measurement detail

    Gate, gauges, percentile, derived signals and snapshot receipt

    History: 7 weekly observations; minimum 4. Axis coverage: 1 of 3 axes measurable. Gate: not computable - 1 of 3 axes measurable

    Gate: not computable - 1 of 3 axes measurable

    linkedin-mcp-server

    repo
    Unassigned (AI-v1 census) · n = 6545 · linkedin-mcp-server
    1 of 3 axes measurable · conf low
    convergence gate
    Convergence gate: Gate: not computable - 1 of 3 axes measurable Development velocity: rising vote Citation momentum: not measurable ∅ Direct-dependents momentum (deps.dev): not measurable ∅
    gate
    1 of 3 axes

    Gate: not computable - 1 of 3 axes measurable

    · Evidaxis snapshot · 2026-11-07
    Gate: not computable - 1 of 3 axes measurable
    position in cohort distribution one of 6545 in cohort
    percentile 89 within cohort p25 p50 p75 p0 p100
    percentile
    p89
    · Evidaxis snapshot · 2026-11-07
    momentum averages present-axis z-scores; two- and three-axis scores are not strictly comparable
    velocity z
    velocity z gaugevelocity z+2.93 within cohort, log-slope +0.082/wk.0+2.93
    velocity z
    +2.93 σ
    slope
    +0.082/wk
    · Evidaxis snapshot · 2026-11-07
    log-slope +0.082/wk
    citation z Citation source: not measured.
    direct-dependents z Direct-dependents axis: minimum of 14 usable points of the new quantity and 5 latest dependents not met.
    cohort
    6545
    systems measured
    weekly commits
    36.2
    Development velocity axis: measured.
    total citations
    no reading
    Citation source: not measured.
    momentum
    86.6
    percentile p89
    commit heatmap, last 26 weeks36.2/wk
    weekly commits, 26 weeks26 weeks of commits, peak 73 in a week, 25 active weeks, 595 total.week 1: 11 commitsweek 2: 6 commitsweek 3: 7 commitsweek 4: 5 commitsweek 5: 32 commitsweek 6: 0 commitsweek 7: 20 commitsweek 8: 4 commitsweek 9: 2 commitsweek 10: 1 commitsweek 11: 12 commitsweek 12: 32 commitsweek 13: 15 commitsweek 14: 13 commitsweek 15: 12 commitsweek 16: 8 commitsweek 17: 22 commitsweek 18: 18 commitsweek 19: 61 commitsweek 20: 73 commitsweek 21: 67 commitsweek 22: 55 commitsweek 23: 64 commitsweek 24: 12 commitsweek 25: 29 commitsweek 26: 14 commits
    weeks
    26
    peak/wk
    73
    active
    25
    total
    595
    · Evidaxis snapshot · 2026-11-07
    citations by yearCitation source: not measured.
    recency-weighted swing trailing 13-week vs prior 39-week log-slope ratio +1.69, regime accelerating. prior slope +0.037, recent slope +0.063 per week. +0.037prior 39w+0.063recent 13w+1.69×
    swing
    +1.69×
    regime
    accelerating
    windows
    13w vs 39w
    snapshot 1 of 1 · · m5
    commit-axis Sharpe log-linear slope over residual std, value +0.035 with 95% CI +0.007 to +0.064, 50 degrees of freedom. CI excludes zero.0+0.03595% CI +0.007, +0.064+0.007+0.064
    sharpe
    +0.035
    95% ci
    +0.007, +0.064
    dof
    50
    snapshot 1 of 1 · · m5
    commit changepoint52 weekly commit points. No significant changepoint detected (|delta slope| within the noise floor).no significant changepoint
    changepoint
    none detected
    snapshot 1 of 1 · · m5
    code-leads-citation lag reserved

    reserved: citation series too short / axis absent for cross-correlation

    status
    reserved
    value
    insufficient data
    snapshot 1 of 1 · · m5
    axis alpha vs cohort reserved

    reserved: cohort N too small for regression (power ~0)

    status
    reserved
    value
    insufficient data
    snapshot 1 of 1 · · m5
    methodology gate snapshot 1 of 1 · · m5
    commit weeks
    52
    citation years
    0
    shipped
    3
    reserved
    3

    shipped

    • recency-swing
    • commit-sharpe
    • commit-changepoint

    reserved

    • code-leads-citation-lag
    • axis-alpha
    • gate-eta
    snapshot 7 of 7 · · m5

    Direct-dependents momentum (deps.dev)

    Direct-dependents axis: minimum of 14 usable points of the new quantity and 5 latest dependents not met.

    Coverage state
    below_floor
    Cohort z
    no axis
    OLS slope
    no reading
    Theil-Sen slope
    no reading
    Latest direct dependents
    2
    Confirmed-clean points
    1
    Reconstructed history points
    no reading
    As-of partition
    no reading
    Fragility veto
    no reading
    Rising vote
    no

    Source: deps.dev (Google), CC-BY 4.0. Modified: aggregated to system-level counts and momentum scores.

    Axis definition · Snapshot axis correlations

    Evidaxis · period 2026-11-07 · n = 1 system · method measurement detail · updated · version 868e3c39d9c7-b1 · record JSON · snapshot receipt