# tewip-ai

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.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.50.0
- **Author:** Mamuti Aishan
- **License:** Apache-2.0
- **npm:** tewip-ai
- **Source:** https://github.com/hmamut39/tewip
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-12T15:15:10.869Z
- **Version scanned:** 0.50.0
- **CVEs:** none found by OSV at scan time

## Tools

17 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `verdict` — Tewip's answer, in the same words it would print for a person
- `github_ci_report` — 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 
- `list_datasets` — Collected failure datasets on this machine, with size and latest run.
- `list_failed_runs` — Latest runs with failing tests: run id, time, branch and number of failing tests.
- `explain_failure` — 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 w
- `test_plan` — 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 li
- `recall` — 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 r
- `trace_requirements` — 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 
- `next_action` — 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
- `vouch_tests` — 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
- `prove_tests_catch_bugs`
- `is_the_work_done`
- `which_tests_to_run`
- `what_will_this_migration_do`
- `is_this_slower`
- `accessibility_barriers`
- `project_standards` — 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 an

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"tewip-ai\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"tewip-ai\"\n      ],\n      \"env\": {\n        \"OPENAI_API_KEY\": \"<YOUR_OPENAI_API_KEY>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `OPENAI_API_KEY` — OpenAI API Key (optional)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (0 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Moderate blast radius — holds an api key; runs on your machine.
- Floor 23, ceiling 23 (tier: moderate)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/tewip-ai
- Install plan: https://forgeregistry.com/api/v1/packages/tewip-ai/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/tewip-ai
- HTML page: https://forgeregistry.com/registry/tewip-ai
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.