best.fama/ads
Fama
Is the Fama MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-14.
Ask what your Meta ads spend and what to stop; pause and change budgets inside limits you set.
needs auth probed 2026-11-14 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","id":null,"error":{"code":-32600,"message":"Sign in to Fama to use this tool, or send a key m- Endpoint
- https://fama.best/api/mcp (streamable-http)
- Host
- fama.best
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://fama.best/api/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server fama.best, PKCE S256, grants authorization_code, refresh_token.
Scopes read act.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://fama.best
- Registry
- active, updated 2026-11-13 · registry entry
Compare this server with others.
More servers
Servers that mention fama.
- Indonesia Payments (Midtrans Snap — GoPay / QRIS / Alfamart / bank VA) app.wishpool/indonesia-payments-mcp · no DNS
- German Real Estate Depreciation & Restnutzungsdauer immo.rundum/real-estate-appraisal · alive
- ANTT SIFAMA: Segunda Via de Boletos io.github.mcp-dir/antt_sifama_boleto_2via-mcp · alive
- ANTT SIFAMA: Consultar Multas io.github.mcp-dir/antt_sifama_consultar_multas-mcp · alive
- ANTT SIFAMA: Download de Auto de Infração io.github.mcp-dir/antt_sifama_download_auto-mcp · alive
- ANTT SIFAMA: Lista de Autos de Infração io.github.mcp-dir/antt_sifama_lista_autos-mcp · alive
- Eclipse Muzzle io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-muzzle-mcp · not probed
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.