PRD to Flutter APK
REMOTE · 37-27-249-33.SSLIP.IO · SCANNED AUG 3
Compile a JSON product spec into an Android APK. Paid per build via x402 (USDC on Base).
Available components
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 →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 333 tokens (~66/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% of tool parameters carry a description.Partial
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · 37-27-249-33.sslip.io
claude mcp add --transport http carlosge492-prd-to-flutter-apk https://37-27-249-33.sslip.io/mcp
[mcp_servers.carlosge492-prd-to-flutter-apk] url = "https://37-27-249-33.sslip.io/mcp"
{
"$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
}
}
} openclaw mcp add carlosge492-prd-to-flutter-apk --url https://37-27-249-33.sslip.io/mcp --transport streamable-http
mcp_servers:
carlosge492-prd-to-flutter-apk:
url: "https://37-27-249-33.sslip.io/mcp" {
"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.
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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Aug 26 60
First indexed and scored.
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 3 Aug 2026 · Probed https://37-27-249-33.sslip.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=37-27-249-33.sslip.io | CN=YE1,O=Let's Encrypt,C=US | 30 Jul 2026 | 28 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 550a99b3f446dad3b2e9479ea1e3a75fc38 |
| SANs: 37-27-249-33.sslip.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
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 No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://37-27-249-33.sslip.io/mcp | Verified | 200 | |
| http (plaintext) | http://37-27-249-33.sslip.io/mcp | HTTPS enforced |
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.
build_status ~34
Status, log, diagnostics, settlement transaction and token usage for a build already paid for.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | — |
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.
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.
| Name | Type | Req | Description |
|---|---|---|---|
| prd | object | yes | the PRD; see the prd_schema tool |
| x_payment | string | — | signed 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.
| Name | Type | Req | Description |
|---|---|---|---|
| prd | object | yes | the PRD; see the prd_schema tool |
No output schema declared.
No examples provided.