com.faable/mcp

MCPcommunautéen ligne
v4.17.0com.faableUnknownMis à jour il y a 1 jGitHub

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

État de l’endpointen ligne
vérifié il y a 1 jour · 451 ms · authentification requise
100 % des 1 vérification a atteint cet endpoint
Fonctionne dans
ClaudeCursorCopilotChatGPTGemini

Déduit des transports déclarés par cette annonce (streamable-http). Un client absent de cette liste n’est pas écarté pour autant — c’est simplement quelque chose que Forge ne peut pas confirmer.

Indexé automatiquement depuis des sources publiques. Pas encore vérifié par son développeur sur Forge.Revendiquer cette annonce →
1Étoiles GitHub
il y a 1 jDernière mise à jour
Paquet
Auteurcom.faable
LicenceUnknown
Version4.17.0
Sourcemcp-registry
Statut de confiance
B
60/100Bon
Endpoint hébergé uniquement : cette évaluation porte sur qui le publie et s’il répond, pas sur le code qui tourne derrière. Aucune analyse de CVE, de dépendances ou de code source ne s’applique ; rien ici ne garantit donc que ce code est sain.
✓Listé dans l’index Forge+10/10
—Identité de l’éditeur vérifiée+0/30
→ Éditeur : exécutez `forge publish` depuis le dépôt pour revendiquer la propriété
—Vérification de domaine+0/10
→ Actuellement indisponible pour ce type d’annonce — la vérification de domaine ne s’exécute aujourd’hui que pour les paquets adossés à npm, cette ligne ne peut donc pas encore être obtenue ici, quel que soit le contenu hébergé sur le domaine.
✓Analyse d’injection de prompt · propre+30/30
✓Analyse d’obfuscation / exfiltration · propre+20/20
Collez-le dans Claude Code, Cursor ou tout assistant d’IA pour combler toutes les lacunes
StatutIndexé par la communauté
ÉditeurNon vérifié
SignatureNon signé
Domaine—
Provenance—
DépendancesNon audité
Surface d’outils40 outils · 1 privilégiés
Analyse de sécurité✓ ProprevHEAD · il y a 1 jQuelle est l’efficacité de cette analyse ?
ÉvaluationsAucune
Indexé18 oct. 2026

La vérification confirme l’identité de l’éditeur (la propriété du dépôt), pas la sûreté du code. L’analyse de sécurité couvre les CVE connues et les scripts d’installation suspects.

Outils

40 outils · 1 privilégiés
Extrait statiquement du paquet publiévHEAD · 1d ago

Lu dans le code que npm livre réellement, au moment de l’analyse. Le paquet n’a jamais été exécuté. Les outils enregistrés dynamiquement à l’exécution, ou cachés dans du code empaqueté ou minifié, peuvent passer inaperçus — c’est donc un plancher de la surface d’outils, pas un recensement complet.

faableAucune description publiée

Cet outil n’a publié aucune description. Forge n’en invente pas.

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.

Aucun schéma d’entrée n’a été publié pour cet outil.

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.

Aucun schéma d’entrée n’a été publié pour cet outil.

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.

Aucun schéma d’entrée n’a été publié pour cet outil.

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?'.

Aucun schéma d’entrée n’a été publié pour cet outil.

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'.

Aucun schéma d’entrée n’a été publié pour cet outil.

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.

Aucun schéma d’entrée n’a été publié pour cet outil.

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.

Aucun schéma d’entrée n’a été publié pour cet outil.

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.

Aucun schéma d’entrée n’a été publié pour cet outil.

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.

Aucun schéma d’entrée n’a été publié pour cet outil.

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.

Aucun schéma d’entrée n’a été publié pour cet outil.

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.

Aucun schéma d’entrée n’a été publié pour cet outil.

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

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

Aucun schéma d’entrée n’a été publié pour cet outil.

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…

Aucun schéma d’entrée n’a été publié pour cet outil.

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.

Aucun schéma d’entrée n’a été publié pour cet outil.

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`.

Aucun schéma d’entrée n’a été publié pour cet outil.

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.

Aucun schéma d’entrée n’a été publié pour cet outil.

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.

Aucun schéma d’entrée n’a été publié pour cet outil.

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…

Aucun schéma d’entrée n’a été publié pour cet outil.

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).

Aucun schéma d’entrée n’a été publié pour cet outil.

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.

Aucun schéma d’entrée n’a été publié pour cet outil.

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.

Aucun schéma d’entrée n’a été publié pour cet outil.

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.

Aucun schéma d’entrée n’a été publié pour cet outil.

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.

Aucun schéma d’entrée n’a été publié pour cet outil.

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.

Aucun schéma d’entrée n’a été publié pour cet outil.

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…

Aucun schéma d’entrée n’a été publié pour cet outil.

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.

Aucun schéma d’entrée n’a été publié pour cet outil.

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.

Aucun schéma d’entrée n’a été publié pour cet outil.

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.

Aucun schéma d’entrée n’a été publié pour cet outil.

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.

Aucun schéma d’entrée n’a été publié pour cet outil.

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…

Aucun schéma d’entrée n’a été publié pour cet outil.

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.

Aucun schéma d’entrée n’a été publié pour cet outil.

link_repoAucune description publiée

Cet outil n’a publié aucune description. Forge n’en invente pas.

delete_appprivilégiéAucune description publiée

Cet outil n’a publié aucune description. Forge n’en invente pas.

deploy_directoryAucune description publiée

Cet outil n’a publié aucune description. Forge n’en invente pas.

suspend_auth_userAucune description publiée

Cet outil n’a publié aucune description. Forge n’en invente pas.

reinstate_auth_userAucune description publiée

Cet outil n’a publié aucune description. Forge n’en invente pas.

revoke_auth_sessionsAucune description publiée

Cet outil n’a publié aucune description. Forge n’en invente pas.

update_auth_client_fieldsAucune description publiée

Cet outil n’a publié aucune description. Forge n’en invente pas.

send_password_setupAucune description publiée

Cet outil n’a publié aucune description. Forge n’en invente pas.

31 outils sur 40 ont publié une description.

Les noms et descriptions d’outils sont écrits par l’éditeur et affichés tels quels, comme du texte inerte. Ce sont les chaînes qu’un client MCP transmet à un modèle, alors Forge y recherche des motifs d’injection de prompt — tout constat apparaît avec l’analyse de sécurité ci-dessus. « Privilégié » est une correspondance de mot-clé sur le nom de l’outil, pas un audit de ce qu’il fait : un nom anodin peut tout de même tout faire.

À propos

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

Mots-clés
mcp
Alternatives
Comparaison des surfaces d’outils…

Aucune couverture des dépendances

Cette entrée ne publie aucun paquet npm : Forge n'a donc pas d'arbre de dépendances pour elle. C'est une lacune de couverture — pas une affirmation qu'elle n'a aucune dépendance.