Exbridge

The Laravel deploy that returns 404 on every route, with nothing in the logs.

If you've put Laravel on cheap shared hosting, you know this one. You upload the app, point the rewrite at public/index.php, and every route 404s. Homepage, /login, all of it. No error page. Logs empty.

The cause is SCRIPT_NAME. Laravel derives its base path from it, and rewriting straight to public/ makes that value wrong. The fix is a four-line entry point — but you won't find it in the official docs, because every Laravel deployment guide assumes a VPS and root access.

This kit is the gap between "here's your FTP and cPanel" and those guides:

• The three config files that run Laravel from a subdirectory (.htaccess, root entry point, public/.htaccess with the line that 500s on most shared hosts removed)

• Seven failures documented with the actual symptom, not the theory

Written from an account with FTP, a control panel, and a few dollars a month — the same thing you have.

$9, one time.

https://whop.com/laravel-shared-hosting/

Does an AI search engine have enough to quote your page?

Not "is it indexed" — whether an answer engine can pull a claim from your page and attribute it to you. That comes down to boring, checkable things: robots.txt and llms.txt, JSON-LD that matches what's on the page, meta that isn't a template, a visible last-updated date, and a brand name spelled the same way everywhere.

Kurage GEO checks those and returns a 100-point score with the specific fixes, each one cited to what it found. No LLM guesswork in the audit itself — it's deterministic, so the same page scores the same twice.

A credit also buys a grounded answer simulation: it asks an AI about your brand using your page as the evidence, so you can read what an answer engine would actually say about you today.

1 credit = 1 audit or 1 simulation. $3. No subscription — buy what you use.

https://whop.com/kurage-geo/

Just shipped: MCP database access that can't drop your tables.

To let an agent fix one customer's phone number, most people hand it a connection string — which also lets it delete everything. The usual answer is "keep AI away from the database", and that costs you the work the agent could have done.

So we built the opposite: a tool where you declare what exists.

'customers' => array(

'columns' => array('id','name','email','phone'),

'editable' => array('name','email','phone'),

'can_delete' => false,

),

Anything undeclared is invisible — to your agent and to your staff. There is no tool that accepts raw SQL. Ask for a table you didn't declare and you get "This table is not allowed". Try to delete where deletion is off and it refuses.

One PHP file. No Node, no Composer. Connect in a single line:

claude mcp add kdbagent -- php kdbagent_mcp.php

Seven tools (tables, schema, select, get, insert, update, delete), plus a read-only mode that hides the write tools entirely. A bridge is included for a server you already run, so credentials never leave it — we run our own production database this way, on both Claude Code and Codex.

$79 one-time, MIT licence. Modify it, resell it, ship it inside your own product.

https://whop.com/checkout/plan_niieVCx2TMmcr