MCP server
AI assistants can use the App Supply Index directly through the Model Context Protocol. Ask "how do I fix my app's app-ads.txt?" and the assistant reads the same grade, fix plan and findings you see on the app's page. Free, no sign-in.
Connect
- Server URL
- https://api.appsupplyindex.com/mcp
- Transport
- Streamable HTTP, no authentication
Claude Code:
claude mcp add --transport http app-supply-index https://api.appsupplyindex.com/mcp
Claude (web and desktop): Settings → Connectors → Add custom connector, and paste the server URL. Other clients that support remote MCP servers take the same URL. In a JSON config:
{
"mcpServers": {
"app-supply-index": { "type": "http", "url": "https://api.appsupplyindex.com/mcp" }
}
}
Tools
- find_apps
- Search the weekly index by app name, developer, bundle ID or package.
- get_app
- An app's grade, one-line verdict, fix plan with points per step, and every finding with how to fix it. Takes a store link, an iOS ID or an Android package.
- check_app
- A live check of any app, the same as the web checker. Use it right after you change your file.
- get_ad_system
- An ad system across the index: developers that list it, lines checked, seller IDs its sellers.json doesn't list, and whether that file could be read.
All tools are read-only. Answers carry the same note as the site: findings are automated observations of public files and describe file contents, not the intent or conduct of any company.
Limits
Live checks share the web checker's limit (20 per hour per address) and its 10-minute cache. Index lookups allow 600 per hour per address. We log which apps are checked, not who asked.
Prefer files? The same data is open under CC BY 4.0: see open data, the HTTP API and llms.txt.