Tewip finds why each failing test failed - real bug, flaky test, environment, test data or changed selector - for any stack, from the command line, CI, or your editor.
Inferido de los transportes que declara este listado (stdio). Que un cliente no aparezca aquí no significa que se haya descartado: simplemente Forge no puede confirmarlo.
OPENAI_API_KEYClave de APIopcionalOptional. Turns on the AI layer for failures the deterministic rules cannot decide. Without it only the rules run, and Tewip says which layer decided each answer.
Declarado por el autor en el registro oficial de MCP. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
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.
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.
verdictTewip's answer, in the same words it would print for a personTewip's answer, in the same words it would print for a person
No se publicó ningún esquema de entrada para esta herramienta.
github_ci_reportLatest Tewip report from a GitHub repository's CI: which failing tests the change likely caused, why each failed, the next action, and any verified fix PR. Use for questions like "why did CI fail on my PR?".Latest Tewip report from a GitHub repository's CI: which failing tests the change likely caused, why each failed, the next action, and any verified fix PR. Use for questions like "why did CI fail on my PR?".
No se publicó ningún esquema de entrada para esta herramienta.
list_datasetsCollected failure datasets on this machine, with size and latest run.Collected failure datasets on this machine, with size and latest run.
No se publicó ningún esquema de entrada para esta herramienta.
list_failed_runsLatest runs with failing tests: run id, time, branch and number of failing tests.Latest runs with failing tests: run id, time, branch and number of failing tests.
No se publicó ningún esquema de entrada para esta herramienta.
explain_failureEverything the agent knows about one failing test: root cause, confidence and source, full evidence, history on this commit versus others, the next action and why.Everything the agent knows about one failing test: root cause, confidence and source, full evidence, history on this commit versus others, the next action and why.
No se publicó ningún esquema de entrada para esta herramienta.
test_planA test plan grounded in a project on this machine: its existing tests (read in full where related), the code the feature lives in, an optional git change and live pages, and the failures Tewip diagnosed there before. Returns risks, prioritised scenarios, what is already covered and what to automate…A test plan grounded in a project on this machine: its existing tests (read in full where related), the code the feature lives in, an optional git change and live pages, and the failures Tewip diagnosed there before. Returns risks, prioritised scenarios, what is already covered and what to automate…
No se publicó ningún esquema de entrada para esta herramienta.
recallWhat this project already concluded about a failure like this one: earlier failures that resemble it, what was decided, by which rule or which person, and the run each came from. Answers from records Tewip kept, never from a guess - and says plainly when nothing resembles it. Use before deciding wh…What this project already concluded about a failure like this one: earlier failures that resemble it, what was decided, by which rule or which person, and the run each came from. Answers from records Tewip kept, never from a guess - and says plainly when nothing resembles it. Use before deciding wh…
No se publicó ningún esquema de entrada para esta herramienta.
trace_requirementsJoins the plans Tewip wrote for a project to the tests that cover them and the runs that attempted them. A scenario counts as covered only when a real test can be named, and as passing only when a real run attempted it; everything else is reported as never run or not covered. Use for "are we ready…Joins the plans Tewip wrote for a project to the tests that cover them and the runs that attempted them. A scenario counts as covered only when a real test can be named, and as passing only when a real run attempted it; everything else is reported as never run or not covered. Use for "are we ready…
No se publicó ningún esquema de entrada para esta herramienta.
next_actionGiven a goal in plain words - "keep the checkout flow green" - says what Tewip would do next and why, from what it can actually see in the project. The order is fixed and published: a real bug first, then the environment, then flakiness, then anything failing it cannot explain, then a coverage gap.…Given a goal in plain words - "keep the checkout flow green" - says what Tewip would do next and why, from what it can actually see in the project. The order is fixed and published: a real bug first, then the environment, then flakiness, then anything failing it cannot explain, then a coverage gap.…
No se publicó ningún esquema de entrada para esta herramienta.
vouch_testsReads test files and says, per test, whether a change to the code could break them: which compare no value, which leave an expectation unfinished, which compare something with itself, which catch and discard their own failure, and which never run. Where the checking happens in a helper it cannot fo…Reads test files and says, per test, whether a change to the code could break them: which compare no value, which leave an expectation unfinished, which compare something with itself, which catch and discard their own failure, and which never run. Where the checking happens in a helper it cannot fo…
No se publicó ningún esquema de entrada para esta herramienta.
prove_tests_catch_bugsSin descripción publicadaEsta herramienta no publicó ninguna descripción. Forge no se la inventa.
is_the_work_doneSin descripción publicadaEsta herramienta no publicó ninguna descripción. Forge no se la inventa.
which_tests_to_runSin descripción publicadaEsta herramienta no publicó ninguna descripción. Forge no se la inventa.
what_will_this_migration_doSin descripción publicadaEsta herramienta no publicó ninguna descripción. Forge no se la inventa.
is_this_slowerSin descripción publicadaEsta herramienta no publicó ninguna descripción. Forge no se la inventa.
accessibility_barriersSin descripción publicadaEsta herramienta no publicó ninguna descripción. Forge no se la inventa.
project_standardsThe house rules this team has written down in .tewip/standards/, and whether a change keeps them. Returns two things kept carefully apart: rules Tewip checks and enforces (a forbid or require pattern over a set of files), and guidance it can only carry - prose for the parts no pattern captures, whi…The house rules this team has written down in .tewip/standards/, and whether a change keeps them. Returns two things kept carefully apart: rules Tewip checks and enforces (a forbid or require pattern over a set of files), and guidance it can only carry - prose for the parts no pattern captures, whi…
No se publicó ningún esquema de entrada para esta herramienta.
11 de 17 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.
Tewip finds why each failing test failed - real bug, flaky test, environment, test data or changed selector - for any stack, from the command line, CI, or your editor.
Los nombres enlazados abren el índice de Forge con todas las entradas que se observó que exponen esa herramienta. Ver todas las herramientas indexadas.
El rastreo se detuvo en el límite de profundidad 4. Nada por debajo de ese nivel llegó a resolverse.
El rastreo se detuvo en el límite de 60 paquetes. El resto del árbol nunca se resolvió.
Hay 36 paquetes resueltos más que no se dibujan aquí (límite de visualización: 24). Toda dependencia con avisos de seguridad se dibuja aunque se supere el límite. Inventario completo (SBOM CycloneDX)
54 dependencias declaradas nunca llegaron al árbol. Faltan en la resolución de Forge, no en el paquete.
+42 más sin listar. Los recuentos por motivo de arriba las incluyen todas.
No se siguen: peerDependencies. Este árbol cubre solo dependencias en tiempo de ejecución, así que lo que estas arrastren nunca se resolvió.