Freebox MCP Server

Freebox MCP server exists for a simple reason — assistants are far more useful when they can act on Freebox directly instead of describing what you should do. Find free stuff near any US ZIP, priced for resale. Live listings, resale estimates, alerts.

What you get

Freebox tracks free curbside and giveaway listings across 400+ US metros, prices every find with an LLM valuation chain, and ranks them by estimated resale value. This remote MCP server exposes that feed to Claude and any other MCP client.

What the assistant can call

Once Freebox is connected, these are the calls the assistant has available:

• find_free_stuff — Search live free listings near a ZIP, ranked by estimated resale value + profit
• area_summary — Counts and total estimated value of free finds around a ZIP

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Freebox's toolset — find_free_stuff, area_summary — is a fair guide to whether it matches your workflow. It is maintained by com.usefreebox; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the freebox mcp server does with a few real requests.