TestChimp
NPM · @TESTCHIMP/CLI · 2 COMPONENTS
QA platform for agents: coverage signals, in-repo test plans, verified tests and release governance.
Available components
Last scanned (22 hours ago)
Scores higher than 50% of npm servers
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 11016 tokens (~112/item across 98 items; 98 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage68
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 3% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 98 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
- Package version: 0.1.89 → 0.1.93 functional
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/@testchimp/cli@0.1.93
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list-api-operation-interactions List API Operation Interactions ~68
List recorded API operation interactions. Requires testId and/or operationId. Defaults to REAL interactions; limit is capped at 100.
| Name | Type | Req | Description |
|---|---|---|---|
| interactionType | string | – | – |
| limit | integer | – | – |
| operationId | string | – | – |
| testId | string | – | – |
No output schema declared.
No examples provided.
list-api-operation-services List API Operation Services ~49
List API operation service resources for the project (configured OpenAPI root file paths + operation counts). Use rootFilePath as the service resource id for list-api-operations / get-api-operation-detail.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list-api-operations List API Operations ~143
List API operations for a service resource with covering-test previews, coverageSummary scores, observability mapping state, and runtimeObservation from the latest finalized production daily summary (with latest-hour fallback). runtimeObservation may include window bounds, requestCount/rpm, errorCount/errorRate, p50/p95/p99LatencyMs, status-class counts, and syncStatus. Missing observability is unknown/not configured, not zero. Use these signals to prioritize uncovered high-volume/high-error operations; prefer --root-file-path.
| Name | Type | Req | Description |
|---|---|---|---|
| includeManual | boolean | – | – |
| includeRemoved | boolean | – | – |
| rootFilePath | string | – | – |
| serviceKey | string | – | – |
No output schema declared.
No examples provided.
list-bunnyshell-environment-events List BunnyShell Environment Events ~59
Troubleshooting: list BunnyShell platform events for an environment.
| Name | Type | Req | Description |
|---|---|---|---|
| bnsEnvironmentId | string | yes | – |
| eventStatus | string | – | – |
| eventType | string | – | – |
| page | integer | – | – |
No output schema declared.
No examples provided.
list-bunnyshell-workflow-jobs List BunnyShell Workflow Jobs ~44
Troubleshooting: list BunnyShell workflow jobs for an environment.
| Name | Type | Req | Description |
|---|---|---|---|
| bnsEnvironmentId | string | yes | – |
| page | integer | – | – |
No output schema declared.
No examples provided.
list-meeting-filter-options List Meeting Filter Options ~60
List the labels, participants (key = user id or email, with display name), and participant email domains that appear on team-wide Meeting Bots meetings. Use the exact values as list-meetings filters (labels, participantKeys, participantDomains).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list-meetings List Meetings ~223
List / search cloud-synced Meeting Bots meetings, newest first, like the Meetings page filters + search. Team-wide meetings only (visibility: all team members). Filters: from / to (YYYY-MM-DD, ISO datetime, or epoch millis; inclusive), labels, participantKeys (user id or email), participantDomains, searchText (full-text over title + transcript; hits include a searchSnippet with matches wrapped in ⟦ ⟧). Returns meetingId, title, startMillis, labels, participants, summaryStatus; page with nextPageToken. Use list-meeting-filter-options for exact label / domain / participant values, then get-meeting-transcript (summaryOnly first) per hit.
| Name | Type | Req | Description |
|---|---|---|---|
| endDateMillis | – | – | – |
| from | – | – | – |
| labels | array | – | – |
| pageSize | integer | – | – |
| pageToken | string | – | – |
| participantDomains | array | – | – |
| participantKeys | array | – | – |
| searchText | string | – | – |
| startDateMillis | – | – | – |
| to | – | – | – |
No output schema declared.
No examples provided.
list-perf-baselines List Perf Baselines ~47
List promoted performance baselines, optionally filtered by TestChimp id.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| testchimpId | string | – | – |
No output schema declared.
No examples provided.
list-perf-runs List Perf Runs ~111
List performance runs, optionally filtered by TestChimp id, JOURNEY/COMPOSITE kind, branch, profile, dataset, LLM mode, or environment.
| Name | Type | Req | Description |
|---|---|---|---|
| branchName | string | – | – |
| dataset | string | – | – |
| environment | string | – | – |
| kind | string | – | – |
| limit | integer | – | – |
| llmMode | string | – | – |
| offset | integer | – | – |
| profile | string | – | – |
| testchimpId | string | – | – |
No output schema declared.
No examples provided.
list-policies List Policies ~39
List policy files for an optional workflow-id. Marks isDefault when filename is <workflow-id>.policy.md.
| Name | Type | Req | Description |
|---|---|---|---|
| workflowId | string | – | – |
No output schema declared.
No examples provided.
list-related-perf-tests List Related Perf Tests ~68
Find JOURNEY and, by default, COMPOSITE performance tests related to scenario titles and/or TestChimp ids.
| Name | Type | Req | Description |
|---|---|---|---|
| includeComposites | boolean | – | – |
| limit | integer | – | – |
| scenarioTitles | array | – | – |
| testchimpIds | array | – | – |
No output schema declared.
No examples provided.
list-rum-environments List RUM Environments ~42
List distinct RUM environment tags for this project. Call this first to choose environment values for TrueCoverage ExecutionScope.environment (e.g. QA, production).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list-screen-states List Screen States ~50
Fetch the project's screen/state vocabulary (relational atlas) for SmartTests and traces. Optional environment field is accepted for forward compatibility; v1 may be project-global.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | – |
No output schema declared.
No examples provided.
list-semantic-nearby List Semantic Nearby ~116
List semantically nearby entities across types (Story/Scenario/Test/Issue/Event). TEST uses TestLocator; STORY/SCENARIO/ISSUE use sourceOrdinalId; EVENT uses sourceEventTitle. Response TEST hits include TestLocator (never platform test_id).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| sourceEntityType | string | yes | – |
| sourceEventTitle | string | – | – |
| sourceOrdinalId | number|string | – | – |
| sourceTest | object | – | – |
| targetEntityTypes | array | – | – |
No output schema declared.
No examples provided.
list-semantic-similar-tests List Semantic Similar Tests ~66
List semantically similar SmartTest pairs in scope using TestLocators (no test_id). Pairs are deduped (A→B only when A.testId < B.testId). Distinct-marked pairs are excluded.
| Name | Type | Req | Description |
|---|---|---|---|
| scope | object | – | – |
No output schema declared.
No examples provided.
list-test-scenarios-for-scope List Test Scenarios For Scope ~107
List in-scope test scenarios (ordinalId + title only) for exactly one locator: a named test run, a release label, or a platform plans folder/file path. Does not return markdown — use get-test-scenarios for detail by known ordinal. Use when executing tests for a plans path, release, or named test run.
| Name | Type | Req | Description |
|---|---|---|---|
| namedTestRunId | string | – | – |
| plansPath | string | – | – |
| release | string | – | – |
No output schema declared.
No examples provided.
list-tests-awaiting-verification List Tests Awaiting Verification ~120
List SmartTests whose latest executions still need human verification before they earn a verified badge (testId, testName, filePath, scenarioId / scenarioOrdinalId / scenarioTitle, verificationStatus NOT_VERIFIED or VERIFIED_STALE, reportedAtMillis, workflowExecutionId). Optional userId narrows to tests authored for that user (defaults to the OAuth token's user); optional limit. Use after writing E2E tests to prompt the user to verify the executions.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| userId | string | – | – |
No output schema declared.
No examples provided.
list-workflow-catalog List Workflow Catalog ~28
List supported TestChimp workflows with Active / Disabled / Missing Config status for the project.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list-workflow-executions List Workflow Executions ~99
List recent workflow executions for the project, optionally filtered by workflowId.
| Name | Type | Req | Description |
|---|---|---|---|
| assignedToMeOnly | boolean | – | Only executions assigned to the calling user (OAuth user, or the bot's owner with --bot). |
| limit | integer | – | – |
| offset | integer | – | – |
| pendingApprovalOnly | boolean | – | Only PENDING_INVOKE_APPROVAL / PLANNED executions. |
| workflowId | string | – | – |
No output schema declared.
No examples provided.
mark-entity-distinct Mark Entity Distinct ~103
Mark two same-type entities as distinct. TEST uses TestLocators; STORY/SCENARIO/ISSUE use ordinals; EVENT uses titles.
| Name | Type | Req | Description |
|---|---|---|---|
| entityType | string | yes | – |
| focusEventTitle | string | – | – |
| focusOrdinalId | number|string | – | – |
| focusTest | object | – | – |
| otherEventTitle | string | – | – |
| otherOrdinalId | number|string | – | – |
| otherTest | object | – | – |
No output schema declared.
No examples provided.
mark-plan-items-implementation-done Mark Plan Items Implementation Done ~80
Mark user stories and/or test scenarios implementation-complete in platform lifecycle (DB only; does not rewrite plan markdown). Use scenarioOrdinalIds / userStoryOrdinalIds (numeric parts of TS-<n> / US-<n>).
| Name | Type | Req | Description |
|---|---|---|---|
| scenarioOrdinalIds | array | – | – |
| userStoryOrdinalIds | array | – | – |
No output schema declared.
No examples provided.
mark-semantic-tests-distinct Mark Semantic Tests Distinct ~56
Mark two SmartTests as legitimately distinct (symmetric) using TestLocators. Agent/API calls use marked_by_user_id = 0.
| Name | Type | Req | Description |
|---|---|---|---|
| distinctTest | object | yes | – |
| focusTest | object | yes | – |
No output schema declared.
No examples provided.
mark-tests-for-review Mark Tests For Review ~208
Report existing SmartTests that an agent patched so humans can re-verify. Always send per-test confidence 0–100 (higher = less need for human review). Do not read project config. Call only from fix-test-execution after test-incorrect patches (never from run-qa / create-tests; never for product-broken cases). Optional agentTraceability / workflowExecutionId / gitCommitSha / branchName.
| Name | Type | Req | Description |
|---|---|---|---|
| actorType | string | – | – |
| agentModel | string | – | – |
| agentTraceability | object | – | – |
| branchName | string | – | – |
| cliVersion | string | – | – |
| gitCommitSha | string | – | – |
| gitSha | string | – | – |
| policyFile | string | – | – |
| policyVersion | string | – | – |
| skillVersion | string | – | – |
| tests | array | yes | – |
| userId | string | – | – |
| workflowExecutionId | string | – | – |
| workflowId | string | – | – |
No output schema declared.
No examples provided.
promote-perf-baseline Promote Perf Baseline ~145
Promote a performance run as the baseline for an environment class. Optional agent traceability records the mutation.
| Name | Type | Req | Description |
|---|---|---|---|
| actorType | string | – | – |
| agentModel | string | – | – |
| agentTraceability | object | – | – |
| branchName | string | – | – |
| cliVersion | string | – | – |
| envClass | string | yes | – |
| gitSha | string | – | – |
| policyFile | string | – | – |
| policyVersion | string | – | – |
| runId | string | yes | – |
| skillVersion | string | – | – |
| userId | string | – | – |
| workflowExecutionId | string | – | – |
| workflowId | string | – | – |
No output schema declared.
No examples provided.
provision-ephemeral-environment Provision Ephemeral Environment ~47
Create a BunnyShell ephemeral environment (create + deploy trigger only). Prefer provision-ephemeral-environment-and-wait for normal flows.
| Name | Type | Req | Description |
|---|---|---|---|
| branchName | string | – | – |
No output schema declared.
No examples provided.
provision-ephemeral-environment-and-wait Provision Ephemeral Environment And Wait ~72
Provision a BunnyShell ephemeral environment, then poll until deployed and component URLs are available. Progress is logged to stderr (CLI) or MCP logging when supported.
| Name | Type | Req | Description |
|---|---|---|---|
| branchName | string | – | – |
| maxWaitMinutes | number | – | – |
| pollIntervalSeconds | number | – | – |
No output schema declared.
No examples provided.
register-bot-profile Register Bot Profile ~201
Register or replace this QA bot's profile and event subscriptions atomically (mutating — confirm with the user first). role: QA_LEAD | PM | QA_ENGINEER | DEVELOPER. responsibilities: the user's own words. capabilities: REQUIREMENTS_UPDATE, E2E_AUTHORING, ISSUE_FIX, MANUAL_TEST_COORDINATION, TEST_BATCH_FIX, QA_POSTURE. subscriptions: [{eventType, filters:[{field, op:'eq', value}]}] where value may be 'me' (e.g. git-push author=me, issue-assigned assignee=me, e2e-batch-completed). Derive subscriptions from capabilities per the testchimp skill's bot onboarding guide. botId defaults to the bot-id header / OAuth token.
| Name | Type | Req | Description |
|---|---|---|---|
| botId | string | – | – |
| capabilities | array | – | – |
| responsibilities | string | – | – |
| role | string | yes | – |
| subscriptions | array | – | – |
No output schema declared.
No examples provided.
report-agent-action Report Agent Action ~324
Report a mutating agent action under a stable workflow-execution-id (ULID). First call for an id creates the workflow_executions row; later calls append Activity timeline rows (AGENT_WORKFLOW_ACTIVITY). Actions land on the entity's Activity timeline (plans, issues, SmartTest file). entityType: USER_STORY | SCENARIO | SMART_TEST | POLICY | ISSUE | TEST_EXECUTION | TEST_INVOCATION_BATCH | EXPLORATION | EVENT | WORKFLOW. actionType: CREATED | UPDATED | DELETED | ANALYZED | IMPLEMENTED | ACTION_COMPLETED | ACTION_FAILED. Identity: SMART_TEST uses `test` (TestLocator: folderPath/fileName/testSuite/testName); other artifact types use `entityIdentity` (ordinal / filename / opaque id). Do not use platform UUIDs. Completion (ACTION_COMPLETED / ACTION_FAILED): entityType WORKFLOW and entityIdentity = catalog workflow_id.
| Name | Type | Req | Description |
|---|---|---|---|
| actionType | string | yes | – |
| actorType | string | – | – |
| agentModel | string | – | – |
| branchName | string | – | – |
| cliVersion | string | – | – |
| entityIdentity | string | – | – |
| entityType | string | yes | – |
| gitSha | string | – | – |
| policyFile | string | – | – |
| policyVersion | string | – | – |
| skillVersion | string | – | – |
| test | object | – | – |
| traceability | object | – | – |
| userId | string | – | – |
| workflowExecutionId | string | yes | – |
| workflowId | string | yes | – |
No output schema declared.
No examples provided.
report-dast-findings Report DAST Findings ~92
Upload a ZAP Traditional JSON report for a security scan. Pass --id and --report-file <path>. Backend parses alerts, dedupes by bug hash, and inserts new SECURITY bugs linked to the scan. Does not mark the scan COMPLETED — the DAST playbook calls update-scan-progress COMPLETED after this.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| reportFile | string | yes | – |
No output schema declared.
No examples provided.
report-deps-findings Report Deps Findings ~94
Upload a full Trivy JSON report for a dependency security scan. Pass --id and --report-file <path>. Backend stores the report, filters by security profile / ignore-unfixed, dedupes, and inserts SECURITY bugs. Does not mark the scan COMPLETED — the deps playbook calls update-scan-progress COMPLETED after this.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| reportFile | string | yes | – |
No output schema declared.
No examples provided.
report-requirement-quality-findings Report Requirement Quality Findings ~144
Upload a DeFOSPAM / requirement quality analysis report for a user story or test scenario (local-agent path). Pass full RequirementQualityReport JSON via --report-file or --json-input {"report":{...}}. report.subject.subjectEntityId is required; use --subject-type + --ordinal-id to resolve via get-requirement-quality-report, or set subjectEntityId explicitly. Backend merges IGNORED/APPLIED findings carry-forward on re-report.
| Name | Type | Req | Description |
|---|---|---|---|
| ordinalId | integer | – | – |
| report | object | – | – |
| reportFile | string | – | – |
| subjectEntityId | string | – | – |
| subjectType | string | – | – |
No output schema declared.
No examples provided.
report-sast-findings Report SAST Findings ~96
Upload a full Semgrep CLI JSON report for a SAST security scan. Pass --id and --report-file <path>. Backend stores the raw report, parses results, dedupes by bug hash, and inserts new SECURITY bugs. Does not mark the scan COMPLETED — the SAST playbook calls update-scan-progress COMPLETED after this.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| reportFile | string | yes | – |
No output schema declared.
No examples provided.
report-secrets-findings Report Secrets Findings ~95
Upload a full Gitleaks JSON report for a secrets security scan. Pass --id and --report-file <path>. Backend redacts secret payloads, stores the report, dedupes by bug hash, and inserts SECURITY bugs. Does not mark the scan COMPLETED — the secrets playbook calls update-scan-progress COMPLETED after this.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| reportFile | string | yes | – |
No output schema declared.
No examples provided.
save-workspace-creds Save Workspace Creds ~293
Save the project API key for local runners in <folder>/.testchimp/mcp.json (Studio format: mode 0600, dir 0700, .testchimp/ gitignored) and map the folder in ~/.testchimp/projects.json. Fetches the key with the current MCP auth — do not pass the key, and the response never includes it. Local stdio MCP only (omitted on hosted mcp.testchimp.io). Hosted / plugin agents: call get-project-credentials and write <repo>/.testchimp/mcp.json with a file-write tool (never put the key in a shell command).
| Name | Type | Req | Description |
|---|---|---|---|
| backendUrl | string | – | – |
| folder | string | yes | Repository root on the machine running this MCP server. Writes <folder>/.testchimp/mcp.json (mode 0600, dir 0700) and maps the folder in ~/.testchimp/projects.json. Hosted mcp.testchimp.io cannot wri… |
| ingressUrl | string | – | – |
| projectId | string | – | Defaults to the connection's project from get-project-credentials. |
| projectName | string | – | – |
| reassign | boolean | – | Replace another project's key in this folder and move the folder mapping to this project. |
No output schema declared.
No examples provided.
send-feedback Send Feedback ~174
Send feedback to the TestChimp team ("contact us" for agents). Use when you hit a TestChimp bug or confusing error, the user struggles with or complains about TestChimp, a capability is missing, or the skill / docs were wrong or unclear. category: BUG | USER_STRUGGLE | FEATURE_REQUEST | DOCS_GAP | OTHER. message: what happened, in plain words. context: what you were doing (workflow, tool or command, error text, CLI / skill versions). agentName: your host, e.g. Cursor, Claude Code, Grok QA bot. Never include secrets, API keys or tokens. Mention to the user that you sent it.
| Name | Type | Req | Description |
|---|---|---|---|
| agentName | string | – | – |
| category | string | – | – |
| context | string | – | – |
| message | string | yes | – |
No output schema declared.
No examples provided.
unmark-entity-distinct Unmark Entity Distinct ~94
Remove a distinct mark between two same-type entities (same identity rules as mark-entity-distinct).
| Name | Type | Req | Description |
|---|---|---|---|
| entityType | string | yes | – |
| focusEventTitle | string | – | – |
| focusOrdinalId | number|string | – | – |
| focusTest | object | – | – |
| otherEventTitle | string | – | – |
| otherOrdinalId | number|string | – | – |
| otherTest | object | – | – |
No output schema declared.
No examples provided.
update-git-folder-mapping Update Git Folder Mapping ~118
Update mapped plans/tests folder paths (and optional repository / plans branch) on the platform. Agent scaffolds folders in a PR; this records platform mapping.
| Name | Type | Req | Description |
|---|---|---|---|
| plansBranch | string | – | Branch plans sync against. Empty string resets to the repository default branch. |
| plansFolderPath | string | – | – |
| plans_folder_path | string | – | – |
| repositoryFullName | string | – | – |
| repository_full_name | string | – | – |
| testsFolderPath | string | – | – |
| tests_folder_path | string | – | – |
No output schema declared.
No examples provided.
update-issue-status Update Issue Status ~264
Update a TestChimp issue status by ordinal id (same flexible issueId formats as get-issue-details). status must be one of: ACTIVE, IGNORED, FIXED, DUPLICATE, IN_PROGRESS_BUG, ARCHIVED_BUG, BLOCKED. For /testchimp fix issue: set IN_PROGRESS_BUG after applying a code fix; set FIXED only after user confirmation / commits pushed. Optional ignoreReason when status is IGNORED: INTENDED_BEHAVIOUR | INACCURATE_ASSESSMENT | NOT_IMPORTANT. Optional agentTraceability records UPDATED Activity inline (requires both workflowId and workflowExecutionId for Activity attachment).
| Name | Type | Req | Description |
|---|---|---|---|
| actorType | string | – | – |
| agentModel | string | – | – |
| agentTraceability | object | – | – |
| branchName | string | – | – |
| cliVersion | string | – | – |
| gitSha | string | – | – |
| ignoreReason | string | – | – |
| issueId | string | yes | – |
| policyFile | string | – | – |
| policyVersion | string | – | – |
| skillVersion | string | – | – |
| status | string | yes | – |
| userId | string | – | – |
| workflowExecutionId | string | – | – |
| workflowId | string | – | – |
No output schema declared.
No examples provided.
update-plan-items-lifecycle-status Update Plan Items Lifecycle Status ~104
Update lifecycle_fields.status for one user story or test scenario (DB only; does not rewrite plan markdown). entityType: story | scenario; ordinalId: numeric US-/TS- ordinal; status: draft | ready | in progress | blocked | done | archived. Used after /testchimp implement to set status to ready (unless policy overrides).
| Name | Type | Req | Description |
|---|---|---|---|
| entityType | string | yes | – |
| ordinalId | integer | yes | – |
| status | string | yes | – |
No output schema declared.
No examples provided.
update-project-init-status Update Project Init Status ~164
Merge project-init progress fields for the current project. Pass a `status` object with snake_case keys (platform_comms, folder_mapping, connect_to_test_env, ci_wiring, and optional import_plans, import_tests, smoke_validation). The server recomputes overall_complete when required items are DONE — do not send it (overallComplete / overall_complete are ignored). Legacy camelCase keys from older skills are forwarded to the backend.
| Name | Type | Req | Description |
|---|---|---|---|
| status | object | yes | Partial ProjectInitStatus. Advertised keys are snake_case: platform_comms, folder_mapping, connect_to_test_env, ci_wiring, import_plans, import_tests, smoke_validation. overall_complete is server-com… |
No output schema declared.
No examples provided.
update-scan-progress Update Scan Progress ~86
Update a scan's status. status must be one of: QUEUED, IN_PROGRESS, COMPLETED, EXCEPTION. Call IN_PROGRESS when starting. Each scan is a single checker type: the category playbook sets COMPLETED after a successful report-*-findings (or EXCEPTION on hard failure).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| status | string | yes | – |
No output schema declared.
No examples provided.
update-test-scenario Update Test Scenario ~180
Sync a test scenario markdown file to the platform after local edits. Requires frontmatter id: TS-<n> and story: US-<n>. Missing either returns an error telling you to call create-test-scenario first. Parses frontmatter and updates linking if story changes. Optional agentTraceability records UPDATED Activity inline.
| Name | Type | Req | Description |
|---|---|---|---|
| actorType | string | – | – |
| agentModel | string | – | – |
| agentTraceability | object | – | – |
| branchName | string | – | – |
| cliVersion | string | – | – |
| content | string | yes | – |
| gitSha | string | – | – |
| policyFile | string | – | – |
| policyVersion | string | – | – |
| skillVersion | string | – | – |
| userId | string | – | – |
| workflowExecutionId | string | – | – |
| workflowId | string | – | – |
No output schema declared.
No examples provided.
update-user-story Update User Story ~183
Sync a user story markdown file to the platform after local edits. Requires frontmatter id: US-<n> (platform-issued). Missing id returns an error telling you to call create-user-story first. Parses frontmatter (id, title, priority) and updates the linked support file and entity. Optional agentTraceability records UPDATED Activity inline.
| Name | Type | Req | Description |
|---|---|---|---|
| actorType | string | – | – |
| agentModel | string | – | – |
| agentTraceability | object | – | – |
| branchName | string | – | – |
| cliVersion | string | – | – |
| content | string | yes | – |
| gitSha | string | – | – |
| policyFile | string | – | – |
| policyVersion | string | – | – |
| skillVersion | string | – | – |
| userId | string | – | – |
| workflowExecutionId | string | – | – |
| workflowId | string | – | – |
No output schema declared.
No examples provided.
update-workflow-execution-assignees Update Workflow Execution Assignees ~209
Change the assignee and/or CC list of a workflow execution. The caller (OAuth user, or the bot's owner with --bot) must be the current assignee or an org admin (admin override needs OAuth, not --bot); anyone on the team may assign an unassigned execution, and a CC'd user may remove themselves. 409 means someone else changed it: re-read with get-workflow-execution and retry. Assignee / CC accept team member user ids or emails. New assignees and CC'd users get a workflow-execution-assigned bot event plus email/Slack per their notification settings. Only call after the user explicitly approved the change. Returns the updated execution.
| Name | Type | Req | Description |
|---|---|---|---|
| addCc | array | – | User ids or emails to CC. |
| assignee | string | – | New assignee: team member user id or email. |
| removeCc | array | – | User ids to remove from CC. |
| workflowExecutionId | string | yes | – |
No output schema declared.
No examples provided.
upload-attachment Upload Attachment ~76
Upload a file (e.g. agent screenshot evidence) to explore-snaps and return a stable view URL. Pass --file <path>; optional --filename and --content-type. Response includes viewUrl to paste in chat.
| Name | Type | Req | Description |
|---|---|---|---|
| contentType | string | – | – |
| file | string | yes | – |
| filename | string | – | – |
No output schema declared.
No examples provided.
upsert-plans-support-file Upsert Plans Support File ~141
Create or update any file under the mapped plans root on the platform by relative path (no git commit/push required). Primary use: upload workflow execution plans at knowledge/workflow_plans/<workflow-id>/<workflow_execution_id>.plan.md after the Plan phase. filePath is relative to the plans mapped root (leading plans/ is stripped). Under workflow_plans/, filenames are coerced to *.plan.md and stored as WORKFLOW_EXECUTION_PLAN. Response includes supportFileId, filePath (canonical), filetype, created. Blocking step before Execute for cloud agents.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| filePath | string | yes | – |
No output schema declared.
No examples provided.
upsert-policy Upsert Policy ~80
Create or update a workflow policy file on the platform (plans/knowledge/policies/*.policy.md). policyFileName is coerced to *.policy.md (same as get-policy). Prefer after writing the file locally so the policy is available immediately (git sync also works later).
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| policyFileName | string | yes | – |
No output schema declared.
No examples provided.
upsert-screen-states Upsert Screen States ~61
Merge screen names and state strings into the project's relational atlas (idempotent upsert). Body uses camelCase screenStates: [{ screen, states: string[] }, ...] per UpsertScreenStatesRequest.
| Name | Type | Req | Description |
|---|---|---|---|
| screenStates | array | yes | – |
No output schema declared.
No examples provided.
How do I install the TestChimp MCP server?
TestChimp runs locally as an npm package, launched with npx -y @testchimp/cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @testchimp/cli
claude mcp add io-testchimp-qa -- npx -y @testchimp/cli
What is the TestChimp MCP server?
TestChimp is an MCP server listed in the public MCP registry as io.testchimp/qa. QA platform for agents: coverage signals, in-repo test plans, verified tests and release governance. This page covers its npm package (@testchimp/cli).
Is the TestChimp MCP server safe to use?
TestChimp scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the TestChimp MCP server expose?
TestChimp exposes 98 tools: get-org-capabilities, get-requirement-coverage, get-execution-history, get-suite-execution-stats, fetch-execution-report, and 93 more. Their descriptions and schemas cost roughly 11,016 tokens of context every time the server is loaded.
Is the TestChimp MCP server still maintained?
TestChimp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the TestChimp MCP server under?
TestChimp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.