Document API for AI-native software: render PDFs, e-sign, PAdES-seal, and verify.
Open Plugins distribution for Kamy — install Kamy PDF generation in Cursor, Claude Code, and any other Open-Plugins-compatible AI coding agent. This repository ships only the plugin manifest and the agent-facing assets (skill, rules, sub-agent, MCP config). The Kamy API, dashboard, SDK source, and template engine live in private infrastructure; this repo is the install surface for AI agents.…
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Open Plugins distribution for Kamy — install Kamy PDF generation in Cursor, Claude Code, and any other Open-Plugins-compatible AI coding agent. This repository ships only the plugin manifest and the agent-facing assets (skill, rules, sub-agent, MCP config). The Kamy API, dashboard, SDK source, and template engine live in private infrastructure; this repo is the install surface for AI agents. ## What's in this plugin Path | Component | Purpose | | Manifest | Name, version, metadata, declared…
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.