io.github.nelsonjordanme/clypt

MCPattested
v0.1.5io.github.nelsonjordanmeUnknownUpdated 2mo agonpmGitHub

Model Context Protocol server for Clypt — submit podcast URLs, receive clips and trailer.

Model Context Protocol server for Clypt. Lets AI agents (Claude Desktop, Cursor, Claude Code, any MCP-aware client) submit a podcast URL and receive clips, an optional trailer, show notes, a guest-share link, and the transcript. Pure shim over the public REST API at — three tools, no clever middleware. Tool | Wraps | Returns | | | — kicks the pipeline. Wall-clock to terminal: ~2-5 min for…

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
2mo agoLast update
Package
Authorio.github.nelsonjordanme
LicenseUnknown
Version0.1.5
Sourcemcp-registry
Trust Status
A
85/100Trusted
Listed in Forge index+10/10
Identity verified · attested build+20/20
Ed25519 publish signature+0/5
Included automatically when the publisher runs `forge publish`
Domain verification+0/5
Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
npm Trusted Publishing (Sigstore)+5/5
npm maintainer match+0/5
Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
CVE scan · clean+30/30
Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain
Provenance✓ Sigstore-verified · 8ad64e9
Dependencies60 resolved+ · none vulnerable
Tool surface3 tools · none privileged
Security scan✓ Cleanv0.1.5 · 2mo ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Model Context Protocol server for Clypt. Lets AI agents (Claude Desktop, Cursor, Claude Code, any MCP-aware client) submit a podcast URL and receive clips, an optional trailer, show notes, a guest-share link, and the transcript. Pure shim over the public REST API at — three tools, no clever middleware. Tool | Wraps | Returns | | | — kicks the pipeline. Wall-clock to terminal: ~2-5 min for audio/RSS sources, ~10-12 min for video + trailer. | | | Current job state. When , contains clips, optional…

Keywords
mcp