Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Autonomous Tool Factory

REMOTE · AGENCY-BACKEND-BBDK.ONRENDER.COM · SCANNED SEP 20

Autonomous factory that finds real developer pain points and builds small paid AI tools to fix them.

+2 this week 73 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1187 tokens (~59/item across 20 items; 20 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 21 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
Install

How do I install the Autonomous Tool Factory MCP server?

Autonomous Tool Factory is a hosted endpoint at https://agency-backend-bbdk.onrender.com/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · agency-backend-bbdk.onrender.com

# add to Claude Code
claude mcp add --transport http lorenestinfinite-maker-tool-factory 'https://agency-backend-bbdk.onrender.com/mcp/'
// .cursor/mcp.json
{
  "mcpServers": {
    "lorenestinfinite-maker-tool-factory": {
      "url": "https://agency-backend-bbdk.onrender.com/mcp/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "lorenestinfinite-maker-tool-factory": {
      "type": "http",
      "url": "https://agency-backend-bbdk.onrender.com/mcp/"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.lorenestinfinite-maker-tool-factory]
url = "https://agency-backend-bbdk.onrender.com/mcp/"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lorenestinfinite-maker-tool-factory": {
      "type": "remote",
      "url": "https://agency-backend-bbdk.onrender.com/mcp/",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add lorenestinfinite-maker-tool-factory --url 'https://agency-backend-bbdk.onrender.com/mcp/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  lorenestinfinite-maker-tool-factory:
    url: "https://agency-backend-bbdk.onrender.com/mcp/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "lorenestinfinite-maker-tool-factory": {
      "Transport": "http",
      "Url": "https://agency-backend-bbdk.onrender.com/mcp/"
    }
  }
}
# add to Vellum
assistant mcp add lorenestinfinite-maker-tool-factory -t streamable-http -u 'https://agency-backend-bbdk.onrender.com/mcp/'
// mcp.json
{
  "mcpServers": {
    "lorenestinfinite-maker-tool-factory": {
      "type": "http",
      "url": "https://agency-backend-bbdk.onrender.com/mcp/"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 17 Sept 26 0
    • Stability: 0.97 → pass security
  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 5 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 20 Sept 2026 · Probed https://agency-backend-bbdk.onrender.com/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=onrender.com CN=WE1,O=Google Trust Services,C=US 24 Jul 2026 22 Oct 2026 ECDSA 256 ECDSA-SHA256 756bcb97dcf1455f0ebf70e5dbe07256
SANs: onrender.com, *.onrender.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agency-backend-bbdk.onrender.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
onrender.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agency-backend-bbdk.onrender.com/mcp/ Verified 200
http (plaintext) http://agency-backend-bbdk.onrender.com/mcp/ HTTPS enforced 301 https://agency-backend-bbdk.onrender.com/mcp/
MCP tools · 20 exposed · ~1,107 tokens

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 →

Tool Tokens
add-license-information-to-codebase ~79

Automatically prepend license text to multiple codebase files to ensure legal compliance across your project. This tool takes a license string and a list of file paths/contents, returning the updated files with a properly formatted blank line separating the license from your original code. (reference price: $0.0000 per call)

NameTypeReqDescription
payload

Structured output declared, but exposes no named fields.

No examples provided.

add-subscriptions-tab-in-user-settings ~50

Add a Subscriptions tab in user settings, a repetitive task that could be automated with a tool. (reference price: $0.0100 per call)

NameTypeReqDescription
payload

Structured output declared, but exposes no named fields.

No examples provided.

ai-generated-code-debugging-overhead ~77

45% of developers report debugging AI-generated code is more time-consuming than debugging their own; 66% cite 'AI solutions that are almost right, but not quite' as their single biggest frustration (2025 SO Developer Survey). (reference price: $0.0100 per call)

NameTypeReqDescription
payload

Structured output declared, but exposes no named fields.

No examples provided.

auto-handoff-when-context-utilization-exceeds-threshold ~55

Auto-handoff when context utilization exceeds threshold, a repetitive task that could be automated with a tool. (reference price: $0.0100 per call)

NameTypeReqDescription
payload

Structured output declared, but exposes no named fields.

No examples provided.

automate-min-sdk-version-bump ~58

Automate MIN_SDK_VERSION bump via release pipeline + AI-based SDK-breaking-change detection, a repetitive task that could be automated with a tool. (reference price: $0.0100 per call)

NameTypeReqDescription
payload

Structured output declared, but exposes no named fields.

No examples provided.

check_tool_health ~42

Mode 3 ("The Manager"): deprecate (delete code + registry entry) any published tool that has earned zero payments after the deprecation window.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

codebase-learning-friction ~59

Learning a codebase generates disproportionate frustration relative to the time spent on it, per the 2025 SO Developer Survey -- largely attributed to inadequate documentation. (reference price: $0.0100 per call)

NameTypeReqDescription
payload

Structured output declared, but exposes no named fields.

No examples provided.

deployment-process-friction ~70

Optimize your CI/CD workflows and identify automation opportunities. This tool analyzes deployment steps, manual tasks, and tool versions to provide actionable suggestions for consolidation, scripting, and resilience, estimating potential time savings for your deployment process. (reference price: $0.0100 per call)

NameTypeReqDescription
payload

Structured output declared, but exposes no named fields.

No examples provided.

develop_tools ~59

Mode 2 ("The Brain"): generate, subprocess-smoke-test, and publish a tool for every queued backlog item. Publishing writes to data/tool_registry.json, which both the HTTP dispatcher and this MCP server's dynamic tool registration read from.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

documentation-creation-toil ~73

Instantly transform Python source code into clean, structured Markdown documentation. This tool parses your code's Abstract Syntax Tree (AST) to automatically extract module docstrings, class definitions, methods, and function signatures into a readable format. (reference price: $0.0000 per call)

NameTypeReqDescription
payload

Structured output declared, but exposes no named fields.

No examples provided.

help-setting-up-an-instance ~49

Request for assistance with setting up a new instance, a repetitive task that could be automated with a tool. (reference price: $0.0100 per call)

NameTypeReqDescription
payload

Structured output declared, but exposes no named fields.

No examples provided.

list_backlog ~22

List every tracked pain point and its current backlog/mention status.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes

No examples provided.

list_published_tools ~23

List every published tool with its price and live ping/payment stats.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes

No examples provided.

offline-session-sync ~62

Ensure zero data loss for user sessions by caching events locally when offline. This tool manages a persistent JSON-based queue that records events and allows for seamless bulk synchronization once connectivity is restored. (reference price: $0.0000 per call)

NameTypeReqDescription
payload

Structured output declared, but exposes no named fields.

No examples provided.

persist-appearance-options-to-localstorage ~56

Persist UI appearance options (nodes, edges, labels) to localStorage, a repetitive task that could be automated with a tool. (reference price: $0.0100 per call)

NameTypeReqDescription
payload

Structured output declared, but exposes no named fields.

No examples provided.

request-help-with-media-search ~46

Request for help with media search, a repetitive task that could be automated with a tool. (reference price: $0.0100 per call)

NameTypeReqDescription
payload

Structured output declared, but exposes no named fields.

No examples provided.

research_pain_points ~56

Mode 1 ("The Eyes"): scan GitHub Issues, targeted Reddit subs, and the public MCP registry for recurring pain points not already solved by an existing tool; queue anything past the daily mention threshold for development.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

run_factory_cycle ~47

Run the full LangGraph-orchestrated pipeline in one call: research -> develop -> health_check. This is graph.py's only production entry point -- it is not exposed over HTTP.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

student-gamification-xp-levels-streak ~57

Student gamification features (XP, Levels & Streaks), a repetitive task that could be automated with a tool. (reference price: $0.0100 per call)

NameTypeReqDescription
payload

Structured output declared, but exposes no named fields.

No examples provided.

support-ticket-system-friction ~67

Automatically organize your support tickets by priority and status to streamline your workflow. This tool generates a status summary, sorts tickets by importance, and identifies high-priority open tickets that need an assignee. (reference price: $0.0000 per call)

NameTypeReqDescription
payload

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the Autonomous Tool Factory MCP server?

Autonomous Tool Factory is an MCP server listed in the public MCP registry as io.github.lorenestinfinite-maker/tool-factory. Autonomous factory that finds real developer pain points and builds small paid AI tools to fix them. This page covers its hosted endpoint (https://agency-backend-bbdk.onrender.com/mcp/).

Is the Autonomous Tool Factory MCP server safe to use?

Autonomous Tool Factory scores 73 out of 100 on VerifyMCP. 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 Autonomous Tool Factory MCP server expose?

Autonomous Tool Factory exposes 20 tools: research_pain_points, develop_tools, check_tool_health, run_factory_cycle, list_backlog, and 15 more. Their descriptions and schemas cost roughly 1,107 tokens of context every time the server is loaded.

Does the Autonomous Tool Factory MCP server require authentication?

No. We connected to Autonomous Tool Factory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Autonomous Tool Factory MCP server still maintained?

Autonomous Tool Factory is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.