Developer · Remote MCP server
Autonomous Tool Factory
Autonomous factory that finds real developer pain points and builds small paid AI tools to fix them.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.lorenestinfinite-maker/tool-factory- Version
- 0.1.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-08-18
- Updated
- 2026-08-18
- Publisher
- lorenestinfinite-maker (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/lorenestinfinite-maker) · how
- Website
- agency-backend-bbdk.onrender.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://agency-backend-bbdk.onrender.com/mcp/ | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 404)
- Handshake
- HTTP 404
- Checked on
- 2026-10-05
How to connect Autonomous Tool Factory
Autonomous Tool Factory is a remote MCP server: there is nothing to install. Its endpoint is https://agency-backend-bbdk.onrender.com/mcp/, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. 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 developer servers
| Server | Runs |
|---|---|
| AuthshoreAuth infrastructure for coding agents. User pools, secrets vault, token management. As easy as git. | Remote & Local · SSE, stdioLive check: ✓ SSE reachable |
| Autobrowserapproval MCPA paid remote MCP for AI agent browser approval MCP, built to return verdicts, receipts, usage logs,. | Remote · HTTPLive check: ✗ no handshake |
| Automatised PipelineCodebase intelligence MCP server - index any repo into a property graph; 26 tools for agents. | Local · stdio |
| Autonoma Agent ServicesPaid agent trust checks, receipt verification, research, data work, and monitoring. | Remote · HTTPLive check: ✓ handshake |
| Autorenew Signup LintSixteen statutory checks on the signup page AB 2863 rewrote, in your editor and in the browser. | Local · stdio |
| AuvikMCP server for the Auvik network monitoring API - devices, alerts, statistics, billing. | Local · stdio |
| AuvikMCP server for the Auvik network monitoring API - devices, alerts, statistics, billing. | Local · stdio |
| AvalancheAct on Avalanche from your agent: scaffold a dapp, deploy a contract, mint, and read chain state. | Local · stdio |