com.faable/mcp

MCPcomunidaden línea
v4.17.0com.faableUnknownActualizado hace 1 dGitHub

Deploy apps from GitHub, read build/runtime logs, and manage your app's users from your AI agent.

Estado del endpointen línea
comprobado hace 1 día · 451 ms · requiere autenticación
100 % de las últimas 1 comprobación llegó a este endpoint
Funciona en
ClaudeCursorCopilotChatGPTGemini

Inferido de los transportes que declara este listado (streamable-http). Que un cliente no aparezca aquí no significa que se haya descartado: simplemente Forge no puede confirmarlo.

Indexado automáticamente desde fuentes públicas. Aún sin verificar por su desarrollador en Forge.Reclamar este listado →
1Estrellas en GitHub
hace 1 dÚltima actualización
Paquete
Autorcom.faable
LicenciaUnknown
Versión4.17.0
Fuentemcp-registry
Estado de confianza
B
60/100Bueno
Solo endpoint alojado: esta evaluación cubre quién lo publica y si responde, no el código que hay detrás. No se aplica análisis de CVE, dependencias ni código fuente, así que nada de lo que aparece aquí certifica que ese código esté limpio.
✓Listado en el índice de Forge+10/10
—Identidad del publicador verificada+0/30
→ Publicador: ejecuta `forge publish` desde el repo para reclamar la propiedad
—Verificación de dominio+0/10
→ Ahora mismo no está disponible para este tipo de listado: hoy la comprobación de dominio solo se ejecuta para paquetes publicados en npm, así que esta fila todavía no se puede conseguir aquí, sea lo que sea lo que haya alojado en el dominio.
✓Análisis de inyección de prompts · limpio+30/30
✓Análisis de ofuscación / exfiltración · limpio+20/20
Pégalo en Claude Code, Cursor o cualquier asistente de IA para corregir todas las carencias
EstadoIndexado por la comunidad
PublicadorSin verificar
FirmaSin firmar
Dominio—
Procedencia—
DependenciasSin auditar
Superficie de herramientas40 herramientas · 1 privilegiadas
Análisis de seguridad✓ LimpiovHEAD · hace 1 d¿Qué tan bien funciona este análisis?
EvaluacionesNinguna
Indexado18 oct 2026

La verificación confirma la identidad del publicador (la propiedad del repo), no la seguridad del código. El análisis de seguridad cubre los CVE conocidos y los scripts de instalación sospechosos.

Herramientas

40 herramientas · 1 privilegiadas
Extraído estáticamente del paquete publicadovHEAD · 1d ago

Leído del código que npm publica realmente, en el momento del análisis. El paquete nunca se ejecutó. Las herramientas registradas dinámicamente en tiempo de ejecución, o escondidas en código empaquetado o minificado, pueden pasarse por alto — así que esto es un mínimo de la superficie de herramientas, no un censo completo.

faableSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

whoamiThe Faable account this server acts as, the active project and its Auth tenant. Use it first when unsure whether the user is logged in or which project is active.

The Faable account this server acts as, the active project and its Auth tenant. Use it first when unsure whether the user is logged in or which project is active.

No se publicó ningún esquema de entrada para esta herramienta.

list_projectsThe user's Faable projects. Apps, domains and Auth tenants live in a project; pass its id as `project` to the other tools.

The user's Faable projects. Apps, domains and Auth tenants live in a project; pass its id as `project` to the other tools.

No se publicó ningún esquema de entrada para esta herramienta.

list_appsThe apps of a project, with their live phase, URL and linked repository. Start here to find the app the user means.

The apps of a project, with their live phase, URL and linked repository. Start here to find the app the user means.

No se publicó ningún esquema de entrada para esta herramienta.

get_appOne app: phase, URL, repository, deploy branch and mode, detected stack, and its newest deployment (which may have failed while an older one keeps serving). Use it to answer 'is my app up?' or 'what is deployed?'.

One app: phase, URL, repository, deploy branch and mode, detected stack, and its newest deployment (which may have failed while an older one keeps serving). Use it to answer 'is my app up?' or 'what is deployed?'.

No se publicó ningún esquema de entrada para esta herramienta.

list_deploymentsRecent deployments of an app, newest first, with phase, commit and the first line of any failure reason. Use it to find the deployment behind 'my last deploy failed'.

Recent deployments of an app, newest first, with phase, commit and the first line of any failure reason. Use it to find the deployment behind 'my last deploy failed'.

No se publicó ningún esquema de entrada para esta herramienta.

get_deploymentEverything recorded about one deployment: phase, commit, detected stack, the runnable artifact, the FULL failure reason and, when it failed, `fault` — whether it is the user's to fix (`user`) or Faable's (`platform`). Without `deployment`, the newest one of the app.

Everything recorded about one deployment: phase, commit, detected stack, the runnable artifact, the FULL failure reason and, when it failed, `fault` — whether it is the user's to fix (`user`) or Faable's (`platform`). Without `deployment`, the newest one of the app.

No se publicó ningún esquema de entrada para esta herramienta.

get_build_logsThe build output of a deployment — the first thing to read when a deploy failed and the user asks why. The cause is usually at the end. Without `deployment`, the newest one.

The build output of a deployment — the first thing to read when a deploy failed and the user asks why. The cause is usually at the end. Without `deployment`, the newest one.

No se publicó ningún esquema de entrada para esta herramienta.

get_runtime_logsWhat the running app printed (last 24 hours, up to 200 lines). Use it when the app is up but misbehaving, or crashes after starting. A deployment retired more than a day ago has none — read its build logs instead.

What the running app printed (last 24 hours, up to 200 lines). Use it when the app is up but misbehaving, or crashes after starting. A deployment retired more than a day ago has none — read its build logs instead.

No se publicó ningún esquema de entrada para esta herramienta.

get_app_trafficRequests the app served: status codes, busiest paths and failing paths. Trails reality by up to 15 minutes.

Requests the app served: status codes, busiest paths and failing paths. Trails reality by up to 15 minutes.

No se publicó ningún esquema de entrada para esta herramienta.

get_usageThis billing period's usage of a project: plan, apps, domains, deployments and egress.

This billing period's usage of a project: plan, apps, domains, deployments and egress.

No se publicó ningún esquema de entrada para esta herramienta.

get_quotaToday's deploy allowance of a project and the builds held waiting for it. Use it when a deploy did not start: a held build is waiting, not failing.

Today's deploy allowance of a project and the builds held waiting for it. Use it when a deploy did not start: a held build is waiting, not failing.

No se publicó ningún esquema de entrada para esta herramienta.

list_domainsCustom domains of an app and whether their DNS is verified.

Custom domains of an app and whether their DNS is verified.

No se publicó ningún esquema de entrada para esta herramienta.

check_domainDNS diagnostic of one custom domain: the CNAME it expects, what DNS answers today, and why it is not verified yet. `prevalidation_cname.ready` says whether the optional `_acme-challenge` record is in place, so the certificate is issued without waiting for the CNAME; `status.tls_state` is `ok` once…

DNS diagnostic of one custom domain: the CNAME it expects, what DNS answers today, and why it is not verified yet. `prevalidation_cname.ready` says whether the optional `_acme-challenge` record is in place, so the certificate is issued without waiting for the CNAME; `status.tls_state` is `ok` once…

No se publicó ningún esquema de entrada para esta herramienta.

list_secretsThe environment variables set on an app. Names only — values are masked and this tool can never reveal them. Use it to check whether a variable the app needs is set.

The environment variables set on an app. Names only — values are masked and this tool can never reveal them. Use it to check whether a variable the app needs is set.

No se publicó ningún esquema de entrada para esta herramienta.

list_auth_tenantsThe Faable Auth tenants (user directories) of a project. Most projects have one and every Auth tool uses it; with several, pass the right one as `tenant`.

The Faable Auth tenants (user directories) of a project. Most projects have one and every Auth tool uses it; with several, pass the right one as `tenant`.

No se publicó ningún esquema de entrada para esta herramienta.

list_auth_loginsWho logged in to the app's Faable Auth, newest first: one row per login with the user's email, when, from which IP and with which method. Answers 'who logged in recently?' or 'did X log in today?'. For 'how many', use count_auth_users.

Who logged in to the app's Faable Auth, newest first: one row per login with the user's email, when, from which IP and with which method. Answers 'who logged in recently?' or 'did X log in today?'. For 'how many', use count_auth_users.

No se publicó ningún esquema de entrada para esta herramienta.

count_auth_usersHow many users of the Auth tenant match: logged in since a time ('how many users logged in today / this week'), signed up since a time ('how many sign-ups this month'), suspended, or all of them. Counts users, not logins.

How many users of the Auth tenant match: logged in since a time ('how many users logged in today / this week'), signed up since a time ('how many sign-ups this month'), suspended, or all of them. Counts users, not logins.

No se publicó ningún esquema de entrada para esta herramienta.

list_auth_usersUsers of the Auth tenant. Find one by email or text, list the suspended ones, or sort: `-last_login` (most recent login first), `last_login` (longest without logging in), `-logins_count` (most active), `-createdAt` (newest sign-ups, the default). Sorting by last_login leaves out users who never log…

Users of the Auth tenant. Find one by email or text, list the suspended ones, or sort: `-last_login` (most recent login first), `last_login` (longest without logging in), `-logins_count` (most active), `-createdAt` (newest sign-ups, the default). Sorting by last_login leaves out users who never log…

No se publicó ningún esquema de entrada para esta herramienta.

get_auth_userOne user of the Auth tenant by id or email: profile, verification, suspension (and why), last login and login count, and the social identities they sign in with. Use it to confirm who a user is before suspending them, or to see why they can't log in (together with list_auth_logs).

One user of the Auth tenant by id or email: profile, verification, suspension (and why), last login and login count, and the social identities they sign in with. Use it to confirm who a user is before suspending them, or to see why they can't log in (together with list_auth_logs).

No se publicó ningún esquema de entrada para esta herramienta.

list_auth_logsThe Auth tenant's audit log, newest first: logins, failed logins (`status: failed`), sign-ups, password resets, admin changes (`type` prefix `admin.user`). Filter by user to answer 'why can't X log in?' — the failed attempts say why.

The Auth tenant's audit log, newest first: logins, failed logins (`status: failed`), sign-ups, password resets, admin changes (`type` prefix `admin.user`). Filter by user to answer 'why can't X log in?' — the failed attempts say why.

No se publicó ningún esquema de entrada para esta herramienta.

list_auth_sessionsThe devices a user is signed in on (one row per login session): IP, device, last activity and whether it is still active.

The devices a user is signed in on (one row per login session): IP, device, last activity and whether it is still active.

No se publicó ningún esquema de entrada para esta herramienta.

list_auth_connectionsHow users can log in to the Auth tenant: social providers (Google, GitHub…), passwordless (email or SMS codes) and username/password, and which are enabled.

How users can log in to the Auth tenant: social providers (Google, GitHub…), passwordless (email or SMS codes) and username/password, and which are enabled.

No se publicó ningún esquema de entrada para esta herramienta.

list_auth_clientsThe applications (OAuth clients) of the Auth tenant: web apps, SPAs, native apps and machine-to-machine clients.

The applications (OAuth clients) of the Auth tenant: web apps, SPAs, native apps and machine-to-machine clients.

No se publicó ningún esquema de entrada para esta herramienta.

list_github_reposThe GitHub repositories Faable can deploy: those the Faable GitHub App is installed on. Use it before create_app to find the repository the user means. When the app is not installed (or the repository is missing), give the user `install_url` — installing it is a step in their browser.

The GitHub repositories Faable can deploy: those the Faable GitHub App is installed on. Use it before create_app to find the repository the user means. When the app is not installed (or the repository is missing), give the user `install_url` — installing it is a step in their browser.

No se publicó ningún esquema de entrada para esta herramienta.

deploy_appBuild and deploy the latest commit of the app's deploy branch on Faable's servers — the same as a git push. Nothing is uploaded from this machine. With `wait`, returns once it is live (with the URL) or failed (with the reason and whether it is the user's code or Faable's); without it, returns the d…

Build and deploy the latest commit of the app's deploy branch on Faable's servers — the same as a git push. Nothing is uploaded from this machine. With `wait`, returns once it is live (with the URL) or failed (with the reason and whether it is the user's code or Faable's); without it, returns the d…

No se publicó ningún esquema de entrada para esta herramienta.

create_appCreate an app from a GitHub repository in a project, link it and start its first deploy (the dashboard's Create & connect). Needs the Faable GitHub App installed on the repository; if the link fails, the new app is removed and the error says what to fix.

Create an app from a GitHub repository in a project, link it and start its first deploy (the dashboard's Create & connect). Needs the Faable GitHub App installed on the repository; if the link fails, the new app is removed and the error says what to fix.

No se publicó ningún esquema de entrada para esta herramienta.

redeployRebuild a failed deployment from the source it recorded. Without `deployment`, the newest failed one. Refused for code older than what production serves.

Rebuild a failed deployment from the source it recorded. Without `deployment`, the newest failed one. Refused for code older than what production serves.

No se publicó ningún esquema de entrada para esta herramienta.

cancel_deploymentStop a deployment that is still queued or building. Production keeps serving what it served. Without `deployment`, the one in flight.

Stop a deployment that is still queued or building. Production keeps serving what it served. Without `deployment`, the one in flight.

No se publicó ningún esquema de entrada para esta herramienta.

set_secretsAdd or update environment variables of an app. The app restarts to apply them when a value changed. Returns the names added, updated and unchanged — never the values.

Add or update environment variables of an app. The app restarts to apply them when a value changed. Returns the names added, updated and unchanged — never the values.

No se publicó ningún esquema de entrada para esta herramienta.

add_domainAttach a custom domain to an app. Returns the CNAME record the user must create at their DNS provider; Faable verifies it and issues the certificate on its own. If the domain already serves traffic somewhere else, tell the user to create `prevalidation_cname` (`_acme-challenge.<fqdn>` CNAME) FIRST…

Attach a custom domain to an app. Returns the CNAME record the user must create at their DNS provider; Faable verifies it and issues the certificate on its own. If the domain already serves traffic somewhere else, tell the user to create `prevalidation_cname` (`_acme-challenge.<fqdn>` CNAME) FIRST…

No se publicó ningún esquema de entrada para esta herramienta.

configure_repoChange the deploy branch, the monorepo root directory ("" clears it) or the deploy mode (push: every push; ci: once CI tags a release; workflow: the repo's own GitHub workflow). Applies to the next deploy.

Change the deploy branch, the monorepo root directory ("" clears it) or the deploy mode (push: every push; ci: once CI tags a release; workflow: the repo's own GitHub workflow). Applies to the next deploy.

No se publicó ningún esquema de entrada para esta herramienta.

link_repoSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

delete_appprivilegiadaSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

deploy_directorySin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

suspend_auth_userSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

reinstate_auth_userSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

revoke_auth_sessionsSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

update_auth_client_fieldsSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

send_password_setupSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

31 de 40 herramientas publicaron una descripción.

Los nombres y descripciones de las herramientas los escribe el publicador y se muestran literalmente como texto inerte. Son las cadenas que un cliente MCP pasa al modelo, así que Forge las analiza en busca de patrones de inyección de prompts — cualquier hallazgo aparece junto al análisis de seguridad de arriba. «Privilegiada» es una coincidencia de palabra clave en el nombre de la herramienta, no una auditoría de lo que hace: un nombre inofensivo puede hacer cualquier cosa.

Acerca de

Deploy apps from GitHub, read build/runtime logs, and manage your app's users from your AI agent.

Palabras clave
mcp
Alternativas
Comparando superficies de herramientas…

Sin cobertura de dependencias

Esta entrada no publica ningún paquete de npm, así que Forge no tiene un árbol de dependencias para ella. Es una carencia de cobertura, no una afirmación de que no tenga dependencias.