five46
NPM · FIVE46 · SCANNED AUG 7
BYOK, fully local AI agent that tests your app/API and writes a real Playwright spec on success.
Available components
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 →
Supply Chain Security88
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 126 of 130 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 126 of 130 dependencies we could resolve, so this covers what we could see, not the whole tree. 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 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability52
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 815 tokens (~407/item across 2 items; 2 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · five46
claude mcp add sekharsdet-five46 -- npx -y five46
codex mcp add sekharsdet-five46 -- npx -y five46
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sekharsdet-five46": {
"type": "local",
"command": [
"npx",
"-y",
"five46"
],
"enabled": true
}
}
} openclaw mcp add sekharsdet-five46 --command npx --arg -y --arg five46
mcp_servers:
sekharsdet-five46:
command: "npx"
args: ["-y", "five46"] {
"mcpServers": {
"sekharsdet-five46": {
"command": "npx",
"args": [
"-y",
"five46"
]
}
}
} 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.
- 5 Aug 26 +25
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 100 functional
- 4 Aug 26 36
First indexed and scored.
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 7 Aug 2026 · Analysed npm/[email protected]
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 126 packages
| Packages resolved | 126 |
|---|---|
| Deprecated | 119 |
| Stale | 30 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
five46_api ~375
Drive real HTTP requests toward a stated goal, one request/assertion at a time, using your own configured LLM key (BYOK). Writes a real, standalone node:test script on success. Read-only for this server (GET/HEAD/OPTIONS only) — set FIVE46_MCP_ALLOW_WRITES=1 in the server environment to unlock POST/PUT/PATCH, FIVE46_MCP_ALLOW_DELETES=1 to separately unlock DELETE. Neither is ever settable via a tool call argument. Requests are restricted to the target base URL's own origin — no additional host allowlist is available via this tool. Discloses: request/response data, including response bodies (which may contain a live session token or other secret), is sent to your configured LLM provider on every step. On a real assertion failure, one additional LLM call analyzes the failure for a root-cause hypothesis — built only from information already visible to the agent during the run, always on for this tool, and included in the returned report as a hypothesis, not a confirmed diagnosis.
| Name | Type | Req | Description |
|---|---|---|---|
| baseUrl | string | yes | The live http(s) base URL to test |
| goal | string | – | What the agent should accomplish — provide exactly one of `goal`/`story`. A vague goal would burn real BYOK cost on an unfocused run. |
| maxSteps | integer | – | Step budget (default 15, hard-capped at 50 regardless of what is passed) |
| story | string | – | A raw, possibly multi-scenario user story/acceptance-criteria text to split into independent goals and run with bounded concurrency (see `concurrency` context, set via FIVE46_MCP_CONCURRENCY on the s… |
| Name | Type | Req | Description |
|---|---|---|---|
| acceptanceCriteria | array | – | Present only for a `story` call — one entry per split acceptance criterion, in the order they were run. |
| outcome | string | – | Present only for a plain `goal` call (never a `story` call — see acceptanceCriteria instead). |
| passed | boolean | yes | Whether this call fully succeeded — for a plain goal, outcome === "goal-reached"; for a story, every acceptance criterion reached goal-reached. |
| specPath | string | – | Absolute path to the generated spec file — present only for a plain `goal` call. |
No examples provided.
five46_test ~440
Drive a real local Playwright browser toward a stated goal, one action at a time, using your own configured LLM key (BYOK). Writes a real, standalone, re-runnable Playwright spec on success. Discloses: the page's visible text/labels/values are sent to your configured LLM provider on every step. Clicking an element that looks like it deletes/deactivates/closes an account or permanently erases data (e.g. "Delete Account") is blocked for this server — set FIVE46_MCP_ALLOW_DELETES=1 in the server environment to unlock it. Never settable via a tool call argument. This is a best-effort heuristic on the clicked element's visible text, not a guarantee. On a real assertion failure (a genuine finding about the app, not a tooling issue), one additional LLM call analyzes the failure for a root-cause hypothesis — built only from information already visible to the agent during the run (never a new disclosure), always on for this tool, and included in the returned report as a hypothesis, not a confirmed diagnosis.
| Name | Type | Req | Description |
|---|---|---|---|
| goal | string | – | What the agent should accomplish — provide exactly one of `goal`/`story`. A vague goal would burn real BYOK cost on an unfocused run. |
| headed | boolean | – | Watch it drive a real visible browser instead of headless (default false) |
| maxSteps | integer | – | Step budget (default 15, hard-capped at 50 regardless of what is passed) |
| storageStatePath | string | – | Relative path (under the configured project root) to a session file previously captured by `five46 login` — starts the browser already authenticated |
| story | string | – | A raw, possibly multi-scenario user story/acceptance-criteria text to split into independent goals and run with bounded concurrency (see `concurrency` context, set via FIVE46_MCP_CONCURRENCY on the s… |
| url | string | yes | The live http(s) or file:// URL to test |
| Name | Type | Req | Description |
|---|---|---|---|
| acceptanceCriteria | array | – | Present only for a `story` call — one entry per split acceptance criterion, in the order they were run. |
| outcome | string | – | Present only for a plain `goal` call (never a `story` call — see acceptanceCriteria instead). |
| passed | boolean | yes | Whether this call fully succeeded — for a plain goal, outcome === "goal-reached"; for a story, every acceptance criterion reached goal-reached. |
| specPath | string | – | Absolute path to the generated spec file — present only for a plain `goal` call. |
No examples provided.