MCP After Effects

TypeScript MCP server for Adobe After Effects (Windows & macOS) — project/comp/layer introspection, atomic undo-grouped

MCP Servers TypeScript Grade B Listed MIT
69.5/100
Rank #149 of 1308
Compare MCP After Effects

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-12 · 5d ago
Recent change
New

Is MCP After Effects safe? MCP After Effects scores 69.5/100 (Grade B), ranked #149 of 1308 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; no OSSF Scorecard result yet; 100% of recent commits are signed; last pushed 2026-08-12. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-16
Newly Listed
First tracked at rank #150
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
50.0
Activity sub-score · out of 100
#35

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-17 00:02 UTC · Repo last pushed 5 days ago

Activity & Reach

Stars
41
Forks
0
Last Push
2026-08-12
5 days ago
Commits (4 wk)
18
Downloads (7d)
775
npm
HN mentions (30d)
Open Issues
0
Rank Change
▲1
was #150

Analysis

HVTrust Dimensions vs MCP Servers

69.5 / 100 · 100.0% confidence

MCP After Effects MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.5 / 25
7.5 above avg 5.0
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.7 above avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.8
Maintenance60% last-push freshness · 40% commit activity
16.8 / 20
4.4 above avg 12.4
AdoptionLog-scaled stars · package downloads
7.7 / 20
1.9 above avg 5.8

Activity Inputs

50.0 / 100
StarsRepository reach
9.7 / 30
FreshnessLast push recency
24.3 / 25
ActivityRecent commits
15.9 / 25
CommunityFork signal
0.0 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
Not available
Signed Commits
100%
of last 100 commits verified

Is MCP After Effects safe?

MCP After Effects has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does MCP After Effects publish package provenance?
Yes. MCP After Effects's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does MCP After Effects have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for MCP After Effects. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is MCP After Effects actively maintained?
Actively maintained. The repository was pushed to within the last 5 day(s).
What license does MCP After Effects use?
MCP After Effects ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MCP After Effects's commits signed?
100% of the last 100 commits to MCP After Effects are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
MCP After Effects appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain MCP After Effects?

For maintainers

HVTrust scores MCP After Effects from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Listed 1
2026-08-16
Newly Listed
First tracked at rank #150

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 69.5 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/mcp-after-effects.svg)](https://hvtracker.net/agents/mcp-after-effects)
HTML:
<a href="https://hvtracker.net/agents/mcp-after-effects"><img src="https://hvtracker.net/badge/mcp-after-effects.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON