MCP server that diagnoses Flutter + Stripe (flutter_stripe) Android and iOS setup issues
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"flutter-stripe-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# flutter-stripe-mcp An MCP server that diagnoses Flutter + Stripe ([flutter_stripe](https://pub.dev/packages/flutter_stripe)) setup issues — so Claude can check your project automatically. ## What it does Three tools: one diagnoses your local project setup, and two search GitHub for known issues and their fixes. `diagnose_setup` takes the path to your Flutter project root and runs every check: | Check | Requirement | |-------|-------------| | `kotlin` | Kotlin version >= 1.9.0 (read from `android/settings.gradle` or legacy `android/build.gradle`) | | `gradle_wrapper` | Gradle wrapper >= 8.0 | | `android_themes` | Theme styles derive from `Theme.AppCompat.*`, `Theme.MaterialComponents.*`, or `Theme.Material3.*` | | `main_activity` | `MainActivity` extends `FlutterFragmentActivity` (not `FlutterActivity`) | | `proguard_rules` | `proguard-rules.pro` contains all required Stripe rules | | `ios_deployment_target` | iOS deployment target >= 13.0 (from `Podfile` or `project.pbxproj`) | | `ios_camera_permission` | `NSCameraUsageDescription` set in `Info.plist` (suggestion — needed for card scanning) | The result lists passing checks by name and returns a `fix` instruction for each problem found. Platforms without an `android/` or `ios/` directory are skipped. ### Checking for known issues Two more tools let Claude check whether a problem is already a documented issue in the [flutter_stripe GitHub repo](https://github.com/flutter-stripe/flutter_stripe), and read the fix straight from the discussion: | Tool | Purpose | |------|---------| | `search_flutter_stripe_issues(query, state="all", limit=10)` | Search issues by keywords (e.g. an error message); returns titles, state, and short excerpts. | | `get_flutter_stripe_issue(issue_number)` | Fetch one issue's full body and all comments, to find the actual fix. | These use GitHub's public search API, which is limited to 60 requests/hour unauthenticated. If you hit the rate limit, the tool returns a clear error instea…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.