Pulse
2026-09-18-v3.0
Dataset
2026-10-27-catalog-ai-v2
Ruleset
b2e8889c66f7
Scanned
2026-10-27
Window
February–September 15, 2026
Catalog tracking observation. This repository is measured with the same fixed window and ruleset, but it is not part of the published benchmark or its aggregate claims.

Official Notion MCP Server

makenotion/notion-mcp-server ↗

makenotion/notion-mcp-server AI coding statistics: 40%

of 20 commits in February–September 15, 2026 were committed by an AI agent — a floor, not an estimate
Too little recent activity to publish. Only 20 commits landed in this window, so the percentage is noisy. Repositories below 100 are excluded from the index for this reason.
40% agent · top contributor 87.5%2 contributors
individual

One person is driving this. The headline number reflects a single contributor's workflow, not a project-wide shift.

8
agent commits
12
other considered commits
2
agent contributors
87.5%
largest contributor

What shapes this result

Mode, timing, and detected signatures show whether the result reflects broad adoption or one concentrated workflow.

Assisted or autonomous

8assisted
0autonomous

Assisted — a developer’s identity authored the commit and the agent added itself as co-author. Autonomous — a bot identity authored the commit without a human identity attached.

Agent share by month

Agent-attributed commit share by month
MonthAgent shareConsidered commits
2026-020%4
2026-0340%5
2026-050%1
2026-0685.7%7
2026-070%3

Peak month: 85.7%. Bars are scaled to that peak, not to 100%.

Which agents

AgentVendorCommitsShare
Claude CodeAnthropic735%
Cursor AgentAnysphere15%

Inspect the matches

Public commit samples let you inspect the signatures behind the aggregate result.

Matched commit samples

  • d7e3bbd6 on GitHubHarden deserializeParams against nested stringified params (#325)Claude Code
  • d282ce9c on GitHubSet up npm trusted publishing (OIDC) release workflows (#318)Claude Code
  • 604eef99 on GitHubAdd per-request Notion token passthrough for HTTP transport (#315)Claude Code
  • 4ce78611 on GitHubfix: allow MCP clients that double-serialize parameters to work correctly Cursor Agent

What entered the denominator

The result begins with commit history, removes merges and routine automation, and reports literal agent signatures as a lower bound.

Exclusion ledger

Commits in window20
Merge commits removed−0
CI / dependency bots removed−0
Considered20

Bots are excluded from the denominator entirely. Agent attribution requires a literal supported signature; no code-style inference is used.

Reproduce this observation

Run the same detector locally.

Deterministic signature matching; no code-style inference. Squash merges can remove trailers, so this result remains a measured floor.

npx qmmit-cli makenotion/notion-mcp-server

Scan another repository