# toolfactory

Build an agent tool once; ship it as Agent Skills, MCP servers, Agent Plugins / Claude / Codex / Cursor bundles, OpenClaw and Hermes plugins, CLIs, and packages, with the tests and releases to match.

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.3.1
- **Author:** io.github.GoatInAHat
- **License:** MIT
- **npm:** toolfactory
- **Source:** https://github.com/GoatInAHat/toolfactory
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 1 day

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-17T13:24:11.656Z
- **Version scanned:** 0.3.1
- **CVEs:** none found by OSV at scan time

## Tools

28 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `echo` — key
- `scrape`
- `summarize`
- `login`
- `screenshot` — Capture the current page.
- `notify` — Post a message into the live conversation.
- `browse` — Service region.
- `region` — Service region.
- `shoot` — Say hello
- `web` — Open the generated operations page.
- `adopt` — Stop regenerating one file; it becomes the author's (recorded as manual in the lock).
- `bootstrap-repo` — Prepare the GitHub repository from the local .env: the `live-tests` environment with its required reviewers and the sensitive config keys inside it, the release
- `build` — Generate every selected surface in-tree from the identity file and the operation snapshot, and refresh the lock.
- `check` — Fail if the operation snapshot or any generated file drifted from the code (the CI drift gate).
- `coverage` — The operation × surface verdict matrix: native, bridged, degraded, or excluded, with reasons.
- `doctor` — Report which upstream CLIs this machine can delegate to (git, gh, npm, uv, claude, openclaw, clawhub, hermes, uvx, agentskills, MCP Inspector, docker).
- `eject` — Adopt every file a surface owns, so the author takes it over entirely.
- `gate` — Run the gate here, in order: build, the drift check, every selected surface's upstream validator, the author's checks and tests, and the credential-free host en
- `init` — Create a new tool: dev.toolfactory/tool.json, the authored identity file, the kernel scaffold for the chosen language, and the first build of every selected sur
- `introspect` — Spawn the kernel MCP server, list its tools, and snapshot them to dev.toolfactory/ops.json.
- `package` — Build every release asset into dist/release/ — npm tarball, Python distributions, OpenClaw plugin tarball, plugin bundle zip, web build, coverage — by the same 
- `review-prompt` — Evaluate a prompt draft against the codex-prompt-standard rubric: anatomy sections, convention checks, and concrete directives. Draft, run this, fix what it fla
- `secrets-usage` — Every credential this project's surfaces need — the tool's own sensitive config keys and the release registries' tokens — with where each one is set, whether it
- `unadopt` — Return an adopted file to toolfactory and regenerate it.
- `unpublish` — Retract what a deselected surface used to publish. Git is the ledger: the previous tag's dev.toolfactory/tool.json says what was selected then, and every regist
- `validate` — Run each selected surface's own upstream validator (agentskills, claude plugin validate, MCP Inspector, openclaw, hermes, npm pack, uv build).
- `hello` — Say hello
- `native`

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"toolfactory\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"toolfactory\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 12, ceiling 30 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- 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/toolfactory
- Install plan: https://forgeregistry.com/api/v1/packages/toolfactory/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/toolfactory
- HTML page: https://forgeregistry.com/registry/toolfactory
- 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.