com.ainetcafe/netcafe-build
REMOTE · AINETCAFE.COM · SCANNED AUG 16
Deploy a live web app from one sentence. build_app + poll to a public HTTPS URL you own.
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1050 tokens (~150/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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 · ainetcafe.com
claude mcp add --transport http com-ainetcafe-netcafe-build https://ainetcafe.com/mcp/build?s=registry
[mcp_servers.com-ainetcafe-netcafe-build] url = "https://ainetcafe.com/mcp/build?s=registry"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-ainetcafe-netcafe-build": {
"type": "remote",
"url": "https://ainetcafe.com/mcp/build?s=registry",
"enabled": true
}
}
} openclaw mcp add com-ainetcafe-netcafe-build --url https://ainetcafe.com/mcp/build?s=registry --transport streamable-http
mcp_servers:
com-ainetcafe-netcafe-build:
url: "https://ainetcafe.com/mcp/build?s=registry" {
"mcpServers": {
"com-ainetcafe-netcafe-build": {
"type": "http",
"url": "https://ainetcafe.com/mcp/build?s=registry"
}
}
} 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.
- 16 Aug 26 +19
- Authorization: unverified → partial ▲ security
- Schema quality: unverified → fail ▼ functional
- Schema quality: pass → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: good → excellent functional
- Stability: fail → 0.10 functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 15 Aug 26 −15
- Authorization: partial → unverified ▼ security
- Stability: 0.03 → fail ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: fail → unverified ▼ functional
- MCP protocol: fail → pass ▲ functional
- Schema quality: fail → pass ▲ functional
- Schema quality: excellent → good functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 14 Aug 26 +10
- Transport: fail → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- 13 Aug 26 58
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 16 Aug 2026 · Probed https://ainetcafe.com/mcp/build?s=registry
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ainetcafe.com | CN=WE1,O=Google Trust Services,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | dac48256f0fdbd780ea13de50d28b439 |
| SANs: ainetcafe.com, *.ainetcafe.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of ainetcafe.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ainetcafe.com. | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ainetcafe.com/mcp/build?s=registry | Verified | 200 | |
| http (plaintext) | http://ainetcafe.com/mcp/build?s=registry | HTTPS enforced | 301 | https://ainetcafe.com/mcp/build?s=registry |
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_app Build and deploy a web app from a description ~208
Turn one plain-language description into a LIVE single-page web tool: code is generated, deployed to managed hosting with HTTPS, and listed — you get the public URL in ~1-2 minutes. Best for tool-style apps: calculators, converters, checklists, timers, generators, small games. Async — poll with check_job. Example — tools/call build_app {"description":"a tip calculator web app"} → poll check_job
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | What the tool should do, in any language. Be specific about inputs/outputs. |
| name | string | – | Optional short app name (defaults to the description). |
| refine | string | – | Slug of an app you built earlier (e.g. "u-1a23e679") to modify instead of building from scratch — describe only the change in `description`. |
| visibility | string | – | "public" (default, listed in the store) or "unlisted" (URL-only, not in the store). |
Structured output declared, but exposes no named fields.
No examples provided.
check_job Check a long-running job ~108
Get the status or result of a job started by deep_research, translate_pdf, or make_slides. Poll every 15-30 seconds until status is "done" or "error". While work is pending, follow retry_after_seconds and next_action; when complete, prefer structured_result when present. Example — GET https://ainetcafe.com/t/check_job?job_id=<id-from-a-job-tool>
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job_id returned when the task was started. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | – |
| is_terminal | boolean | – | – |
| job_id | string | yes | – |
| kind | string | – | – |
| next_action | object|null | – | – |
| result | – | – | – |
| retry_after_seconds | integer | – | – |
| status | string | yes | – |
| structured_result | – | – | – |
No examples provided.
get_app Get details of one application ~75
Full details of one hosted application: what it does, how to use it, measured benchmark scores, source repository, and the URL a human can open to run it. Example — GET https://ainetcafe.com/t/get_app?slug=<slug-from-list_apps>
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Application slug, from list_apps. |
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| open_url | string | – | – |
| slug | string | yes | – |
No examples provided.
list_apps List hosted open-source AI applications ~155
List the open-source AI applications hosted and ready to run at AI NetCafé (ainetcafe.com). Each one normally requires local setup (Docker/Python + your own model API key); here they run pre-configured. Use this to find a tool for a task like translating a PDF with formulas intact, generating a PowerPoint file, polishing an academic paper, or running an autonomous research report. Do not call this first when the request already clearly matches compare_models, translate_pdf, deep_research, or make_slides; call that task tool directly. Example — GET https://ainetcafe.com/t/list_apps
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional filter, e.g. "office", "research", "chat". |
| Name | Type | Req | Description |
|---|---|---|---|
| apps | array | yes | – |
| try_in_browser | string | – | – |
No examples provided.
project_status Check a submitted or hosted project ~86
Check where a repository stands on AI NetCafé: live (with its public page and app URL), in the deployment pipeline, rejected (with the reason), or unknown. Use after submit_project. Example — GET https://ainetcafe.com/t/project_status?repo=<owner/name>
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | GitHub repository owner/name, full URL, or the listed slug. |
Structured output declared, but exposes no named fields.
No examples provided.
submit_project Publish an app to AI NetCafé hosting ~202
Submit a GitHub repository (a web app, typically AI-built) to the AI NetCafé hosting platform. The automated pipeline reviews it, containerizes it, deploys it on a dedicated subdomain with HTTPS and a pre-wired multi-LLM gateway, lists it in the store for humans, and exposes it to AI agents. Every use is metered and the author accrues a revenue share. Use this when a user says "deploy my project", "publish my app somewhere", or "I built something with AI, where can people use it?". Free to submit. Example — tools/call submit_project {"repo":"owner/name"}
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | – | Optional contact (email / X / GitHub handle) for listing and revenue notifications. |
| note | string | – | Optional one-liner: who is it for, what does it solve. |
| repo | string | yes | GitHub repository as owner/name (or full github.com URL). |
Structured output declared, but exposes no named fields.
No examples provided.
what_can_you_do Find the right tool for a task ~162
Describe a task in plain language (any language) and get back exactly which tools on this server do it, with ready-to-run example calls — instead of reading a catalogue of 89 tools and guessing. Also returns multi-step recipes when a task needs several tools chained (invoices to a ledger, a bank statement reconciled, a messy CSV turned into a deliverable). Deterministic and free: it calls no model, costs nothing, and never runs out of quota. Call this FIRST when you are not sure what this server offers.
| Name | Type | Req | Description |
|---|---|---|---|
| task | string | yes | What you are trying to do, e.g. "reconcile a bank statement against my books" or "把一堆发票整理成能入账的表格" |
Structured output declared, but exposes no named fields.
No examples provided.