Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PRD to Flutter APK

REMOTE · 37-27-249-33.SSLIP.IO · SCANNED AUG 23

Generate a Flutter app from a JSON spec free; pay only for the compiled APK (USDC on Base).

−54 this week 0 Trust /100

Deprecated

This server is marked deprecated in the MCP registry.

Dead

Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security0
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety

Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.

Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 4 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the PRD to Flutter APK MCP server?

PRD to Flutter APK is a hosted endpoint at https://37-27-249-33.sslip.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · 37-27-249-33.sslip.io

# add to Claude Code
claude mcp add --transport http carlosge492-prd-to-flutter-apk 'https://37-27-249-33.sslip.io/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "carlosge492-prd-to-flutter-apk": {
      "url": "https://37-27-249-33.sslip.io/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "carlosge492-prd-to-flutter-apk": {
      "type": "http",
      "url": "https://37-27-249-33.sslip.io/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.carlosge492-prd-to-flutter-apk]
url = "https://37-27-249-33.sslip.io/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "carlosge492-prd-to-flutter-apk": {
      "type": "remote",
      "url": "https://37-27-249-33.sslip.io/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add carlosge492-prd-to-flutter-apk --url 'https://37-27-249-33.sslip.io/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  carlosge492-prd-to-flutter-apk:
    url: "https://37-27-249-33.sslip.io/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "carlosge492-prd-to-flutter-apk": {
      "Transport": "http",
      "Url": "https://37-27-249-33.sslip.io/mcp"
    }
  }
}
# add to Vellum
assistant mcp add carlosge492-prd-to-flutter-apk -t streamable-http -u 'https://37-27-249-33.sslip.io/mcp'
// mcp.json
{
  "mcpServers": {
    "carlosge492-prd-to-flutter-apk": {
      "type": "http",
      "url": "https://37-27-249-33.sslip.io/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 23 Aug 26 −13

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 19 Aug 26 −14

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 18 Aug 26 −13

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 17 Aug 26 −14

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 16 Aug 26 −13
    • HTTPS: pass → unverified security
  • 12 Aug 26 0
    • Endpoint reachability: reachable → unreachable security
    • Stability: 0.33 → unverified security
    • TLS certificate: pass → unverified security
    • HSTS header: pass → unverified security
    • Transport: pass → fail security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: fail → unverified functional
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 11 Aug 26 +2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 10 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 23 Aug 2026 · Probed https://37-27-249-33.sslip.io/mcp

TLS unreached
DNSSEC insecure

Validation of 37-27-249-33.sslip.io. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
sslip.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://37-27-249-33.sslip.io/mcp Unreachable
http (plaintext) http://37-27-249-33.sslip.io/mcp Inconclusive 404
MCP tools · 7 exposed · ~480 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
build_files ~34

The generated source for a build or preview, as a map of path to file contents.

NameTypeReqDescription
job_idstringyes

No output schema declared.

No examples provided.

build_status ~34

Status, log, diagnostics, settlement transaction and token usage for a build already paid for.

NameTypeReqDescription
job_idstringyes

No output schema declared.

No examples provided.

payment_terms ~39

What a build costs and how to pay: price, token contract, chain and the EIP-712 domain, as an x402 challenge. Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

prd_schema ~28

The JSON Schema a product requirements document must satisfy. Generate against this rather than guessing field names.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

preview_build ~113

Generate a real app from a PRD for FREE and read the source it produces — same generator, same repair loop, same static analysis as a paid build. It is not packaged into an APK; that is what payment buys. Returns a job id: poll it with build_status, then read the code with build_files. Takes about 5 minutes. Heavily rate limited, because each run costs the operator real model tokens.

NameTypeReqDescription
prdobjectyesthe PRD; see the prd_schema tool

No output schema declared.

No examples provided.

start_build ~154

Buy a build. Call once without `x_payment` to get the x402 payment requirements, sign an EIP-3009 authorization over them, then call again passing the signed authorization as `x_payment`. Returns a job id; poll it with build_status until apk_available is true, then download the APK from apk_url. A build takes about 5-8 minutes, so poll rather than blocking. Payment settles on-chain before the build starts, and a failed build still returns its diagnostics.

NameTypeReqDescription
prdobjectyesthe PRD; see the prd_schema tool
x_paymentstringsigned x402 payment authorization (the value of the X-Payment header). Omit to be quoted.

No output schema declared.

No examples provided.

validate_prd ~78

Check a product requirements document and report exactly what would be built — screens, models, navigation, auth — without building it. Free, no payment required. Uses the same validator as the paid build, so anything accepted here will not be rejected after payment.

NameTypeReqDescription
prdobjectyesthe PRD; see the prd_schema tool

No output schema declared.

No examples provided.

Common questions

What is the PRD to Flutter APK MCP server?

PRD to Flutter APK is an MCP server listed in the public MCP registry as io.github.carlosge492/prd-to-flutter-apk. Generate a Flutter app from a JSON spec free; pay only for the compiled APK (USDC on Base). This page covers its hosted endpoint (https://37-27-249-33.sslip.io/mcp).

Is the PRD to Flutter APK MCP server safe to use?

PRD to Flutter APK scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the PRD to Flutter APK MCP server expose?

PRD to Flutter APK exposes 7 tools: validate_prd, prd_schema, payment_terms, build_status, preview_build, and 2 more. Their descriptions and schemas cost roughly 480 tokens of context every time the server is loaded.

Does the PRD to Flutter APK MCP server require authentication?

Its publisher declares no required credentials for PRD to Flutter APK. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the PRD to Flutter APK MCP server still maintained?

PRD to Flutter APK is marked deprecated in the MCP registry. We last reached this channel on 11 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.