rea
Reverse engineer anything with agents, from app behavior down to native binaries.
Check if a dependency's license obligates you, based on how you ship. npm, PyPI, Go.
Skills que enseñan a la IA este tipo de trabajo; funcionan junto a este
Reverse engineer anything with agents, from app behavior down to native binaries.
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
Las listas se ordenan por una puntuación de uso (sobre 100) con estas partes
| Popularidad | 0/80 | Estrellas de GitHub o descargas semanales: la mayor cuenta 60, la menor 20 |
|---|---|---|
| Actualidad | 7/12 | Puntuación completa con una versión o cambio de código en 30 días |
| Sigue respondiendo | 8/8 | El endpoint en la nube respondió en la última revisión |
| Puntuación de uso | 15/100 |
Calidad: Pasó 5/5 revisiones básicas (se muestra, no ordena) · Impulso: Sin datos aún (Solo se usa en la pestaña En auge)
Elige la app de IA que usas y copia la configuración.
Que tu IA lo instale con una frase
Instala LicenseGuard. Sigue https://mcp.popnx.com/i/rccaoki-wq-license-guard.md, enséñame los comandos y espera mi OK antes de ejecutarlos.Pégala en una IA que trabaje en tu equipo (como Claude Code o Cursor). Lee nuestros pasos, te muestra los comandos y espera tu OK. Sin clave ni registro. · Ver el texto completo que lee tu IA
Pasó 5/5 revisiones · Lo que preguntas pasa por el servidor del autor (license-guard.rcc-aoki.workers.dev) · ✓ Comandos revisados el 13 nov 2026
Primero: ¿qué IA usas?
Elige tu app y los pasos aparecen abajo.
Funciona con Claude · unos 2 min
Sin clave y sin instalar nada · Configúralo una vez en claude.ai o en la app de escritorio y úsalo en el chat · las cuentas gratis pueden añadir 1 · en Team/Enterprise lo añade un Owner
CustomizeConnectors
Copia cada valor al campo con el mismo nombre en Claude y pulsa Continue
LicenseGuardhttps://license-guard.rcc-aoki.workers.dev/mcpPulsa Continue en la pantalla de inicio de sesión que detectó Claude · en Authentication elige lo que indique el autor (Sign in now, Sign in when needed o No sign in) y pulsa Add
+ConnectorsLicenseGuard
Usa LicenseGuard y dime qué puedes hacer por mí; luego muéstrame una cosa✓ Si Claude dice que está usando LicenseGuard o muestra una herramienta de LicenseGuard en la respuesta, ya está conectado
Nombres de menú comprobados con la ayuda de Anthropic el 11 nov 2026 · tu pantalla puede variar un poco según la versión
Funciona con ChatGPT según tu plan
MCP completo: ChatGPT Business, Enterprise o Edu en la web · Pro: conecta con permisos de lectura/obtención, así que las herramientas que cambian datos pueden no funcionar · Plus: no confirmado en la documentación; si ves una opción para añadir MCP propio en la página de plugins puedes probar · solo web
Plugins+Add custom MCP server
Pon un nombre, pega la dirección en Connection, marca el aviso de riesgo y pulsa Create as a plugin
LicenseGuardhttps://license-guard.rcc-aoki.workers.dev/mcpAbre un chat nuevo y elige LicenseGuard en tus plugins antes de escribir
Usa LicenseGuard y dime qué puedes hacer por mí; luego muéstrame una cosa✓ Si ChatGPT dice que está usando LicenseGuard o muestra una herramienta de LicenseGuard en la respuesta, ya está conectado
Nombres de menú comprobados con la ayuda de OpenAI el 11 nov 2026 · tu pantalla puede variar un poco según la versión
Funciona con Claude Code · unos 2 min
Sin clave y sin instalar nada
Mac: pulsa Command+Espacio y escribe Terminal · Windows: abre PowerShell
claude mcp add --transport http --scope user license-guard https://license-guard.rcc-aoki.workers.dev/mcpDeberías ver LicenseGuard en la lista como conectado
Usa LicenseGuard y dime qué puedes hacer por mí; luego muéstrame una cosa✓ Si Claude Code dice que está usando LicenseGuard o muestra una herramienta de LicenseGuard en la respuesta, ya está conectado
Nombres de menú comprobados con la ayuda de Anthropic el 11 nov 2026 · tu pantalla puede variar un poco según la versión
Funciona con Cursor · unos 2 min
Sin clave y sin instalar nada
Usa LicenseGuard y dime qué puedes hacer por mí; luego muéstrame una cosa✓ Si Cursor dice que está usando LicenseGuard o muestra una herramienta de LicenseGuard en la respuesta, ya está conectado
Nombres de menú comprobados con la ayuda de Cursor el 11 nov 2026 · tu pantalla puede variar un poco según la versión
Funciona con VS Code · unos 2 min
Sin clave y sin instalar nada
Usa LicenseGuard y dime qué puedes hacer por mí; luego muéstrame una cosa✓ Si VS Code dice que está usando LicenseGuard o muestra una herramienta de LicenseGuard en la respuesta, ya está conectado
Nombres de menú comprobados con la ayuda de VS Code el 11 nov 2026 · tu pantalla puede variar un poco según la versión
Otras apps que usan MCP, como Windsurf, Zed o Gemini CLI, añaden servidores de forma distinta. Míralo en la lista de apps
Ver todas las apps que usan MCP →
Dirección para apps que se conectan por la web
https://license-guard.rcc-aoki.workers.dev/mcpLa configuración JSON está en “Para desarrolladores”, abajo
Claude Code
claude mcp add --transport http --scope user license-guard https://license-guard.rcc-aoki.workers.dev/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"license-guard": {
"url": "https://license-guard.rcc-aoki.workers.dev/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"license-guard": {
"type": "http",
"url": "https://license-guard.rcc-aoki.workers.dev/mcp"
}
}
}Claude Code
claude mcp add --scope user license-guard -- docker run -i --rm ghcr.io/rccaoki-wq/license-guard:1.1.0Claude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"license-guard": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/rccaoki-wq/license-guard:1.1.0"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"license-guard": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/rccaoki-wq/license-guard:1.1.0"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"license-guard": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/rccaoki-wq/license-guard:1.1.0"
]
}
}
}Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
oci: ghcr.io/rccaoki-wq/license-guard:1.1.0Según cómo se conecta este servidor y la documentación de cada app, comprobado el 10 nov 2026.
Se conectan por internet en
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
Se ejecutan en tu computadora en
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Nombres y descripciones de las herramientas tal como los informó el servidor el 15 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.
check_dependency_licenseDetermine whether adding or keeping a single open source dependency creates a legal obligation, given how this project ships. Call this BEFORE adding a new dependency to a project, and when auditing an existing one. A permissive result means no source-disclosure duty; a blocked r
check_manifest_licensesScan an entire dependency manifest and report every dependency whose license creates an obligation for this shipping model. Use when reviewing a project as a whole, preparing for due diligence, or after a large dependency change. Pass a package-lock.json when one exists: problema
explain_licenseGiven an SPDX license identifier or expression, explain what it requires across every shipping model at once. Use when the question is about the license itself rather than a specific package — for example when comparing AGPL-3.0 against GPL-3.0 for a hosted service, or deciding w
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 19 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub rccaoki-wq, dueña del repo
Último cambio de código: hace 3 meses
Usa Apache-2.0
Respondió en 99 ms (HTTP 200)
No hace falta iniciar sesión
Leímos 3 descripciones de herramientas y no encontramos instrucciones ocultas para la IA
No revisado: solo se pueden revisar paquetes npm y PyPI con versión
Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.
[](https://mcp.popnx.com/en/servers/rccaoki-wq-license-guard)Pregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.
Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.
Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.
Aún no hay reseñas
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 5 de 5 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Funciona de las dos formas: instálalo en tu computadora o conéctate a la versión en la nube.
El repo de GitHub cambió por última vez hace 3 meses, y la última versión (1.1.0) llegó al registro hace 3 meses.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también sirve en apps que aceptan MCP remoto, como ChatGPT en la web (MCP completo en Business y superiores; Pro solo lectura).
En la misma categoría: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Misma categoría, otros creadores, comandos ya revisados. Primero los oficiales, luego por estrellas.
Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP servers
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| Este LicenseGuard | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Dónde se ejecuta | En la nube o instalado en tu equipo | Funciona en la nube, sin instalar nada | Funciona en la nube, sin instalar nada | Funciona en la nube, sin instalar nada | Funciona en la nube, sin instalar nada | En la nube o instalado en tu equipo |
| Necesita clave | No | No | No | No | No | No |
| Se añade con + en Claude | No | No | No | Sí | No | No |
| Revisiones básicas | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| Licencia | Apache-2.0 | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Precio | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro |
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
*English | 日本語*
Also listed on mcpservers.org, Smithery, the TensorBlock MCP Index, and the Docker MCP catalog.
**Does this dependency's license create an obligation for the way *you* ship software?**
Generic license scanners answer a different question — "what license is this?" — and then warn on everything. LicenseGuard evaluates the license against your distribution model, so the same license produces different verdicts depending on how the software reaches its users.
Live: https://licenseguard.tenchorooms.com
The workers.dev origin below is the same deployment, kept as the stable endpoint the MCP catalogs point at.
| How you ship | AGPL-3.0 dependency |
|---|---|
| SaaS (network-accessible) | blocked — §13 network clause |
| Internal use only | allowed |
| Distributed binary / on-prem | blocked — inherited GPL distribution terms |
| devDependency (never in the artifact) | allowed |
That last row is the whole point. A build-time linter under AGPL never ships, so it triggers nothing — but tools that warn on it anyway train people to ignore every warning they produce.
The same split runs through the rest of the license landscape, and the distinctions are not interchangeable:
Verdicts are stated as facts with the clause cited. LicenseGuard does not tell you what to do.
Does the GPL apply if I only host the software and never distribute it? No. GPL-3.0 triggers its obligations on distribution. Hosted SaaS is not distribution, so no obligation arises *today* — but shipping the same software later, as an on-prem deployment, a binary, or a published library, would trigger whole-work source disclosure.
Does the AGPL apply if I only host the software as a SaaS? Yes. AGPL-3.0 §13 requires that users interacting with a modified version over a network be offered the corresponding source of the whole work. This is the clause that makes AGPL behave differently from GPL for hosted services, and it is the entire practical difference between the two.
Do build-time and dev dependencies create license obligations? No. A dev dependency is not part of the artifact you ship, so distribution-triggered obligations do not arise. Tools that *emit code into your output*, such as code generators, are a separate case worth checking individually.
Is MIT safe for commercial use? Yes, in every distribution model. MIT asks for attribution and nothing more. Apache-2.0 reaches the same result while adding a patent grant and a NOTICE requirement — obligations, but ones that do not vary by how you ship.
Does static linking change the answer? Only for LGPL, and only for compiled languages. LGPL's design is that you may use the library in a proprietary work provided the user can replace it, which dynamic linking gives you and static linking does not. Go and Rust link statically by default, and nothing in Cargo.lock or go.sum says so.
Why does the same license give different answers for different projects? Because copyleft obligations attach to *events* — distributing, or letting users interact over a network — not to the presence of the code. Whether those events happen is a fact about your business, not about your repository, which is why a scanner that only reads your lockfile cannot decide it.
You need this when you are adding a dependency, not when you are searching the web. So the primary surface is an MCP tool, not a search result.
Hosted — nothing to install:
claude mcp add licenseguard --transport http https://license-guard.rcc-aoki.workers.dev/mcp
Local (stdio) — your manifest never leaves your machine. Only package names and versions are sent to public registries to look up licenses:
claude mcp add licenseguard -- docker run -i --rm ghcr.io/rccaoki-wq/license-guard:1.1.0
The image is published on every release and declared as an OCI package in the official MCP registry, so clients that read the registry can install it without any of this. To build it yourself instead: docker build -t licenseguard . && docker run -i --rm licenseguard.
Both paths run the same policy engine. They cannot disagree — an end-to-end suite (npm run e2e:stdio) pins them together.
Stateless Streamable HTTP, no authentication, no session state.
| Tool | When to call it |
|---|---|
check_dependency_license | Before adding a single dependency |
check_manifest_licenses | To audit a whole manifest or lockfile |
explain_license | To see what a license requires across every distribution model |
The JSON API returns the same verdicts:
curl "https://license-guard.rcc-aoki.workers.dev/api/pkg/pypi/pyload-ng?model=saas"
Scan a whole lockfile:
curl -X POST https://license-guard.rcc-aoki.workers.dev/api/scan \
-H 'content-type: application/json' \ -d "$(jq -Rs '{content: ., distributionModel: "saas"}' package-lock.json)"
An agent-facing index lives at /llms.txt.
Ecosystems: npm · PyPI · Go modules · crates.io · RubyGems · NuGet
| Format | Transitive deps | Registry lookups |
|---|---|---|
package-lock.json | yes | none — licenses are embedded |
pnpm-lock.yaml, yarn.lock | yes | yes (amortized by a shared cache) |
go.sum | yes | yes |
Cargo.lock, poetry.lock, uv.lock | yes | yes |
Gemfile.lock | yes | yes |
packages.lock.json | yes | yes |
package.json, requirements.txt, pyproject.toml, go.mod, Cargo.toml | direct only | yes |
.csproj, Directory.Packages.props, packages.config | direct only | yes |
| CycloneDX (JSON), SPDX (JSON) | yes | only where the document has no license |
Problem licenses usually arrive as a dependency of a dependency, not as something you added on purpose — so the lockfile path is the one that matters. package-lock.json v2/v3 embeds a license for every entry, which means a full transitive audit with zero network lookups and the exact versions that will actually be installed.
An incomplete scan is never reported as clean. Dependencies that could not be resolved appear as not-checked or review and are counted in the summary. They never become allowed.
A single scan performs at most 300 registry lookups, which bounds what one request can cost. Cached packages don't consume that budget, so the ceiling only binds on packages nobody has looked up yet — a first scan of a ~1000-crate Cargo.lock typically leaves a few dozen entries marked not-checked, and scanning again resolves them (measured: servo's 1043 crates reach zero unresolved published crates on the second pass). The result says so explicitly rather than quietly showing a shorter list.
Git dependencies and members of the workspace being scanned are reported as not-published instead, across every format that identifies them — Cargo.lock's source field, yarn's workspace: and git+ protocols, pnpm's tarball URLs, and package-lock.json's resolved. No public registry has license data for them, so they are never looked up. That is a different situation from hitting the lookup limit: re-scanning will not resolve them, and the result says so.
This matters for more than speed. A workspace member named after a package that also exists publicly — utils, core, or anything else generic — would otherwise be resolved against that unrelated public package and reported as allowed, because the workspace version (0.0.0-use.local) matches nothing and the lookup falls back to the latest release. Marking the origin is what stops a private package from inheriting a stranger's license.
Private registries are the deliberate exception. A resolved URL pointing somewhere other than npmjs is just as likely to be a transparent Artifactory or Nexus proxy serving the real public package, and nothing in the lockfile distinguishes the two — so those are still looked up, and still reported as unresolved if they fail.
CycloneDX and SPDX are read in JSON, including GitHub's {"sbom": …} envelope, so the response of gh api repos/OWNER/REPO/dependency-graph/sbom can be pasted unmodified. A license recorded in the document is used as-is; components without one are looked up. NOASSERTION, NONE, and LicenseRef-* are not treated as declarations, because they are the document saying it does not know.
Two things about real SBOMs are reported rather than smoothed over, because both change what the result means:
Most components carry no usable license. Across five published GitHub SBOMs, the document supplied the license for 8 of 44 components in expressjs/express and 1 of 51 in tokio-rs/tokio. The rest were resolved against a registry today. The result states the split instead of claiming the licenses came from the document.
A version range is not a version. GitHub's dependency-graph export writes the manifest range — ^2.0.0, >= 0.2.42,< 0.3.0 — into the purl *and* the version field: 36 of 44 components in express, 50 of 51 in tokio. There is no release under that string, so a scanner that passes it through resolves against the latest release while displaying a version that is not in your artifact. Ranges are not accepted as versions, and the result says how many components were affected. A lockfile does not have this problem, which is the practical reason to prefer one.
Components that are left out are counted and named rather than dropped, and the reason matters more than the count. GitHub Actions are not a gap. They run in CI, never enter the artifact, and so cannot create a distribution or network obligation — which is why they are excluded, and the result says exactly that instead of filing them under "unsupported". This is the difference between a fact about your software and a limitation of the tool, and it is not a rounding error: 52 of the 194 components across those five SBOMs are githubactions, the second-largest type after cargo. Package types the scan genuinely cannot read (maven, deb, …) are reported separately.
A document where *nothing* is checkable is rejected with the reason, not returned as an empty clean report — and the two reasons differ. gorilla/mux's SBOM is 100% GitHub Actions, so the answer is that the document contains nothing you ship; looking for a different scanner will not change that.
Phase 0 — validating willingness to pay. The MCP server and the free web too