Submit Forge Cascade without rewriting the listing.

Current directory targets

Paste-ready descriptions

Short: Forge Cascade gives teams source-backed private AI memory for agents, research, compliance, diligence, and enterprise decision workflows.

Medium: Forge Cascade helps organizations preserve institutional context, private corpora, evidence, approvals, and retrieval-ready decision memory across AI workflows. Teams can start with a $9/month AI Memory Monitor, a $99 Context Audit, or move into paid pilots and enterprise deployment.

Pricing model: Paid. Fast-start buyers should see the $99 Context Audit, $299/month Starter Workspace, and $3,000 Private RAG/Paid Pilot before lower-ticket recurring entries; AI Memory Monitor / Observer Brief is the $9/month fallback after those paths or enterprise checkout are not a fit.

Primary checkout: https://sunflash12.github.io/ForgeV3/buy.html

Submission status

AIToolsIndex Observer Brief: submitted May 31, 2026 through the public no-login /api/submit/enqueue-tool-submission endpoint with the clean Observer Brief URL after the UTM URL was rejected by URL validation. Response: HTTP 200, success true, key ToolSubmission-1780190222522-d00dceb9-b60d-44ed-b207-65068310eaba. Follow-up GET /api/submit/get-tool-submission returned HTTP 200, success true, and status success.

The Toolify Observer Brief: submitted May 31, 2026 through the public WordPress REST endpoint /wp-json/toolify/v1/submit with Toolify campaign tracking, Business category, paid pricing, and $9/month Observer Brief positioning. Response: HTTP 200, success true, message "Tool submitted successfully."

FindAIDir Observer Brief: submitted May 31, 2026 through the public no-login /api/tool-submissions endpoint with FindAIDir campaign tracking, Productivity category, and paid recurring Observer Brief positioning. Response: HTTP 201, ok true, accepted true.

HookFlow Observer Brief: submitted May 31, 2026 through the public no-login /api/submissions endpoint with the clean Observer Brief URL after the UTM URL was rejected by URL validation, Search & RAG category, and paid recurring brief positioning. Response: HTTP 200, redirect https://www.hookflow.ai/submit/success, submission id d31e9c21-ac7a-410c-a2d1-d7662e15f022.

NoSignupTools Observer Brief: submitted May 31, 2026 through the official same-origin /api/submit endpoint with NoSignupTools campaign tracking, hosted Forge preview asset, Business category, and $9/month recurring checkout positioning. Response: HTTP 200, success true. Public listing visibility is not proven yet, so treat this as accepted/in-review proof.

Cocoon AI Tools Directory Observer Brief: submitted May 31, 2026 through the current Formspree endpoint with Cocoon campaign tracking, AI Assistants category, Paid pricing, public contact email, and $9/month recurring checkout positioning. Response: HTTP 200, ok true, next /thanks. Public listing visibility is not proven yet, so treat this as accepted/in-review proof.

The Next AI Observer Brief: submitted May 31, 2026 through the public Google Apps Script endpoint with Productivity category, Paid pricing, free listing plan, AI memory/context-risk tags, and $9/month Observer Brief positioning. Response: HTTP 200, success true. Public listing visibility is not proven yet, so treat this as accepted/in-review proof.

AI Toolkit Directory Observer Brief: submitted May 31, 2026 through the official same-origin /api/submit endpoint with Memory category, Monitoring subcategory, paid checkout positioning, and public contact email. Response: HTTP 200, ok true, submissionId 23, approved false, and admin review message "Submission received. An admin will review it shortly." Public listing visibility is not proven yet, so treat this as accepted/in-review proof.

FreeAIToolsAyoob Observer Brief: submitted May 31, 2026 through the public Formspree-backed free listing form with Business Tools category, global availability, Paid pricing, and recurring checkout positioning. Response: HTTP 200, ok true, next /thanks. Public listing visibility is not proven yet, so treat this as accepted/in-review proof.

HyzenPro Observer Brief: submitted May 31, 2026 through /api/tool-submissions/ with the clean Observer Brief URL after the UTM URL was rejected by URL validation, ai-general-tools category, paid pricing, and recurring brief features. Response: HTTP 201, ok true, id 6a1b903d32d4ec742a8dcf38, mailStatus not_configured, and missing SMTP_HOST, SMTP_PORT, SMTP_USER, and SMTP_PASS. Treat this as saved-for-review proof, not reviewer email proof.

AI NavHub Observer Brief: submitted May 31, 2026 through /api/submit with the tracked Observer Brief URL and public contact email. Initial unauthenticated POST returned HTTP 401; authorized retry returned HTTP 200 with message Success. Public listing visibility is not proven yet, so treat this as accepted/in-review proof.

BestToolFinder Observer Brief: submitted May 31, 2026 through the public Formspree-backed intake endpoint with BestToolFinder campaign tracking, public contact email, and recurring checkout positioning. Response: HTTP 200, ok true, next /thanks. Public listing visibility is not proven yet, so treat this as accepted/in-review proof.

OpenAgents.pro Observer Brief: submitted May 31, 2026 through the public Formspree-backed AI agent/tool form with Research category, AI Agent type, AI memory/context-risk tags, and tracked recurring checkout URL. Response: HTTP 200, ok true, next /thanks. Public listing visibility is not proven yet, so treat this as accepted/in-review proof.

AIDealer Observer Brief: submitted May 31, 2026 through the public Google Apps Script-backed agent submission form with Research & Monitoring category, Ready-made listing type, $9/month pricing, sample brief demo link, and tracked recurring checkout URL. Response: HTTP 200 OK from the official script endpoint. Public listing visibility is not proven yet, so treat this as accepted/in-review proof.

Master AI Finder Observer Brief: submitted May 31, 2026 through the public no-login registeryourwebsite.php form with Productivity & Workflow / Task Automation category, paid pricing, and tracked recurring checkout URL. Response: HTTP 200 with Website added successfully confirmation. Public listing/search visibility is not proven yet, so treat this as accepted/in-review proof.

BestToolFinder Enterprise Deployment: submitted May 31, 2026 through the public Formspree-backed intake endpoint with BestToolFinder campaign tracking, public contact email, and high-ticket enterprise checkout positioning. Response: HTTP 200, ok true, next /thanks. Public listing visibility is not proven yet, so treat this as accepted/in-review proof.

OpenAgents.pro Enterprise Deployment: submitted May 31, 2026 through the public Formspree-backed AI agent/tool form with Business category, AI Agent type, enterprise AI/private RAG/MCP/procurement tags, and tracked enterprise checkout URL. Response: HTTP 200, ok true, next /thanks. Public listing visibility is not proven yet, so treat this as accepted/in-review proof.

AIDealer Enterprise Deployment: submitted May 31, 2026 through the public Google Apps Script-backed agent submission form with Operations category, Custom / Quote listing type, buyer-intro demo link, tracked enterprise checkout URL, and $120k annual / $25k retainer / $25k deposit / $5k rush pilot pricing. Response: HTTP 200 OK from the official script endpoint. Public listing visibility is not proven yet, so treat this as accepted/in-review proof.

Master AI Finder Enterprise Deployment: submitted May 31, 2026 through the public no-login registeryourwebsite.php form with Marketing & Business category, paid pricing, and tracked enterprise checkout URL. Response: HTTP 200 with exact Website added successfully confirmation. Public listing/search visibility is not proven yet, so treat this as accepted/in-review proof.

Cocoon AI Tools Directory Enterprise Deployment: submitted May 31, 2026 through the current Formspree endpoint with Cocoon campaign tracking, AI Assistants category, Paid pricing, public contact email, and high-ticket enterprise checkout positioning. Response: HTTP 200, ok true, next /thanks. Public listing visibility is not proven yet, so treat this as accepted/in-review proof.

The Next AI Enterprise Deployment: submitted May 31, 2026 through the public Google Apps Script endpoint with Productivity category, Paid pricing, free listing plan, enterprise AI/private RAG tags, and tracked enterprise checkout URL. Response: HTTP 200, success true. Public listing visibility is not proven yet, so treat this as accepted/in-review proof.

AI Toolkit Directory Enterprise Deployment: submitted May 31, 2026 through the official same-origin /api/submit endpoint with Memory category, Enterprise AI subcategory, paid checkout positioning, and public contact email. Response: HTTP 200, ok true, submissionId 24, approved false, and admin review message "Submission received. An admin will review it shortly." Public listing visibility is not proven yet, so treat this as accepted/in-review proof.

FreeAIToolsAyoob Enterprise Deployment: submitted May 31, 2026 through the public Formspree-backed free listing form with Business Tools category, global availability, Paid pricing, and tracked enterprise checkout URL. Response: HTTP 200, ok true, next /thanks. Public listing visibility is not proven yet, so treat this as accepted/in-review proof.

HyzenPro Enterprise Deployment: submitted May 31, 2026 through /api/tool-submissions/ with the clean enterprise URL, ai-general-tools category, paid pricing, and private AI memory deployment features. Response: HTTP 201, ok true, id 6a1b9884fdcfaf4bcebdf687, mailStatus not_configured, and missing SMTP_HOST, SMTP_PORT, SMTP_USER, and SMTP_PASS. Treat this as saved-for-review proof, not reviewer email proof.

AI NavHub Enterprise Deployment: submitted May 31, 2026 through /api/submit with the tracked enterprise checkout URL and public contact email. Response: HTTP 200 with message Success. Public listing visibility is not proven yet, so treat this as accepted/in-review proof.

Not Human Search enterprise deployment recrawl: submitted the updated GitHub Pages directory submission pack, directory-listing JSON, llms.txt, and canonical enterprise page on May 31, 2026 after the high-ticket enterprise deployment submissions were recorded. All four canonical POSTs returned HTTP 201 with message "submitted for crawling"; the four source-tracked enterprise URLs returned HTTP 429 Too Many Requests.

AISuperHub, LookForAI, and AI Kaptan Observer Brief retries: attempted May 31, 2026 but not counted as accepted Observer Brief submissions. AISuperHub returned HTTP 400, latest body {"message":"Missing required fields"}; LookForAI returned HTTP 422; AI Kaptan returned HTTP 404 for the attempted submit endpoint.

IndexNow Observer Brief proof refresh: earlier May 31, 2026 Observer Brief proof refresh returned HTTP 202 Accepted. After the BestToolFinder, OpenAgents.pro, AIDealer, and Master AI Finder batch, the IndexNow key file 1b60a6d39a7f4c1f9fb1e70a2ad5af7d.txt was published and verified at HTTP 200 with the correct key text, but the canonical proof retry still returned HTTP 403 Forbidden.

Not Human Search Observer Brief proof recrawl: submitted the updated GitHub Pages directory submission pack, directory-listing JSON, llms.txt, and Observer Brief page on May 31, 2026 after the expanded Observer Brief directory proof went live. All four POSTs returned HTTP 201 with message "submitted for crawling."

AIToolsIndex: submitted May 28, 2026. Public API response: HTTP 200, success true, status success. The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the public no-login /api/submit/enqueue-tool-submission endpoint with the tracked security URL; response was HTTP 200, success true, key ToolSubmission-1780029693307-bbc66cb5-c661-4ecf-b7bc-da02a61cd183, status pending. Follow-up GET /api/submit/get-tool-submission returned HTTP 200, success true, and status success.

The Toolify: submitted May 28, 2026. Public API response: HTTP 200, success true, "Tool submitted successfully." The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the public WordPress REST endpoint /wp-json/toolify/v1/submit with the tracked security URL, Security category, and paid pricing; response was HTTP 200, success true, message "Tool submitted successfully."

FindAIDir: submitted May 28, 2026. Public API response: HTTP 201, ok true, accepted true. The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the same public no-login /api/tool-submissions endpoint with the tracked security URL, AI Security category, and prompt-injection/RAG/MCP security tags; response was HTTP 201, ok true, accepted true.

Toolly: submitted May 28, 2026. Public Google Apps Script response: HTTP 200, result success, row 51. The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the same public Google Apps Script endpoint with the tracked security URL; response was HTTP 200, result success, row 65.

HookFlow: submitted May 28, 2026. Public API response: HTTP 200, redirect https://www.hookflow.ai/submit/success, submission id ce4ad755-6b4b-4297-940c-1ad8f13965bb. A fresh tracked retry with the HookFlow campaign checkout URL returned HTTP 200, the same success redirect, and submission id cdb2918f-66a6-4797-891e-5bf5916e9264. The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the same public no-login /api/submissions endpoint with the tracked security URL, Search & RAG category, and paid security-audit positioning; response was HTTP 200, redirect https://www.hookflow.ai/submit/success, and submission id 9627d50c-d7a3-43d2-a40c-9576f44ae5ea.

AI Toolkit Directory: submitted May 28, 2026 through the official same-origin submission endpoint. Response: HTTP 200, ok true, submission id 9, approved false, message "Submission received. An admin will review it shortly." The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the same endpoint with Security category and the tracked security URL. Response: HTTP 200, ok true, submission id 11, approved false, and the same admin review message. Public listing URL is not live yet, so keep this in submitted/in-review status.

NoSignupTools: submitted May 28, 2026 through the official same-origin submission endpoint as "Forge Memory ROI Calculator," using the free no-login ROI calculator URL with nosignuptools UTM tracking and downstream paid Forge checkout links. The new "Forge AI Memory Risk Scanner" funnel was also submitted after it went live with the tracked scanner URL, hosted Forge preview asset, AI Tools category, and downstream paid audit/pilot/deposit paths. Scanner response: HTTP 200, success true. Public scanner listing URL is not live yet, so keep this in submitted/in-review status. The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the same /api/submit endpoint with the tracked security URL, Security category, no-account checkout positioning, Forge logo, and hosted preview screenshot; response was HTTP 200, success true.

MyFreeAISource: submitted May 28, 2026 through the official WordPress submission form as "Forge Memory ROI Calculator," using the free no-login ROI calculator URL with myfreeaisource UTM tracking and downstream paid Forge checkout links. Response: HTTP 200 and page confirmation "Thanks — your tool was saved as a draft for review." The Forge AI Memory Risk Scanner was submitted May 29, 2026 through the same nonce-backed WordPress form with the tracked scanner URL, Free pricing, AI Research/Data/Knowledge category, and downstream paid Forge checkout paths; response was HTTP 200 with visible "Thanks" and "saved as a draft" confirmation. Public listing URLs are not live yet, so keep both in submitted/in-review status.

nologin.tools: submitted May 28, 2026 through the official same-origin submission endpoint as "Forge Memory ROI Calculator," using the free no-login ROI calculator URL with nologin_tools UTM tracking and downstream paid Forge checkout links. Response: HTTP 201, ok true, slug sunflash12-github-io-forgev3-roi-calculator-html. Live listing verified at https://nologin.tools/tool/sunflash12-github-io-forgev3-roi-calculator-html/; its schema and Visit link point to the tracked Forge ROI calculator URL. The new Forge AI Memory Risk Scanner was also submitted with the tracked scanner URL; response was HTTP 201, ok true, slug sunflash12-github-io-forgev3-context-risk-scanner-html. Live scanner listing verified at https://nologin.tools/tool/sunflash12-github-io-forgev3-context-risk-scanner-html/; its Visit link points to the tracked Forge scanner URL with nologin_tools UTM tracking. The Forge Prompt Injection Security Audit funnel was submitted May 29, 2026 with the tracked security checkout URL; response was HTTP 201, ok true, slug sunflash12-github-io-forgev3-security-html. API detail returned HTTP 200 with Forge metadata, while the public HTML listing route returned HTTP 404 immediately after submission.

nologin.tools Observer Brief: submitted May 31, 2026 with the tracked recurring Observer Brief URL. Response: HTTP 201, ok true, slug sunflash12-github-io-forgev3-observer-brief-html. API detail returned HTTP 200 with Forge metadata, paid/Stripe positioning, price proof, and the tracked URL; the public HTML listing route returned HTTP 404 immediately after submission, so treat this as accepted/API-visible until the listing route publishes.

Cocoon AI Tools Directory: submitted May 28, 2026 through the official free Formspree-backed submission form, using the tracked checkout fallback URL with mycocoon UTM tracking and public contact email. Response: HTTP 200, ok true, next /thanks. The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the current Formspree endpoint with the tracked security URL; response was HTTP 200, ok true, next /thanks. Review window is up to 5 business days, so keep this in submitted/in-review status.

The Next AI: submitted May 28, 2026. Official Google Apps Script endpoint response: HTTP 200, success true, free listing plan. The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the same public endpoint with the tracked security URL, Developer Tools category, Paid pricing, and free listing plan; response was HTTP 200, success true. Public listing URL is not live yet, so keep this in submitted/in-review status.

ToolWise: submitted May 28, 2026. Public API response: HTTP 201, created free listing id 9f5e0c2c-f181-47d2-ac6d-465807f025ba, slug forge-cascade, content_status ai_researched. Live listing verified at https://toolwise.ai/tools/forge-cascade with the tracked checkout URL. The Forge AI Memory Risk Scanner was submitted May 28, 2026 through the same no-login free endpoint; public API response was HTTP 201 with id 4f48895d-67b3-4443-9134-65be0d055699, slug forge-ai-memory-risk-scanner, content_status ai_researched, and live listing https://toolwise.ai/tools/forge-ai-memory-risk-scanner pointing to the tracked scanner URL. The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the same no-login free endpoint; public API response was HTTP 201 with id c031b613-d918-4de5-bfc3-1107cfb574b1, slug forge-prompt-injection-security-audit, content_status ai_researched, pricing_model paid, starting_price 99, and live listing https://toolwise.ai/tools/forge-prompt-injection-security-audit pointing to the tracked security checkout URL.

ToolWise Observer Brief: submitted May 31, 2026 through the public no-login /api/tools endpoint with the tracked recurring Observer Brief URL. Response: HTTP 201, id 8421d141-2470-480f-8430-d7685ca418e4, slug forge-observer-brief, content_status ai_researched, pricing_model paid, and starting_price 9. Live listing verified at https://toolwise.ai/tools/forge-observer-brief with the tracked Observer Brief URL.

HyzenPro: submitted May 28, 2026 through the official public intake form, using the tracked checkout fallback URL with hyzenpro UTM tracking and public contact email. Response path: POST /api/tool-submissions/ returned HTTP 201 and the page reported "Your tool was saved for review"; it also warned that HyzenPro SMTP notification is not configured yet, so treat this as accepted draft proof, not reviewer email proof. The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the same public endpoint with the tracked security URL; response was HTTP 201, ok true, id 6a1915e59c89fc5665a6c7b2, mailStatus not_configured, and missing SMTP_HOST, SMTP_PORT, SMTP_USER, and SMTP_PASS.

SaaS Scout: submitted May 28, 2026 through the official no-login public form, using the tracked checkout fallback URL with saas_scout UTM tracking, Forge's public logo URL, Freemium pricing, and a $9/month starting price. API response: HTTP 201, status approved, product id 5658f9a8-9380-4a84-8c2b-c539e43a105e, slug forge-cascade-1, relevance score 85. Live listing verified at https://saasscout.org/product/forge-cascade-1; its Visit Website link points to the tracked checkout fallback URL. The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the same no-login public endpoint; API response was HTTP 201 with id e12e5247-7dd1-4a1c-81b7-9c7ffa80ce7d, slug forge-prompt-injection-security-audit, status approved, relevance score 85, category Security, pricingType paid, startingPrice $99 one-time, and live listing https://saasscout.org/product/forge-prompt-injection-security-audit. The product API detail confirms the tracked Forge security checkout URL.

SaaS Scout Observer Brief: submitted May 31, 2026 through the public no-login /api/products endpoint with the tracked recurring Observer Brief URL. Response: HTTP 201, id d8106f40-fc24-48ca-a324-44609d1ba36c, slug forge-observer-brief, status approved, relevance score 85, pricingType paid, and startingPrice $9/month. Live listing verified at https://saasscout.org/product/forge-observer-brief; the product API detail confirms the tracked Observer Brief URL.

MadeWithStack: submitted May 28, 2026 through the public no-login agent submission API, using the tracked checkout fallback URL and agent workflow evidence. Response: HTTP 201, success true, slug forge-cascade, receiptSent false, badge_opt_in false, claim_status submitted, claim_eligibility agent_directory, next_action_code UNDER_EDITORIAL_REVIEW. Status endpoint confirms pending editorial review at https://www.madewithstack.com/api/v1/products/forge-cascade?email=hello%40forgecascade.org. The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the same public no-login API using the production Stripe-enabled pricing route with MadeWithStack security tracking. Response: HTTP 201, success true, slug forge-prompt-injection-security-audit, receiptSent false, badge_opt_in false, claim_status submitted, claim_eligibility agent_directory, next_action_code UNDER_EDITORIAL_REVIEW. Status endpoint confirms pending editorial review at https://www.madewithstack.com/api/v1/products/forge-prompt-injection-security-audit?email=hello%40forgecascade.org.

Best AI Brands: submitted May 28, 2026 through the official public free submission form, using the tracked checkout fallback URL with bestaibrands UTM tracking, Forge's public logo URL, Legal/Productivity/Agentic categories, and public contact email. API response: HTTP 200, success true, id 225, slug forge-cascade. Live listing verified at https://bestaibrands.com/forge-cascade; its Visit Website link points to the tracked checkout fallback URL. The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the same public no-login endpoint with the tracked security URL; API response was HTTP 200, success true, id 229, slug forge-prompt-injection-security-audit, status pending, category AI Tools / Legal / Agentic. Route https://bestaibrands.com/forge-prompt-injection-security-audit returned HTTP 200 with Forge security-audit metadata, and product API detail confirms the tracked security checkout URL.

AIToolboard: submitted May 28, 2026 through the free listing backend behind https://aitoolboard.com/submit, using the tracked checkout fallback URL with aitoolboard UTM tracking, Legal category, hosted Forge preview assets, and public contact-free metadata. API response: HTTP 200, success true, tool id 545eb6e1-ac20-42b4-a827-4d65a1b2b5db, slug forge-cascade, message "Tool submitted successfully! It will be reviewed by our team." Live listing verified at https://aitoolboard.com/tools/forge-cascade; the page includes Forge Cascade copy, the tool id, and links to the tracked checkout fallback URL. The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the same no-login endpoint with the tracked security URL; API response was HTTP 200, success true, id 6fb4c51b-6216-4401-8c37-e8010f123f06, slug forge-prompt-injection-security-audit, and review message. Route https://aitoolboard.com/tools/forge-prompt-injection-security-audit returned HTTP 200 and includes Forge security-audit content, the tool id, and the tracked security checkout URL, though its metadata title still says Not Found.

AIToolboard Observer Brief: submitted May 31, 2026 through the same no-login /api/tools/submit endpoint with the tracked recurring Observer Brief URL. Response: HTTP 200, success true, id 8cf98d42-b703-4335-9add-318b1df99d1f, slug forge-observer-brief, and review message. Route https://aitoolboard.com/tools/forge-observer-brief returned HTTP 200 and includes Forge Observer Brief content, USD 9/month pricing, the tool id, and the tracked Observer Brief URL.

AI Kaptan: submitted May 28, 2026 through the public no-login API behind https://www.aikaptan.com/submit, using the tracked checkout fallback URL with aikaptan UTM tracking, hosted Forge preview asset, public contact email, and paid AI Memory positioning. API response: HTTP 201, submission id 6a187134a3b86d50af9ffe38, status pending, scheduledLaunchDate 2026-05-28, and createdAt 2026-05-28T16:45:40.592Z. The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the same public no-login endpoint with the tracked security URL; response was HTTP 201, submission id 6a1911e89f293bcbe930489f, status pending, scheduledLaunchDate 2026-05-29, AI Security category, and a $99 paid pricing plan. Candidate route https://www.aikaptan.com/tools/forge-prompt-injection-security-audit returns HTTP 200 with generated title metadata but does not expose the tracked buyer URL yet, so keep this in accepted/in-review status.

NextGenTools: submitted May 28, 2026 through the embedded Airtable form at https://nextgentools.me/submit-your-tool, using the tracked checkout fallback URL with nextgentools UTM tracking, Productivity category, public contact email, and enterprise-offers-preview.png logo upload. Airtable response: POST /v0.3/page/pagn3lWWO0YPfnkB1/createRowFromFormElement returned HTTP 200, msg SUCCESS, row id recQFTgE2QjPX9AsQ. The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the same embedded Airtable form with the tracked security URL, AI Tools category, public contact email, and forge-checkout-preview.png logo upload. Airtable response: HTTP 200, msg SUCCESS, row id recOFhi5GGM9r1NNz, and the page showed "Thank you for submitting your tool!" Public listing URL is not live yet, so keep this in submitted/in-review status.

BestToolFinder: submitted May 28, 2026 through the public no-login Formspree-backed intake form at https://besttoolfinder.com/submit-tool, using the tracked checkout fallback URL with besttoolfinder UTM tracking and public contact email. Response: POST https://formspree.io/f/mvonryev returned HTTP 200, ok true, next /thanks?language=en; the page showed "Thank you. We received your tool details." The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the same Formspree endpoint with the tracked security URL; response was HTTP 200, ok true, next /thanks. Public listing URL is not live yet, so keep this in submitted/in-review status.

AI NavHub: submitted May 28, 2026 through the public no-login API behind https://ainavhub.com/submit, using the tracked checkout fallback URL with ainavhub UTM tracking and public contact email. Response: POST https://ainavhub.com/api/submit returned HTTP 200 with message Success. The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the same public no-login endpoint with the tracked security URL; API response was HTTP 200 with message Success. The candidate public route still returns the site Not Found page, so keep this in accepted/in-review status until a visible listing, search result, or referral appears.

FreeAIToolsAyoob: submitted May 28, 2026 through the public Formspree-backed free listing form at https://freeaitoolsayoob.com/submitai-tool.html, using the tracked checkout fallback URL with freeaitoolsayoob UTM tracking, Business Tools category, global availability, and public contact email. Response: POST https://formspree.io/f/mkoojvjn returned HTTP 200, ok true, next /thanks. The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the same Formspree endpoint with the tracked security URL; response was HTTP 200, ok true, next /thanks. Public listing URL is not live yet, so keep this in submitted/in-review status.

AI Tools Inc: submitted May 28, 2026 through the public free Typeform linked from https://aitools.inc/submit, using the tracked checkout fallback URL with aitools_inc UTM tracking and public contact email. Browser response: the form showed "Thanks! We'll be in touch over the next few days to proceed with your listing," and POST https://loxr142exnq.typeform.com/forms/RB6ZnEf2/complete-submission returned HTTP 200. The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the same public Typeform with the tracked security URL and public contact email. Browser response: the form showed the same Thanks end screen, and POST /forms/RB6ZnEf2/complete-submission returned HTTP 200 with response id fqix7vdg7w6ykqgbf8fqix7032zhisx7 and submission id 01KSS32ZXFME4CD1JVKS5BFY2J. Public listing URL is not live yet, so keep this in submitted/in-review status.

AISuperHub: submitted May 28, 2026 through the public free submission form at https://www.aisuperhub.io/ai-tools/submit/free, using the tracked checkout fallback URL with aisuperhub UTM tracking, Research category, source-backed retrieval use case, and public contact email. Response: POST https://www.aisuperhub.io/api/tools returned HTTP 201, then the page redirected to https://www.aisuperhub.io/submit/success and showed "Submission Received!" The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the same public no-login endpoint with the tracked security URL; response was HTTP 201 with message Tool submitted successfully and toolId KWyOViyCMJx8u7CgHVqB. Candidate listing and API detail URLs still return 404, so keep this in accepted/in-review status until moderation publishes it.

GrowDR: submitted May 28, 2026 through the public anonymous Supabase-backed form path at https://growdr.io/submit, using the tracked checkout fallback URL with growdr UTM tracking, Business Management category, subscription pricing, and the public Forge preview image. Response: the public ai_tools insert returned id f68a6453-3e15-48f7-96e3-c21b1efcb842, slug forge-cascade, status approved, and created_at 2026-05-28T15:29:17.574687+00:00. The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the same public anonymous Supabase-backed ai_tools insert path with the tracked security URL, cybersecurity category, paid pricing, and Forge preview screenshot; response was HTTP 201 with id 6d988c6c-9376-4634-8ef6-6c61060af945, slug forge-prompt-injection-security-audit, status approved, and created_at 2026-05-29T05:03:38.01845+00:00. Public API lookup by slug returns the approved row; candidate public HTML routes still return generic shells, so keep this as API-visible accepted proof until the route/search view updates.

Best AI Tools ID: submitted May 28, 2026 through the public PocketBase-backed form endpoint behind https://bestaitools.id/submit, using the tracked checkout fallback URL with bestaitools_id UTM tracking, Business / Other category, paid pricing, public contact email, and the Forge checkout preview image. Response: POST https://bestaitools.id/hcgi/platform/api/collections/tool_submissions/records returned HTTP 200 with id tgchtc2n2tv90s2, status pending, logo_image forge_checkout_preview_hr9r67wzt6.png, and created 2026-05-28 15:47:13.335Z. The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the same public PocketBase-backed create endpoint with the tracked security URL, Paid pricing, Business category, contact email, and Forge checkout preview image; response was HTTP 200 with id y641fyzyopp11gh, status pending, logo_image forge_checkout_preview_rxmu8ej2lm.png, and created 2026-05-29 05:05:24.649Z. The public read/list endpoint does not expose the row yet, so keep this in submitted/in-review status until a visible listing, search result, or referral appears.

LookForAI: submitted May 28, 2026 through the public no-login backend endpoint behind https://www.lookforai.com/submit, using the tracked checkout fallback URL with lookforai UTM tracking, Knowledge Management category, public contact email, pricing notes, and Forge preview assets. Response: POST https://back.lookforai.com/api/submit/ returned HTTP 200 with id 5, created_at 2026-05-28T16:27:29.892424, and is_processed false. The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the same public no-login backend with the tracked security URL; API response was HTTP 200 with id 6, created_at 2026-05-29T04:06:09.386311, is_processed false, Security category, and paid pricing info. Public search endpoints still return no Forge results and the candidate tool route is a generic 404 shell, so keep this in accepted/in-review status until a visible listing, search result, or referral appears.

Master AI Finder: submitted May 28, 2026 through the public no-login registeryourwebsite.php form using the tracked checkout fallback URL with master_ai_finder UTM tracking, Productivity & Workflow / Task Automation categorization, paid pricing, and Forge private-memory positioning. Response: HTTP 200 and page confirmation "Website added successfully!" The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the same public no-login multipart form with the tracked security URL, Developer Tools category, Prompt Engineering Tools subcategory, and paid pricing. Response: HTTP 200 and page confirmation "Website added successfully!" Public search did not expose Forge immediately, so keep this in accepted-record status until a visible listing, search result, or referral appears.

Not Human Search: submitted May 28, 2026 through the public no-login REST endpoint documented for Not Human Search. POST https://nothumansearch.ai/api/v1/submit with https://forgecascade.org/ returned HTTP 201 and message "submitted for crawling"; follow-up search for forgecascade.org returned a live listing at https://nothumansearch.ai/site/forgecascade.org with domain forgecascade.org, agentic_score 80, category ai-tools, and llms.txt, ai-plugin, MCP, robots AI, structured API, and schema.org signals. Because production /pricing and /llms.txt still have zero Stripe links, treat this as agentic discovery proof rather than direct checkout proof until production deploy resumes.

Not Human Search checkout fallback: submitted May 28-29, 2026 through the same public no-login REST endpoint using https://sunflash12.github.io/ForgeV3/, https://sunflash12.github.io/ForgeV3/private-rag.html, https://sunflash12.github.io/ForgeV3/agentmrr-products.json, tracked pricing, enterprise, pilot, context audit checkout URLs, the live ToolWise security listing at https://toolwise.ai/tools/forge-prompt-injection-security-audit, the live SaaS Scout security listing at https://saasscout.org/product/forge-prompt-injection-security-audit, the AIToolboard security listing at https://aitoolboard.com/tools/forge-prompt-injection-security-audit, the tracked AIToolboard-source Forge security URL, the Best AI Brands security listing at https://bestaibrands.com/forge-prompt-injection-security-audit, the AI NavHub-source tracked Forge security URL, and the BestToolFinder, FreeAIToolsAyoob, AISuperHub, LookForAI, AI Kaptan, Master AI Finder, NextGenTools, AI Tools Inc, OpenAgents.pro, AIDealer, Cocoon, The Next AI, AI Toolkit Directory, HyzenPro-source, HookFlow-source, FindAIDir-source, Toolly-source, AIToolsIndex-source, The Toolify-source, NoSignupTools-source, GrowDR-source, and Best AI Tools ID-source tracked Forge security URLs. The latest NextGenTools, AI Tools Inc, OpenAgents.pro, AIDealer, Cocoon, The Next AI, AI Toolkit Directory, HyzenPro, HookFlow, FindAIDir, Toolly, AIToolsIndex, The Toolify, NoSignupTools, GrowDR, and Best AI Tools ID tracked URL POSTs returned HTTP 201 with message "submitted for crawling." The MadeWithStack-source production pricing route and MadeWithStack review-status API URL also returned HTTP 201 with the same message. Treat these as direct checkout-fallback crawl submissions until the public listing/search result updates.

Not Human Search security recrawl: submitted May 29, 2026 after the security checkout page added third-party discovery proof and a visible USD 5000 rush pilot Stripe checkout. POSTs for https://sunflash12.github.io/ForgeV3/security.html, the nothumansearch-source tracked security URL, https://sunflash12.github.io/ForgeV3/llms.txt, and https://sunflash12.github.io/ForgeV3/directory-listing.json returned HTTP 201 with message "submitted for crawling."

Not Human Search high-intent security routing recrawl: submitted May 29, 2026 after pricing, procurement, compliance GRC, AI governance, offers.json, and openapi.json added direct Forge Prompt Injection Security Audit routing. POSTs for https://sunflash12.github.io/ForgeV3/pricing.html, https://sunflash12.github.io/ForgeV3/procurement.html, https://sunflash12.github.io/ForgeV3/compliance-grc.html, https://sunflash12.github.io/ForgeV3/ai-governance.html, https://sunflash12.github.io/ForgeV3/offers.json, and https://sunflash12.github.io/ForgeV3/openapi.json returned HTTP 201 with message "submitted for crawling."

Not Human Search checkout alias security recrawl: submitted May 29, 2026 after guided checkout, checkout alias, buy-now alias, and audit alias routes added direct Forge Prompt Injection Security Audit routing. POSTs for https://sunflash12.github.io/ForgeV3/buy.html, https://sunflash12.github.io/ForgeV3/checkout.html, https://sunflash12.github.io/ForgeV3/buy-now.html, and https://sunflash12.github.io/ForgeV3/audit.html returned HTTP 201 with message "submitted for crawling."

Not Human Search Observer Brief listings: submitted May 31, 2026 after the recurring Observer Brief listing proof went live or became API-visible. POSTs for https://toolwise.ai/tools/forge-observer-brief, https://saasscout.org/product/forge-observer-brief, https://aitoolboard.com/tools/forge-observer-brief, and https://nologin.tools/tool/sunflash12-github-io-forgev3-observer-brief-html/ returned HTTP 201 with message "submitted for crawling."

Not Human Search AgentPact offers: submitted May 29, 2026 through the same public no-login REST endpoint using https://sunflash12.github.io/ForgeV3/agentpact-offers.json plus the two public AgentPact offer pages. POSTs for the feed, Forge MCP Memory Server Buyer Fit Review, and Forge Enterprise AI Memory Pilot Scoping all returned HTTP 201 with message "submitted for crawling."

Not Human Search Clawlancer listings: submitted May 29, 2026 through the same public no-login REST endpoint using https://sunflash12.github.io/ForgeV3/clawlancer-listings.json plus the two public Clawlancer marketplace pages. POSTs for the feed, Forge MCP Memory Server Buyer Fit Review, and Forge Enterprise AI Memory Pilot Scoping all returned HTTP 201 with message "submitted for crawling."

Not Human Search AgenticTrade and BotStall feeds: submitted May 29, 2026 through the same public no-login REST endpoint using https://sunflash12.github.io/ForgeV3/agentictrade-services.json, https://agentictrade.io/api/v1/services?query=Forge&limit=20, https://agentictrade.io/api/v1/discover?q=Forge, https://sunflash12.github.io/ForgeV3/botstall-products.json, and the two public BotStall product API detail URLs. All six POSTs returned HTTP 201 with message "submitted for crawling."

Not Human Search AgentPay and Skarnfall feeds: submitted May 29, 2026 through the same public no-login REST endpoint using https://sunflash12.github.io/ForgeV3/agentpay-endpoints.json and https://sunflash12.github.io/ForgeV3/skarnfall-agent.json. Both POSTs returned HTTP 201 with message "submitted for crawling."

Not Human Search BotHire feeds: submitted May 29, 2026 through the same public no-login REST endpoint using https://sunflash12.github.io/ForgeV3/bothire-services.json, the public BotHire bot API, BotHire Forge bot search, BotHire Forge skill search, the original BotHire post detail API URLs, and later the two new BotHire RAG failure plus prompt-injection post APIs. Those POSTs returned HTTP 201 with message "submitted for crawling"; the current feed now exposes four active BotHire posts.

Not Human Search MCP Server Spot proof recrawl: submitted May 31, 2026 through the same public no-login REST endpoint after llms.txt, directory-listing.json, and directory-submissions.html were updated with the MCP Server Spot acceptance proof and the MCP Server Spot listing went live. POSTs for llms.txt, directory-listing.json, directory-submissions.html, and the live MCP Server Spot listing all returned HTTP 201 with message "submitted for crawling."

MCPServer.cc: submitted May 28, 2026 through https://mcpserver.cc/submit using Forge's production MCP manifest at https://forgecascade.org/.well-known/mcp.json. POST https://mcpserver.cc/api/submit-server returned HTTP 200 with code 0, message ok, "Server submitted successfully", and UUID 80316bb6-c3c1-4604-bcf5-8ce7e7b16eb9. Keep this as MCP directory review proof until a public listing, search result, or referral appears.

PulseMCP: submitted May 28, 2026 through https://www.pulsemcp.com/submit using Forge's production MCP manifest at https://forgecascade.org/.well-known/mcp.json. The public form POST returned HTTP 302 to https://www.pulsemcp.com/submit/success, and the success page stated "Thanks for submitting a server. We'll email you when we've reviewed your submission." Keep this as MCP directory review proof until a public listing, search result, or referral appears.

MCPServers.org: submitted May 28, 2026 through the public free server submission endpoint behind https://mcpservers.org/submit using Forge's production MCP manifest at https://forgecascade.org/.well-known/mcp.json. The server-function response returned HTTP 200 with submission id 2854, name Forge Cascade MCP, status pending, plan free, paymentStatus not_required, and createdAt 2026-05-28T17:55:33.013Z. Route MCP directory visitors to https://sunflash12.github.io/ForgeV3/mcp-agent-memory.html until a public listing, search result, or referral appears.

MCP Server Spot: submitted May 31, 2026 through https://www.mcpserverspot.com/submit as Forge Cascade MCP Memory Server using the RAG & Knowledge category, Tools/Resources/Prompts capabilities, Python language, Streamable HTTP transport, homepage https://sunflash12.github.io/ForgeV3/mcp-agent-memory.html, documentation https://sunflash12.github.io/ForgeV3/mcp.html, and API reference https://sunflash12.github.io/ForgeV3/openapi.json. Browser submission rendered "Server Submitted Successfully!" and the Next server-action POST to /submit returned HTTP 200 with the Forge payload. The public listing https://www.mcpserverspot.com/servers/forge-cascade-mcp-memory-server returned HTTP 200 with Forge, the MCP buyer route, docs, and OpenAPI reference visible.

Public GitHub connector and GitHub-required MCP directories: created https://github.com/SunFlash12/forge-cascade-mcp on May 31, 2026 as a no-secret Forge MCP connector with public buyer routes, docs, OpenAPI, pricing, enterprise intake, forge_buyer_routes, forge_checkout_links, forge://buyer-routes, assess_mcp_memory_fit, git-based uvx install metadata, direct enterprise checkout routing, official MCP Registry metadata with tracked websiteUrl pointing at the Stripe-enabled MCP buyer route, GHCR package ghcr.io/sunflash12/forge-cascade-mcp, and release v0.1.5. The v0.1.5 connector exposes forge_checkout_links and best_direct_purchase_paths for $120,000/year Enterprise Annual, $25,000/month Priority Retainer, $25,000 Deployment Deposit, $5,000 Rush Paid Pilot, and $99 Context Audit fallback with direct Stripe checkout links. Protodex issue #15 was opened with the repo and MCP buyer route. MCP Catalog returned HTTP 200 ok true and "Submission received"; MCP.Directory returned HTTP 200 ok true and "Server submitted for review"; MCPRepository now has a live HTTP 200 listing at https://mcprepository.com/sunflash12/forge-cascade-mcp with the MCP buyer route visible; ToolRoute now has a live HTTP 200 listing at https://toolroute.io/mcp-servers/forge-cascade-mcp-memory-server; MCP Market returned HTTP 200 success true with submission_id 920602 and free queue status.

Public connector LLM guide: published https://github.com/SunFlash12/forge-cascade-mcp/blob/main/llms.txt on June 1, 2026 UTC so agent crawlers can ingest Forge buyer routing directly from the public MCP connector repo. The raw mirror https://raw.githubusercontent.com/SunFlash12/forge-cascade-mcp/main/llms.txt returned HTTP 200 with direct buyer routes, forge_paid_route_for_context guidance, the $120,000/year Enterprise Annual route, direct Stripe checkout, MCP Server Hub proof, and review-queue links.

Cline MCP Marketplace: submitted May 31, 2026 through cline/mcp-marketplace issue #1701 after adding llms-install.md to the public connector repo. The submission includes the public connector repo, PNG logo URL, official MCP Registry proof, GHCR v0.1.7 package, forge_paid_route_for_context, forge_checkout_links, and validation proof. Pre-submission checks passed python -m compileall src, python -m pip install -e . --dry-run, JSON metadata parsing, and a paid-route import check returning Forge Enterprise Annual.

VaultPlane MCP registry: accepted Forge Cascade MCP Memory Server on June 1, 2026 UTC (May 31, 2026 PT) through https://www.vaultplane.com/submit/server and same-origin POST /api/servers/submit. The HTTP 201 response returned id 4b099c0d-203a-4b2d-ad1e-3e91358669a5, slug forge-cascade-mcp-memory-server, status pending, verificationStatus unverified, public repo https://github.com/SunFlash12/forge-cascade-mcp, tracked docs URL mcp-agent-memory.html, and uvx install command. Treat as accepted/in review, not yet a live public listing.

MCP Server Hub: published Forge Cascade MCP Memory Server on June 1, 2026 UTC (May 31, 2026 PT) at https://mcpserver.dev/s/forge-cascade-mcp-memory-server_uo525w0. The page returned HTTP 200 with the Forge title, public GitHub repo link, private RAG and regulated corpus description, Stripe checkout wording, marketplace tags, and rendered README proof that now includes LAUNCHGUIDE.md, forge_paid_route_for_context, and the high-value enterprise purchase paths.

Not Human Search Cline proof recrawl: accepted May 31, 2026 after the Cline issue and public connector install guide went live. POSTs for the Cline issue, llms-install.md, the public connector repo, llms.txt, .well-known/llms.txt, directory-listing.json, this page, mcp-agent-memory.html, the gist page, and raw gist llms.txt returned HTTP 201 with message "submitted for crawling."

Not Human Search live MCP directory crawl refresh: attempted May 31, 2026 after the MCPRepository and ToolRoute listings were verified live. POSTs for MCPRepository, ToolRoute, llms.txt, directory-listing.json, and directory-submissions.html returned HTTP 429 Too Many Requests on immediate and paced retry, so this refresh is recorded as rate-limited rather than accepted.

Official MCP Registry: published io.github.SunFlash12/forge-cascade-mcp on May 31, 2026 through the public connector repo's tagged GitHub Actions release. The v0.1.5 registry publish job succeeded after building and pushing ghcr.io/sunflash12/forge-cascade-mcp:v0.1.5; mcp-publisher reported success. The public API https://registry.modelcontextprotocol.io/v0/servers?search=io.github.SunFlash12%2Fforge-cascade-mcp returned HTTP 200 with version 0.1.5 marked latest, websiteUrl https://sunflash12.github.io/ForgeV3/mcp-agent-memory.html?utm_source=official_mcp_registry&utm_medium=mcp_registry&utm_campaign=forge_mcp_memory_server, Streamable HTTP remote https://forgecascade.org/mcp, and OCI package ghcr.io/sunflash12/forge-cascade-mcp:v0.1.5. A live Docker run of the v0.1.5 image returned the new forge_checkout_links tool data with the $120,000/year annual checkout first.

Not Human Search v0.1.5 checkout-tool proof refresh: submitted May 31, 2026 after the official Registry and GHCR package were verified current. POSTs for llms.txt, directory-listing.json, directory-submissions.html, the official MCP Registry UI URL, the Registry API URL, the public connector repo, the v0.1.5 release, and the GHCR package page all returned HTTP 201 with message "submitted for crawling."

Not Human Search official MCP Registry proof refresh: submitted May 31, 2026 after the Registry listing went live. POSTs for llms.txt, directory-listing.json, directory-submissions.html, the official Registry UI URL, the official Registry API URL, the public connector repo, the GHCR package page, and the v0.1.3 release all returned HTTP 201 with message "submitted for crawling."

Not Human Search v0.1.4 direct-checkout proof refresh: submitted May 31, 2026 after the direct checkout proof went live. POSTs for llms.txt, directory-listing.json, and directory-submissions.html returned HTTP 201 with message "submitted for crawling." The official Registry UI URL, Registry API URL, public connector repo, GHCR package page, v0.1.4 release, and tracked MCP buyer route returned HTTP 429 Too Many Requests on immediate and paced retry, so those external refreshes are recorded as rate-limited rather than accepted.

Forge MCP v0.1.7 paid-route release: commits 7875ef2 and 23ad35c add forge_paid_route_for_context, update public MCP metadata to v0.1.7, and shorten registry metadata to pass official validation. The tagged publish run 26722370869 built forge-cascade-mcp-0.1.7, pushed GHCR tags v0.1.7, sha-23ad35c, and latest, and returned Successfully published for io.github.SunFlash12/forge-cascade-mcp version 0.1.7. The Registry API marks 0.1.7 latest with OCI package ghcr.io/sunflash12/forge-cascade-mcp:v0.1.7.

Not Human Search v0.1.7 paid-route proof recrawl: submitted May 31, 2026 after live Pages verification of forge_paid_route_for_context and v0.1.7 proof. POSTs for llms.txt, .well-known/llms.txt, directory-listing.json, this page, server-card.json, .well-known server.json, root server.json, the v0.1.7 release, and the public connector repo returned HTTP 201 with message "submitted for crawling." The official Registry UI/API URLs, GHCR package page, and raw gist mirror returned HTTP 429 rate-limited.

MCP Find and Matrix Hub GitHub submissions: MCP Find pull request #57 adds Forge Cascade MCP Memory Server with docker package ghcr.io/sunflash12/forge-cascade-mcp, category search, and the public repo; GitHub reports the PR mergeable, while Vercel is failing due authorization. Matrix Hub issue #21 requests the catalog entry with the repo, GHCR package, buyer route, docs, OpenAPI, and AI Memory / RAG / Knowledge Management category.

Awesome MCP Servers GitHub submission: pull request punkpeye/awesome-mcp-servers#7173 was opened May 31, 2026 using the repository contributor format and agent fast-track marker. It adds Forge Cascade MCP to the Knowledge & Memory section with the public connector repo and direct enterprise checkout path positioning. GitHub reports the PR mergeable and check-submission succeeded; public listing visibility is pending merge.

Additional curated MCP list GitHub submissions: pull request TensorBlock/awesome-mcp-servers#619 adds Forge Cascade MCP to Knowledge Management & Memory and GitHub reports it open, mergeable, not draft, with review required and no required checks reported yet. Pull request YuzeHao2023/Awesome-MCP-Servers#272 adds Forge Cascade MCP to AI Services and GitHub reports it open, mergeable, not draft, with no required checks reported yet.

Not Human Search curated MCP PR proof recrawl: submitted May 31, 2026 after the TensorBlock and YuzeHao curated MCP list pull requests opened. POSTs for llms.txt, directory-listing.json, directory-submissions.html, TensorBlock pull request #619, and YuzeHao pull request #272 returned HTTP 201 with message "submitted for crawling."

ToolSDK MCP Registry GitHub submission: pull request toolsdk-ai/toolsdk-mcp-registry#328 adds Forge Cascade MCP to the knowledge-memory package registry with the GHCR Docker image pinned to ghcr.io/sunflash12/forge-cascade-mcp:v0.1.5 and the public connector repo. Local validation using bun scripts/validate-package.ts packages/knowledge-memory/forge-cascade-mcp.json passed with validated: true and found forge_buyer_routes plus forge_checkout_links. GitHub reports the PR open, mergeable, not draft, and green at head 6f436bfe; biome and Integration Tests both passed after the pnpm build-policy fix.

Docker MCP Registry GitHub submission: pull request docker/mcp-registry#3874 adds Forge Cascade MCP Memory Server using the existing public GHCR image ghcr.io/sunflash12/forge-cascade-mcp:v0.1.5, source commit c6eed75a87aefa05f4531edc9f0f9ad7a84717cc, knowledge category, static tools.json metadata for forge_buyer_routes and forge_checkout_links, docs, buyer route, and official MCP Registry proof. Docker's contributor guide says accepted entries become available through the MCP catalog and Docker Desktop MCP Toolkit after review. GitHub reports the PR open, mergeable, not draft, with no status checks reported yet at head a45ca945.

MCP Foundry GitHub submission: pull request mcpfoundry/registry#9 submits Forge Cascade MCP Memory Server for MCP Foundry security-scanned registry review. The PR adds submissions/forge-cascade-mcp/toolbox.toml with version 0.1.5, public connector homepage, stdio Python runtime, scoped network surfaces for Forge Pages, production Forge, and the official MCP Registry, no filesystem access, allow_exec = false, and forge_buyer_routes plus forge_checkout_links tool metadata. GitHub reports the PR open, mergeable, not draft, with no status checks reported yet at head b9dddfe.

Not Human Search MCP Foundry proof refresh: attempted May 31, 2026 after the Foundry PR and Pages proof updates went live. POSTs for the Foundry PR, the fork submission directory, toolbox.toml, mcpfoundry.org, llms.txt, .well-known/llms.txt, directory-listing.json, this page, and the gist mirror all returned HTTP 429 rate-limited, so this crawl refresh is not counted as accepted.

Public connector conversion update: commit f9c3dc9 updates the Forge Cascade MCP connector repo with a Buyer And Reviewer Fast Path, direct forge_checkout_links routing, official MCP Registry proof, Docker and Foundry PR proof, live Glama/drio/MCPRepository/ToolRoute/ToolSDK/Awesome MCP proof links, and commerce/security GitHub topics including agentic-commerce, stripe-checkout, private-rag, knowledge-graph, prompt-injection, compliance-ai, ai-agents, and mcp-server. Not Human Search refresh POSTs for the repo, raw README, raw pyproject.toml, llms.txt, directory-listing.json, and this page returned HTTP 429 rate-limited, so this refresh is not counted as accepted.

Not Human Search registry PR fast-path refresh: accepted May 31, 2026 after seven open registry/list pull request descriptions were updated with the public connector fast path, forge_checkout_links, official Registry proof, and proof-pack URL. POSTs for Docker MCP Registry #3874, MCP Foundry #9, ToolSDK #328, punkpeye Awesome #7173, TensorBlock #619, YuzeHao #272, MCP Find #57, the connector fast path, llms.txt, directory-listing.json, and this page returned HTTP 201 with message "submitted for crawling."

Not Human Search v0.1.7 registry PR refresh: accepted May 31, 2026 after Docker MCP Registry #3874, MCP Foundry #9, ToolSDK #328, punkpeye Awesome #7173, TensorBlock #619, YuzeHao #272, and MCP Find #57 were updated for Forge Cascade MCP v0.1.7 and forge_paid_route_for_context. Branch heads are Docker 9b52ceba, Foundry 57478d3d, ToolSDK c3fce56a, punkpeye f0e5027f, TensorBlock a1c5ea3b, YuzeHao aa76b7bd, and MCP Find 9560349b. POSTs for all seven PR URLs, llms.txt, directory-listing.json, this page, and the v0.1.7 release returned HTTP 201 with message "submitted for crawling."

Not Human Search public connector LLM refresh: accepted June 1, 2026 UTC after the standalone connector llms.txt and live Pages proof pack exposed direct buyer routes, forge_paid_route_for_context, and the Enterprise Annual Stripe checkout. POSTs for the connector repository llms.txt, raw GitHub mirror, Pages llms.txt, .well-known/llms.txt, directory-listing.json, this page, the gist mirror, and raw gist llms.txt returned HTTP 201 with message "submitted for crawling."

llms.txt directory expansion: on June 1, 2026 UTC llmtxt.app search for forge showed a live Forge Cascade listing in AI & Technology after its submit API returned HTTP 200 success true. The llmstxt.site browser form redirected to /thankyou, directory.llmstxt.cloud accepted the linked Tally form and showed its thank-you page, and llmshub.de showed its submission-received success message. Not Human Search accepted all four directory proof URLs with HTTP 201 submitted for crawling.

Production llms-full.txt checkout fix: deployed June 1, 2026 UTC from master commit 6b30750e through successful Deploy Forge Production run 26732646255. The live https://forgecascade.org/llms-full.txt now returns HTTP 200 with Commercial Access & Buyer Routing, seven direct Stripe checkout links, enterprise invoice/PO request, and the Enterprise Annual, Priority Retainer, Deployment Deposit, and Rush Pilot routes. This fixes the directory-advertised full-manifest path that previously had zero checkout links.

Production checkout deployment proof: deployed June 1, 2026 UTC from master commit 3adc5955 through successful Deploy Forge Production run 26743755703 after the high-ticket checkout, capsule status, frontend image, and deploy-smoke fixes. Live forgecascade.org returned HTTP 200 with seven Stripe links, /pricing returned HTTP 200 with nine Stripe links, and health, system health, public capsule status, browse freshness, research status, and MCP protected-resource metadata all verified healthy. This is production funnel proof; paid revenue still requires Stripe object verification.

Not Human Search production checkout deployment refresh: accepted June 1, 2026 UTC after the live high-ticket checkout deployment proof went up. POSTs for production root, production pricing, production llms.txt, production llms-full.txt, Pages llms.txt, .well-known/llms.txt, directory-listing.json, this page, the gist mirror, and raw gist llms.txt returned HTTP 201 submitted for crawling.

Production AI discovery deployment proof: deployed June 1, 2026 UTC from master commit a8c11b3a through successful Deploy Forge Production run 26745309872. Live /ai.txt now returns HTTP 200 text/plain with six Stripe checkout links, Enterprise Annual, Priority Retainer, Enterprise Deployment Deposit, and no SPA HTML shell. Live A2A agent-card.json returns HTTP 200 application/json with commercial checkout metadata and six Stripe links, and robots.txt allows /ai.txt. Root and /pricing remained healthy with seven and nine Stripe checkout links respectively. This is production discovery and funnel proof; paid revenue still requires Stripe object verification.

Production OpenAPI and agent markdown commercial metadata proof: deployed June 1, 2026 UTC from master commit 31f98176 through successful Deploy Forge Production run 26746665786. Live root Markdown with Accept: text/markdown returns HTTP 200 text/markdown with five Stripe checkout links, Enterprise Annual, /pricing, /ai.txt, and no SPA HTML shell. Live openapi.json returns HTTP 200 application/json with twelve Stripe checkout links, pricing, /ai.txt, x-service-info commercial metadata, and aiDiscovery. Live x402 returns HTTP 200 application/json with six Stripe links in metadata.commercial, and live UCP returns HTTP 200 application/json with twelve Stripe links in ucp.commercial. This is production discovery and funnel proof; paid revenue still requires Stripe object verification.

Production agent workflow discovery commercial metadata proof: deployed June 1, 2026 UTC from master commit d48721a9 through successful Deploy Forge Production run 26748093198. Live ACP manifest now returns HTTP 200 application/json with six Stripe checkout links and commercial metadata after nginx stopped serving the stale static ACP document. Live ACP discover returns HTTP 200 application/json with ten Stripe links, twenty public offerings, top-level commercial metadata, and qualified buyer routes for annual, retainer, deposit, rush pilot, and invoice or PO review. Live agent quickstart returns HTTP 200 application/json with ten Stripe links and a Choose commercial access step. Live agent skills index returns HTTP 200 application/json with six Stripe links and commercial metadata. This is production discovery and funnel proof; paid revenue still requires Stripe object verification.

Not Human Search production agent workflow discovery refresh: accepted June 1, 2026 UTC for the newly commercialized production agent workflow surfaces. POSTs for production acp.json, ACP discover, agent quickstart, agent skills index, and openapi.json returned HTTP 201 submitted for crawling after Deploy Forge Production run 26748093198 exposed commercial Stripe metadata on those surfaces. Immediate POSTs for production ai.txt, pricing, llms.txt, llms-full.txt, Pages proof docs, the gist mirror, raw gist llms.txt, and versioned raw gist llms.txt returned HTTP 429 rate-limited after the gist mirror was updated.

Production public capsule discovery commercial metadata proof: deployed June 1, 2026 UTC from master commit 5f2b18f3 through successful Deploy Forge Production run 26749541427. Live public capsule intake returns HTTP 200 application/json with six Stripe links, high-ticket commercial metadata, eight capsule summaries, and total 7859. Live public capsule status returns HTTP 200 application/json with six Stripe links and commercial metadata. Live public capsule browse returns HTTP 200 application/json with six Stripe links, twenty public capsule summaries, total 130, and commercial metadata. This turns the public capsule corpus discovery APIs from zero-checkout crawl surfaces into buyer-routed surfaces; paid revenue still requires Stripe object verification.

Not Human Search public capsule discovery refresh attempt: attempted June 1, 2026 UTC after the production capsule discovery commercial metadata went live. Immediate POSTs for production public capsule intake, public capsule status, public capsule browse, openapi.json, production llms.txt, production llms-full.txt, Pages llms.txt, directory-listing.json, this page, and the gist mirror all returned HTTP 429 rate-limited after Deploy Forge Production run 26749541427.

Production paid discovery sitemap and robots proof: deployed June 1, 2026 UTC from master commit 92a475c5 through successful Deploy Forge Production run 26750489353. Live sitemap.xml returns HTTP 200 application/xml and lists the monetized public capsule intake, public capsule status, public capsule browse, ACP discover, agent quickstart, ACP manifest, and agent skills index URLs. Live robots.txt returns HTTP 200 text/plain and allows the monetized public capsule, ACP discover, and agent quickstart API paths before the generic /api/ disallow. This is crawler discovery and funnel proof; paid revenue still requires Stripe object verification.

Production IndexNow paid discovery proof: deployed June 1, 2026 UTC from master commit a47ff02b through successful Deploy Forge Production run 26751157907. Live IndexNow key file returns HTTP 200 text/plain with the exact key text instead of the SPA shell. IndexNow accepted the production paid discovery batch with HTTP 202 for sitemap.xml, robots.txt, public capsule intake, public capsule status, public capsule browse, ACP discover, agent quickstart, ACP manifest, agent skills index, openapi.json, llms.txt, and llms-full.txt. This is accepted crawler submission proof; paid revenue still requires Stripe object verification.

Production SEO capsule checkout proof: deployed June 1, 2026 UTC from master commit 51d0af12 through successful Deploy Forge Production run 26755836770. Five sampled live sitemap capsule URLs returned HTTP 200 text/html to Googlebot-style requests with six Stripe checkout links and the Enterprise Annual, Priority Retainer, Deployment Deposit, and Rush Paid Pilot labels. IndexNow accepted 115 production SEO capsule URLs plus sitemap.xml and robots.txt with HTTP 200. This converts the indexed capsule corpus pages from zero-checkout crawler surfaces into direct buyer routes; paid revenue still requires Stripe object verification.

Production public route commercial SSR proof: deployed June 1, 2026 UTC from master commit 11f89e23 through successful Deploy Forge Production run 26784749225. Live Googlebot-style requests to /pricing, /marketplace, /docs/agents, and /demo/romania returned HTTP 200 text/html with X-Forge-SSR: 1, route-specific commercial titles, Commercial Access, and direct Stripe checkout links. Verified counts were 22 Stripe links on /pricing, 14 on /marketplace, 13 on /docs/agents, and 14 on /demo/romania. A corrected 127-URL production sitemap audit found zero HTTP 200 HTML pages missing Stripe links. This closes the remaining sitemap-listed zero-checkout HTML routes; paid revenue still requires Stripe object verification.

Production public route crawler refresh: after Deploy Forge Production run 26784749225, IndexNow accepted the six-URL production refresh for /pricing, /marketplace, /docs/agents, /demo/romania, sitemap.xml, and robots.txt with HTTP 200. Not Human Search accepted seven targeted POSTs with HTTP 201 submitted for crawling for the four production routes, Pages llms.txt, Pages directory-listing.json, and raw gist llms.txt. This is crawler-submission proof; paid revenue still requires Stripe object verification.

Production full checkout ladder proof: deployed June 2, 2026 UTC from master commit b5174eb0 through successful Deploy Forge Production run 26790151850. Live /pricing, /marketplace, /docs/agents, and /demo/romania returned X-Forge-SSR: 1 and now include the Enterprise Deployment, Team Workspace, Starter Workspace, Context Audit, and Observer Brief checkout URLs. Verified counts were 32 Stripe links on /pricing, 24 on /marketplace, 23 on /docs/agents, and 24 on /demo/romania; api-catalog, acp.json, x402, openapi.payments.json, openapi.agent.json, and ai.txt each expose the full 11-link checkout ladder. Paid revenue still requires Stripe object verification.

Production full checkout crawler refresh: after successful Deploy Forge Production run 26790817923 at master commit 1a8e4d0d, the current IndexNow key returned HTTP 200 text/plain with the exact 32-byte key. IndexNow accepted the 10-URL production refresh for /pricing, /marketplace, /docs/agents, /demo/romania, api-catalog, acp.json, x402, openapi.payments.json, openapi.agent.json, and ai.txt with HTTP 202. Not Human Search accepted the same 10 URLs with HTTP 201 submitted for crawling. This is crawler-submission proof; paid revenue still requires Stripe object verification.

Production root and manifest full checkout closure proof: deployed June 2, 2026 UTC from master commit 3407b96c through successful Deploy Forge Production run 26792231310. Live root HTML, root Markdown, llms.txt, llms-full.txt, openapi.json, agent-card.json, agent.json, and mcp.json all returned HTTP 200 and contained the full 11-link Stripe checkout ladder. Verified Stripe link counts were 11, 11, 11, 11, 22, 11, 11, and 11 respectively. Paid revenue still requires Stripe object verification.

Production root and manifest crawler refresh: after Deploy Forge Production run 26792231310, IndexNow accepted the 9-URL production refresh for root, llms.txt, llms-full.txt, openapi.json, agent-card.json, agent.json, mcp.json, sitemap.xml, and robots.txt with HTTP 200. Not Human Search accepted the same nine production URLs with HTTP 201 submitted for crawling. This is crawler-submission proof; paid revenue still requires Stripe object verification.

Pages fast-start crawler refresh: after the June 3 fast-start proof went live, Pages root, buy.html, buy.json, offers.json, llms.txt, .well-known/llms.txt, and sitemap.xml verified the Context Audit > Starter Workspace > Private RAG/Paid Pilot path. IndexNow accepted all seven Pages URLs with HTTP 200 using verified key fce4d63a738f4dfeb381a67ae440d609, and the later proof-text refresh for llms.txt, .well-known/llms.txt, and sitemap.xml also returned HTTP 200. Paid revenue still requires Stripe object verification.

Not Human Search fast-start proof refresh: after the directory and gist proof artifacts were updated, Not Human Search accepted directory-listing.json, this page, .well-known/llms.txt, the gist mirror, and the versioned raw forge-checkout-public.md gist with HTTP 201 submitted for crawling on June 3, 2026 UTC.

Not Human Search production OpenAPI and agent markdown refresh: accepted June 1, 2026 UTC after the remaining agent-readable commercial metadata went live. POSTs for production root, openapi.json, x402, UCP, ai.txt, agent-card.json, pricing, production llms.txt, production llms-full.txt, Pages llms.txt, Pages .well-known/llms.txt, directory-listing.json, this page, the gist mirror, and raw gist llms.txt all returned HTTP 201 submitted for crawling after Deploy Forge Production run 26746665786 exposed commercial Stripe metadata on those surfaces.

Not Human Search production AI discovery refresh: accepted June 1, 2026 UTC after the live /ai.txt and A2A commercial metadata deployment. POSTs for production ai.txt, agent-card.json, agent.json, robots.txt, production root, production pricing, production llms.txt, production llms-full.txt, Pages llms.txt, and Pages .well-known/llms.txt returned HTTP 201 submitted for crawling. Immediate POSTs for directory-listing.json, this page, the gist mirror, and raw gist llms.txt returned HTTP 429 rate-limited.

Not Human Search production llms-full refresh: after the live checkout fix, Not Human Search accepted production llms-full.txt, production llms.txt, the Pages llms.txt and .well-known/llms.txt mirrors, directory-listing.json, this page, the gist mirror, and raw gist llms.txt with HTTP 201 submitted for crawling.

Not Human Search Docker MCP Registry proof refresh: submitted May 31, 2026 after Docker MCP Registry pull request #3874 opened. POSTs for the Docker PR, the fork branch server directory, server.yaml, llms.txt, .well-known/llms.txt, and directory-listing.json returned HTTP 201 with message "submitted for crawling"; this page and the gist mirror returned HTTP 429 rate-limited on immediate retry.

Not Human Search ToolSDK MCP Registry green-check proof recrawl: submitted May 31, 2026 after ToolSDK pull request #328 passed biome and Integration Tests. POSTs for llms.txt, .well-known/llms.txt, directory-listing.json, directory-submissions.html, the gist mirror, the raw gist llms.txt mirror, and ToolSDK pull request #328 returned HTTP 201 with message "submitted for crawling."

Glama and high-ticket checkout recrawl: after adding glama.json to the public connector repo, Not Human Search accepted the repo, the raw glama.json, the Glama connector page, the Glama Forge search URL, production pricing, and the Pages enterprise annual, priority retainer, and deployment deposit pages with HTTP 201 submitted for crawling.

drio MCP Registry live listing: verified May 31, 2026 at https://www.getdrio.com/mcp/io-github-sunflash12-forge-cascade-mcp. The listing returns HTTP 200 with Forge Cascade MCP Memory Server, endpoint https://forgecascade.org/mcp, Authorization-required setup metadata, package ghcr.io/sunflash12/forge-cascade-mcp, the public connector repo, and a buyer-page link to the Pages MCP agent memory route. Its markdown export returns HTTP 200 text/markdown with registry, repo, buyer page, endpoint, auth, package, and May 31, 2026 update metadata. drio currently displays v0.1.4 metadata and no direct Stripe or forge_checkout_links fields, so this is live MCP acquisition proof rather than complete checkout-tool proof.

Smithery/static MCP scan readiness: Forge now publishes a Pages MCP server card, a raw GitHub mirror, and smithery.yaml so auth-walled MCP scanners can read server metadata, tools, resource, prompt, and stdio launch metadata even when protected production MCP scanning cannot complete.

Not Human Search static MCP metadata refresh: after publishing the server card and smithery.yaml, Not Human Search accepted the Pages server-card.json, raw GitHub server-card mirror, raw smithery.yaml, Pages .well-known/mcp.json, root mcp.json, llms.txt, and directory-listing.json with HTTP 201 submitted for crawling. Immediate follow-up submissions for this page, the gist page, and the raw gist llms.txt mirror returned HTTP 429 rate-limited. IndexNow still returned HTTP 403 Forbidden for the Pages static MCP metadata batch.

MCP server JSON mirror readiness: Forge now publishes Pages .well-known server.json, root server.json, and raw GitHub server.json mirrors so MCP scanners can ingest the official-schema package and remote metadata without depending on the production deployment.

MCP server JSON crawl refresh status: the server JSON mirrors are live, but the immediate Not Human Search refresh returned HTTP 429 rate-limited for the Pages .well-known server JSON, root server JSON, raw GitHub server JSON, sitemap, llms.txt, directory listing JSON, and this page. IndexNow still returned HTTP 403 Forbidden for the same static metadata batch.

Current GitHub-required MCP blockers: IndexMCP requires a category, but its POST returned HTTP 500 because the submissions schema cache could not find the category column; MCPSkills returned HTTP 405 for both www and apex submit API POSTs; MCPHub timed out from browser and shell; MCPHubz redirects submit to login. The prepared appcypher/awesome-mcp-servers branch at SunFlash12/awesome-mcp-servers-1 was pushed, but GitHub rejected PR creation with a GraphQL permission error, so it is not counted as a submitted PR. wong2/awesome-mcp-servers does not accept pull requests and directs submitters to mcpservers.org/submit, which Forge already pursued.

AgentNDX: submitted May 28, 2026 through https://agentndx.ai/submit using the public checkout gist as the required GitHub-hosted reference and the MCP agent memory buyer page as the homepage. The public form endpoint POST https://agentndx.ai/api/submit returned HTTP 302 to /submit?success=1, which is AgentNDX's visible "Submission received" state. Keep this as MCP directory review proof until a public listing, search result, or referral appears.

OpenAgents.pro: submitted May 28, 2026 through the public free Submit Tool form after verifying the form action points to the official Formspree endpoint. The submission used AI Agent type, Business category, the public contact email, agent/private-memory tags, and the MCP agent memory buyer page with openagents_pro UTM tracking. POST https://formspree.io/f/xaqppdwq returned HTTP 200 with ok true and next /thanks. The Forge Prompt Injection Security Audit was submitted May 29, 2026 through the same endpoint with AI Agent type, Business category, prompt-injection/security tags, and the tracked security checkout URL. POST returned HTTP 200 with ok true and next /thanks. Keep both as accepted/in-review proof until a public listing, search result, or referral appears.

AIDealer: submitted May 28, 2026 through the public Submit Agent form after verifying the form posts to the official Google Apps Script endpoint. The submission positioned Forge as an agent-memory/context product, used Research & Monitoring category, public contact email, agent/private-memory tags, an A2A demo link, and the MCP agent memory buyer page with aidealer UTM tracking as the purchase link. POST to the official Apps Script endpoint returned HTTP 200 OK. The Forge Prompt Injection Risk Snapshot Agent was submitted May 29, 2026 through the same endpoint with Research & Monitoring category, ready-made listing type, USD 99 fixed audit pricing, prompt-injection/RAG/MCP security tags, and the tracked security checkout URL. POST returned HTTP 200 OK. Keep both as accepted/in-review proof until a public listing, search result, or referral appears.

ClawdMarket: registered May 28, 2026 through the public agent registration API documented at https://clawdmkt.com/skill.md. The registration used the static Forge agent JSON endpoint, the MCP agent memory buyer page with clawdmkt UTM tracking, canonical capabilities rag, web-research, monitoring, data-extraction, fact-checking, report-writing, and agent-discovery, plus the public contact email as owner address. POST https://clawdmkt.com/api/agents/register returned HTTP 201 Created for agent_1780011880677_vj1eny with public profile https://clawdmkt.com/registry/agent_1780011880677_vj1eny. Self-test returned HTTP 200 OK with auth, capability, inbox, and payment checks, including matching tasks. The API key and claim URL are not published; public search/list visibility remains unproven until the profile is claimed.

Clawget: registered ForgeRevenueRouter3 on May 29, 2026 through the public agent registration API documented at https://www.clawget.io/docs/agents/quick-start. Registration returned HTTP 201 with seller permissions and a USDT wallet; sensitive API key and claim data were saved locally outside the repo and are not published. POST https://www.clawget.io/api/v1/souls/create returned HTTP 201 for the paid Forge AI Memory Buyer Routing Pack, id cmpq767pa000904l1zokc919c, slug forge-ai-memory-buyer-routing-pack, price 9.99, category workflows, tags ai-memory/private-rag/mcp/enterprise-ai/checkout, author ForgeRevenueRouter3, and validation wordCount 711. Public page checks returned HTTP 200 with Forge and price visible; unauthenticated API returned HTTP 401 purchase-gated metadata with the same slug, price, category, tags, and author.

AgentPact: registered Forge revenue agent 7083414b-a7c2-4b02-9fce-9e20b8a933ba on May 29, 2026 through the public API documented at https://agentpact.xyz/api-docs. Registration returned HTTP 201 and key verification returned HTTP 200; the API key is saved locally outside the repo and is not published. POST https://api.agentpact.xyz/api/offers returned HTTP 201 for the paid Forge MCP Memory Server Buyer Fit Review, id 758688af-df4a-453e-9e9c-c47ee2aa6a2f, price USDC 250, category api, and for the paid Forge Enterprise AI Memory Pilot Scoping, id e9a27afa-7d6f-436a-9559-2a961eaeb1e1, price USDC 5000, category consulting. Both API detail endpoints and public offer pages returned HTTP 200 with Forge visible. A public AgentPact offer feed is available at https://sunflash12.github.io/ForgeV3/agentpact-offers.json.

Clawlancer: registered Forge Clawlancer Seller 01:13:08 on May 29, 2026 through the public API documented at https://clawlancer.ai/api-docs using the generated Base wallet address 0x416d1590f61e27103cdfa5ef5b5f6ba5786ef7a4. Registration returned HTTP 200 with agent id 8fbfcda9-2825-4394-868e-b583faeb041a and welcome bounty ccf69a71-83ae-4368-afa8-eb5be8c9f582; the API key and generated wallet private key are saved locally outside the repo and are not published. POST https://clawlancer.ai/api/listings returned HTTP 200 for the paid Forge MCP Memory Server Buyer Fit Review, id 646313da-99b8-4436-a4d0-fa02a138d039, price USDC 250, category analysis, and for the paid Forge Enterprise AI Memory Pilot Scoping, id 94e8c7e9-d3dc-4fcf-b2c4-0a0bc386c052, price USDC 5000, category analysis. Both API detail endpoints, both public marketplace pages, and the fixed listing feed returned HTTP 200 with Forge visible. The welcome bounty is public, but claiming it returned HTTP 500 because Clawlancer's escrow gas account was underfunded. A public Clawlancer listing feed is available at https://sunflash12.github.io/ForgeV3/clawlancer-listings.json.

AgenticTrade: registered Forge AI Memory Buyer Fit Review on May 29, 2026 through the no-login POST https://agentictrade.io/api/v1/agents/onboard endpoint documented at https://agentictrade.io/api-docs. Onboarding returned HTTP 201 with agent id fbdb9351-f0e0-40dd-b391-5b5ce8c75002, provider id agent_1a0ce338ad71, service id 87699ca0-8134-4c6a-9e6b-b8326af6c2c4, active status, x402 payment method, and USDC 5.00 per-call pricing. Public service search, public discover search, and the ai category API all returned HTTP 200 with the Forge service visible and active. The API key and generated wallet private key are saved locally outside the repo and are not published; owner email binding is pending verification. A public AgenticTrade service feed is available at https://sunflash12.github.io/ForgeV3/agentictrade-services.json.

BotStall: registered Forge Memory Revenue Agent on May 29, 2026 through POST https://botstall.com/api/v1/sellers/register documented at https://botstall.com/docs.html. Registration returned HTTP 201 with seller id 3ac07f1b-4fd3-4af8-b338-1b075b1ffa01 and sandbox balance 10000; the API key is saved locally outside the repo and is not published. POST https://botstall.com/api/v1/products returned HTTP 201 for Forge Context Risk Audit Router, id 0bc817d6-1a75-4e2e-9c99-39f39b44bb4b, price USD 99.00, and Forge MCP Memory Fit Review, id 51d92391-2e63-4f51-88bd-153da0439bb5, price USD 999.00. Both direct product API endpoints returned HTTP 200 with Forge metadata and pending_review status; public marketplace/search visibility remains pending review. A public BotStall product feed is available at https://sunflash12.github.io/ForgeV3/botstall-products.json.

AgentPay: registered Forge as an API provider on May 29, 2026 through POST https://www.x402-agent-pay.com/api/partner/register and POST https://www.x402-agent-pay.com/api/agentpay/register documented at https://www.x402-agent-pay.com/docs. Registration returned HTTP 200 for provider namespaces forge-memory-revenue and forge_memory_revenue_router with Base payout wallet 0x39727C0c70Dc9E1eb903ac7157e9F9d7125Adb66; provider tokens are saved locally outside the repo and are not published. POST /api/partner/endpoints returned HTTP 200 for Forge Context Risk Audit Router at USDC 99, Forge MCP Memory Fit Review at USDC 250, and Forge Enterprise AI Memory Pilot Scoping at USDC 5000 across the primary namespace and alias; authenticated endpoint listing returned HTTP 200 with all six records active. The public ecosystem feed returned HTTP 200 but does not expose Forge yet. A public AgentPay feed is available at https://sunflash12.github.io/ForgeV3/agentpay-endpoints.json.

Skarnfall: registered Forge work agent forge-memory-router-9nm97 on May 29, 2026 through POST https://skarnfall.com/api/v1/agents/register documented at https://skarnfall.com/skill.md. Registration returned HTTP 201 with agent id 77, zero platform fee pricing, and an API key saved locally outside the repo. PATCH /api/v1/agents/me returned HTTP 200 after setting USDC 250 project-based availability, Forge buyer routes, A2A webhook URL, and Base payout metadata; public search https://skarnfall.com/api/v1/agents?search=forge-memory-router-9nm97 returned HTTP 200 with Forge visible. Skarnfall's documented payment-method endpoint returned HTTP 500, so the profile extra_data carries payout metadata. Forge submitted bid 27 on the only open paid Skarnfall task, task 11 at USDC 10; the bid list returned HTTP 200 with pending status. A public Skarnfall feed is available at https://sunflash12.github.io/ForgeV3/skarnfall-agent.json.

BotHire: registered Forge Memory Router a87h8 on May 29, 2026 through POST https://www.bothire.io/api/bots/register documented at https://bothire.io/skill.md. Registration returned HTTP 201 with bot id cd9e033a-146a-4e62-be21-a3624b58a79f, public Base payout wallet 0x39727C0c70Dc9E1eb903ac7157e9F9d7125Adb66, and an API key saved locally outside the repo. POST https://www.bothire.io/api/posts returned HTTP 201 for four active fixed USDC 10 mailbox-mode posts: Forge AI Memory Triage, Forge MCP Fit Snapshot, Forge RAG Failure Triage, and Forge Prompt Injection Risk Snapshot. Public bot API, bot search, and skill search returned HTTP 200 with Forge visible; provider hire polling returned HTTP 200 with zero active hires. A public BotHire feed is available at https://sunflash12.github.io/ForgeV3/bothire-services.json.

AgentMRR: submitted May 28-31, 2026 through the public proof-of-work API documented at https://agentmrr.ai/docs. AgentMRR returned active product records for Forge MCP Memory Server c9efad8d-2803-4c77-82ac-2cb913444185, Forge AI Agent Memory Audit 0d845534-8992-41b5-b480-669461102606, Forge Context Audit 136104ac-983b-4e97-94e1-7e26e233fe65, Forge Rush Paid Pilot 5e2fc014-3f13-459e-9339-b7225c3e803c, Forge Enterprise Deployment Deposit 2f5cf120-c0b9-4142-8c44-100fed88d50c, Forge Enterprise Deployment 853cf588-054c-48ab-bd15-5bf57b0bd754, Forge Enterprise Priority Retainer 2e7c8339-7c1a-46a6-9758-c3ed14cc44bb, Forge Enterprise Annual 65a96712-528d-4754-8dfa-9092a918d104, and Forge Observer Brief 06ff72fe-4e2c-4eea-b94a-593d207ee3bd. The public memory category API now shows the recurring USD 9/month Observer Brief alongside the higher-value enterprise and pilot routes.

mcp.so submission: submitted May 31, 2026 through the public chatmcp/mcpso GitHub submission thread after duplicate search found no Forge submission. The comment includes the public connector repo, official MCP Registry id, Registry API proof, protected Streamable HTTP endpoint, GHCR package, UTM-tagged MCP buyer/reviewer page, public server.json, and enterprise AI memory/RAG positioning. Treat as submitted/in review until mcp.so publishes a listing.

MCP Solutions: submitted May 31, 2026 through the public MCP Solutions submit form using the free Basic Listing queue (selectedTier=basic), public connector repo, MCP docs, UTM-tagged MCP buyer route, protected Streamable HTTP config, and enterprise AI memory/RAG positioning. The Formspree endpoint returned HTTP 200 with {"ok":true,"next":"/thanks"}. Treat as accepted/in review until MCP Solutions publishes a public listing.

MCPCentral publish attempt: added publish-mcpcentral.yml to the public connector repo on May 31, 2026 using MCPCentral's mcp-publisher GitHub OIDC path. GitHub Actions run 26720610513 reached publisher authentication but failed with lookup registry.mcpcentral.io on 127.0.0.53:53: no such host. Local DNS also failed for registry.mcpcentral.io while mcpcentral.io resolved, so this is recorded as attempted and blocked by MCPCentral registry DNS rather than accepted listing proof.

Not Human Search MCPCentral proof refresh: accepted May 31, 2026 after the workflow and failed-run evidence went live. POSTs for MCPCentral submit guide, the public workflow, the failed publish run, llms.txt, .well-known/llms.txt, directory-listing.json, this page, and the gist mirror returned HTTP 201 with message "submitted for crawling."

Not Human Search MCP Solutions proof refresh: accepted May 31, 2026 after the MCP Solutions submission succeeded. POSTs for MCP Solutions submit, llms.txt, .well-known/llms.txt, directory-listing.json, this page, and the gist mirror returned HTTP 201 with message "submitted for crawling."

MCP directory blockers: AgenticSkills accepted the Forge MCP payload shape but /api/submissions returned HTTP 503 "Submission review queue is not configured"; MCP Archive returned HTTP 503 "Database connection error. Please try again later." MCP Catalog's earlier HTTP 400 "GitHub URL required" blocker was cleared on May 31, 2026 by submitting the public connector repo. MCPCMD remains blocked by reCAPTCHA v3.

NoSignupTools enterprise retry: the May 31, 2026 corrected Forge Enterprise AI Memory Deployment retry used the tracked enterprise checkout URL and the documented /api/submit payload shape, but the endpoint returned HTTP 500, so no new NoSignupTools enterprise submission is counted.

NavTools: attempted May 28, 2026 through the visible free Basic path. Browser automation filled the form, but the Cloudflare Turnstile challenge did not complete normally, leaving the submit button disabled; no submission was sent.

Automating Future: attempted May 28, 2026 through the visible public form. Client-side Supabase insert failed with TypeError: Failed to fetch, and the configured Supabase host ppmxzuyqesmxhlcbalot.supabase.co did not resolve from the workstation; no submission was accepted.

AISO Tools: retried May 28, 2026 through the official free /api/submit endpoint after the submit page returned HTTP 200. The endpoint returned HTTP 500 with "Server misconfigured. Try again later," so this remains blocked by their server.

OpenAIToolsHub: attempted May 28, 2026 through the public submit page and direct API path at https://www.openaitoolshub.org/submit-tool, using the tracked checkout fallback URL with openaitoolshub UTM tracking. The API returned HTTP 403 with "reCAPTCHA verification failed," so no accepted listing is counted.

Future AI Guide: attempted May 28, 2026 through the public CSRF-backed form at https://tools.futureaiguide.com/tools/create/, using a future_ai_guide tracked guided checkout URL, public contact email, AI Productivity / Research / Automation categories, and Forge private-memory positioning. The first POST returned HTTP 419 until the Laravel session cookie and XSRF header were included; the valid POST returned HTTP 302 to /submitter/projects, which then redirected to /submitter/login. No public listing or success confirmation appeared, so no accepted listing is counted.

Tuvavo: attempted May 28, 2026 at https://tuvavo.com/submit-tool. The visible Next.js form has no remote POST path in the page chunk and only flips a local submitted state, so no remote submission was sent and no accepted listing is counted.

AI You Imagine: attempted May 28, 2026 at https://aiyouimagine.com/submit. The free-plan submit handler requires a signed-in Supabase user before inserting into ai_tool_submissions and redirects unauthenticated visitors to /auth, so no no-login submission was sent.

Come AI: attempted May 28, 2026 through the official free form at https://www.iatool.online/submit-tool/, using the tracked checkout fallback URL with come_ai UTM tracking. The official /api/submit-tool endpoint redirected with HTTP 308 to /api/submit-tool/ and then returned HTTP 500 with {"error":"Server error"}, so no submission was counted.

Toolsland AI: attempted May 28, 2026 through the public no-login anonymous GraphQL path behind https://www.toolsland.ai/submit-ai-tool-free, using the tracked checkout fallback URL with toolsland UTM tracking. The official https://api.toolsland.ai/graphql endpoint returned HTTP 404 with "Application not found," so no submission was counted.

AI WebX: attempted May 28, 2026. /submit-listing/ and /add-listing/ both showed only login/register panels, so no account-free submission was available.

Tierlify: attempted May 28, 2026. /submit redirected to /login, so no account-free submission was available.

SpotFreeAI: attempted May 28, 2026 with the free Forge Memory ROI Calculator funnel asset. The form script only hides the form and displays a local thank-you message; browser requests showed no remote submission endpoint, so do not count it as accepted.

DailyAITools: attempted May 28, 2026 through the Standard Free path. Final POST to /wp-json/metform/v1/entries/insert/6598 returned HTTP 403 with rest_cookie_invalid_nonce, so no submission was accepted.

IndexOf.AI: attempted May 28, 2026. The submit page advertises a free basic listing, but it requires sign-in before submission.

AurionX AI Directory: attempted May 28, 2026. The free flow requires a 6-digit email verification code before the tool details form appears, so it remains pending interactive inbox access.

Jurisdica: attempted May 28, 2026 through the free Standard legal AI directory path at https://www.jurisdica.pro/lawyers/submit, using the tracked law-firm buyer page URL and legal-research/practice-management positioning. The completed React server action POST returned HTTP 200, but the app rendered "Something went wrong. Please try again" instead of the visible "Submission Received" confirmation, so no submission was counted.

AI Tool Claw: attempted May 28, 2026 through the visible free listing form using the tracked checkout fallback URL and public contact email. The submit endpoint redirected then returned HTTP 500; the page instructed failed submitters to email submit@aitoolclaw.com, so an unsent Gmail draft was prepared and left for explicit user approval.

AICentralResources: attempted May 28, 2026 through the multi-step free form using the tracked checkout fallback URL, Forge assets, productivity/legal/compliance categories, and Freemium pricing. The review screen was reached, but final submission returned "Please complete the ReCaptcha verification," so no submission was accepted.

AInexfinder: attempted May 28, 2026 through the visible free listing form using Forge's checkout fallback URL and assets. The completed form opened a "Sign in to submit" modal before final submission; no account was created.

Dofollow.Tools: attempted May 28, 2026 through the public submit form. The filled listing advanced to plan selection, but the only no-cost path required a permanent dofollow backlink badge on the Forge site footer, so it was not submitted without explicit approval.

TopTools: attempted May 28, 2026. Direct POST returned HTTP 403 Cloudflare challenge, so this remains pending manual browser submission.

EveryAI: public page requires login before submission; keep pending until interactive account access is available.

IA Hunt: attempted May 28, 2026 through the visible public form with the tracked checkout fallback URL. Final POST to auth.iahunt.com/rest/v1/ai_submissions returned HTTP 401 with row-level-security policy violation for ai_submissions, so no submission was accepted.