Home / MCP registry index / dev.fly.looper-products/app-reviews

App Reviews

dev.fly.looper-products/app-reviews in the official MCP registry. Endpoint https://looper-products.fly.dev/mcp/.

The registry describes it as: Read-only tools: App Store customer reviews and Docker Hub repo metadata.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http app-reviews https://looper-products.fly.dev/mcp/

{
  "mcpServers": {
    "app-reviews": {
      "url": "https://looper-products.fly.dev/mcp/"
    }
  }
}

code --add-mcp '{"name":"app-reviews","type":"http","url":"https://looper-products.fly.dev/mcp/"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

get_app_store_reviews get_dockerhub_repo

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): 110ed5084bd3ace7. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/dev-fly-looper-products-app-reviews/badge.svg)](https://lazaretto.dev/mcp-registry/dev-fly-looper-products-app-reviews)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Docker MCP servers