io.github.chinlee2200-dotcom/bridgecore

Est-ce que io.github.chinlee2200-dotcom/bridgecore est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.chinlee2200-dotcom/bridgecore » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 5 outils

• do≈ 641 tokens

  One tool for 3,604 app capabilities (n8n catalog + OpenAPI + MCP): say what should happen; get the exact call. Plain words in ('send an sms to +1 213 555 0100 saying hello', 'add a row to google sheets'); the matching capability is found, its required inputs are checked (values you said out loud — emails, #channels, +phones — are filled for you), and the exact HTTP/MCP request that would be sent is returned, with `missing` naming any input still needed. Preview only: this server never sends the request and never accepts credentials. A 'when …' need or several steps returns one preview per step; n8n-only steps come back as an importable n8n workflow. Running the request for real is offered separately by the Bridgecore Apify Actor (apify.com/bridgecore/bridgecore-automation-planner).

  Paramètres, retour & exemple (3)

  Paramètres

  • need · string · requis
    What should happen, in plain words. One action to run it ('text +1… saying hi'); 'when …' for a flow.
  • inputs · object · optionnel
    Values for the capability's inputs by name (see `missing` in a dry run). Optional.
  • dry_run · boolean · optionnel
    Kept for compatibility; this server always previews and never sends.

  Exemple d'appel

  {"name": "do", "arguments": {"need": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ran": 1, "need": "texte", "note": "texte", "steps": [], "charged": 1, "dry_run": true, "fee_usd": 1, "workflow": {}}}

• find_recipe≈ 448 tokens

  Find a ready-made automation recipe for a plain-words need, e.g. 'when a typeform is submitted add a row to google sheets and send a slack message'. Returns the best matching recipes (apps chained with →, what it does, the n8n workflow JSON, the blanks to fill and accounts to connect) plus matching public n8n templates (title + official link). Covers connecting apps, automating a workflow, syncing tools, and getting notified when something happens.

  Paramètres, retour & exemple (2)

  Paramètres

  • need · string · requis
    What should happen, in plain words. Start with 'when …' for the trigger.
  • limit · integer · optionnel
    How many recipes to return (1-10).

  Exemple d'appel

  {"name": "find_recipe", "arguments": {"need": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"need": "texte", "recipes": [], "planned_steps": [], "public_templates": []}}

• inspect_workflow≈ 612 tokens

  Read an existing n8n workflow JSON (a template from n8n.io, an export, anything) and say what it would do before it runs: every node's label (read-only / reversible / irreversible, computed from the node's own resource + operation), which irreversible steps (send, post, delete, pay) would run with nobody asked, which steps already have an approval in front of them, and which nodes have no account connected. With add_gates=true it returns a copy of the workflow with a one-tap Approve / Decline step (Slack, Telegram, Gmail…) wired in front of every such step. Nothing is run; the original is not modified.

  Paramètres, retour & exemple (3)

  Paramètres

  • ask_via · string · optionnel · slack | telegram | gmail | discord | microsoftteams | whatsapp
    Where the Approve / Decline message goes.
  • workflow · object · requis
    The n8n workflow JSON (nodes + connections), as exported or as a template's JSON.
  • add_gates · boolean · optionnel
    Also return `gated_workflow`: a copy that asks before every irreversible step.

  Exemple d'appel

  {"name": "inspect_workflow", "arguments": {"workflow": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"name": "texte", "gated": [], "nodes": [], "risky": [], "counts": {}, "to_fill": [], "verdict": "texte", "verified": {}, "gated_workflow": {}, "accounts_missing": []}}

• make_n8n_workflow≈ 667 tokens

  Generate an importable n8n workflow JSON from a plain-words need, with every node wired in order, values said out loud already filled (emails, #channels, trigger events), plus the list of blanks only the person can fill and the credentials to connect. Shape-checked; the person tests it in n8n before turning it on. Say 'and ask me first' (or approval='always') and a one-tap approval gate — a Slack/Telegram/Gmail message with Approve / Decline buttons — goes in front of the step, so nothing is sent, posted, deleted or paid until the person taps Approve.

  Paramètres, retour & exemple (3)

  Paramètres

  • name · string · optionnel
    Workflow name shown in n8n (optional; made from the need when left out).
  • need · string · requis
    What should happen, in plain words. Start with 'when …' for the trigger; add 'and ask me first' before a step the person wants to approve.
  • approval · string · optionnel · auto | always | never
    auto = gate the steps the need asks to approve ('ask me first'); always = gate every irreversible step (send, post, delete, pay); never = no gates.

  Exemple d'appel

  {"name": "make_n8n_workflow", "arguments": {"need": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"need": "texte", "links": {}, "steps": [], "to_fill": [], "accounts": [], "approval": {}, "problems": [], "workflow": {}, "how_to_import": "texte"}}

• plan_automation≈ 336 tokens

  Turn a plain-words need into steps (one trigger + actions) and pick the concrete tool for each step from 3,000+ app capabilities (n8n nodes, OpenAPI, MCP). Reports a gap when the named app cannot do a step instead of substituting another app.

  Paramètres, retour & exemple (2)

  Paramètres

  • need · string · requis
    What should happen, in plain words: 'when <trigger> <action>, then <action>'.
  • alternatives · integer · optionnel
    Runner-up tools to list per step (1-5).

  Exemple d'appel

  {"name": "plan_automation", "arguments": {"need": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"need": "texte", "steps": []}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.usebridgecore.com/