Other · Local MCP server
Toolfactory
Build an agent tool once; ship it as Agent Skills, MCP servers, Agent Plugins / Claude / Codex.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.GoatInAHat/toolfactory- Version
- 0.4.3
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm, OCI image (Docker)
- Published
- 2026-10-03
- Updated
- 2026-10-03
- Publisher
- GoatInAHat (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/GoatInAHat) · how
- Website
- github.com/GoatInAHat/toolfactory
- Repository
- github.com/GoatInAHat/toolfactory
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | toolfactory | 0.4.3 | stdio |
| OCI image (Docker) | ghcr.io/goatinahat/toolfactory:0.4.3 | - | stdio |
How to connect Toolfactory
Toolfactory runs locally from a Node.js package published to the npm registry: toolfactory version 0.4.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y toolfactory@0.4.3.
Toolfactory runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/goatinahat/toolfactory:0.4.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm ghcr.io/goatinahat/toolfactory:0.4.3.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"toolfactory": {
"command": "npx",
"args": [
"-y",
"toolfactory@0.4.3"
]
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| ToolAPIFree public MCP for AI agents - 193 tools, 44 workflows. No API key. | Remote · SSE, HTTPLive check: ✓ handshake |
| ToolBudget Router MCPPaid remote MCP for context-budget routing, schema cost estimates, usage audits, and readiness. | Remote · HTTPLive check: ✗ no handshake |
| Toolcairn MCPMCP server for tool discovery: find, compare, and verify tools across 35+ registries. | Local · stdio |
| Toolchain Lens MCPLocal explanation of reproducibility signals and toolchain contradictions without exact versions... | Local · stdio |
| ToolforestHosted MCP server with managed OAuth for 15+ toolkits: Google Workspace, Fitbit, Oura, Kalshi, etc. | Remote · HTTPLive check: sign-in required |
| Toolkit MCP ServerGenerate IDs, QR codes, and hashes, encode values, geolocate IPs, plus gated host diagnostics. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| ToolpinCheck whether an MCP server answers, what its tools claim, and whether that claim has changed. | Remote · HTTPLive check: ✓ handshake |
| ToolRouterThe OpenRouter for tools. One MCP connection gives any AI agent 254 hosted tools, pay per call. | Remote · HTTPLive check: ✓ handshake |