com.opointo/opointo

Est-ce que com.opointo/opointo est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.opointo/opointo » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 11 outils

• add_screen≈ 270 tokens

  Needs a subscription. Adds one screen designed in the Designer to a project. With the project's .opointo/files.json it returns the screen file, the route that mounts it and the one line to register it, and never rewrites existing files. Without it, a self-contained screen file for any Expo app.

  Paramètres, retour & exemple (5)

  Paramètres

  • tab · string · optionnel
    nest it in this tab's stack; omit to place it where the design does
  • appId · string · requis
    the share code from "Send app to agent"
  • screen · string · optionnel
    the new screen's name in that design
  • manifest · object · optionnel
    the parsed .opointo/files.json
  • componentName · string · optionnel
    only to add a second copy of a screen; omit for the export's name

  Exemple d'appel

  {"name": "add_screen", "arguments": {"appId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• check_snippet≈ 163 tokens

  Scans TSX that uses these components for the mistakes that render nothing with no error: animated opacity on glass, the flex: 1 collapse, a clipped lens, a conditionally mounted surface. A read-only text scan, not a guarantee; verify_app checks a whole emitted project.

  Paramètres, retour & exemple (1)

  Paramètres

  • code · string · requis
    the TSX to check

  Exemple d'appel

  {"name": "check_snippet", "arguments": {"code": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• emit_app≈ 278 tokens

  Needs a subscription. Turns a design from the Designer into a working Expo app: navigation, providers, tab bar, screens and the components they use. Returns a recipe for the current project: every file with its target path, one install line and ordered steps with a check each. Pass `step` for one step in full, which does not count against the daily allowance.

  Paramètres, retour & exemple (4)

  Paramètres

  • page · number · optionnel
    for step write or review; each page names the next
  • step · string · optionnel
    a step id from the recipe, or "review" for the screen list
  • appId · string · requis
    the share code from the Designer's "Send app to agent", e.g. "34ca4babb2"
  • override · boolean · optionnel
    emit even with screens flagged not ready; ask the customer first

  Exemple d'appel

  {"name": "emit_app", "arguments": {"appId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_component≈ 175 tokens

  Finds the component for a UI need described in plain words, ranked, and says when this catalog ships nothing on purpose because the phone's own control is the right choice. Omit `need` to list every component with its purpose and whether it renders the real system control.

  Paramètres, retour & exemple (2)

  Paramètres

  • need · string · optionnel
    e.g. "a progress bar for an upload"
  • category · string · optionnel · controls | chrome | surfaces

  Exemple d'appel

  {"name": "find_component", "arguments": {"need": "texte", "category": "controls"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_app_setup≈ 181 tokens

  How an app is set up so these components work and follow its theme, one topic at a time: the app-root providers in the order that works, the theme hooks and token scales, or the rules that hold across the whole catalog. An app built by emit_app already has all three wired.

  Paramètres, retour & exemple (2)

  Paramètres

  • topic · string · requis · providers | theme | rules
  • platform · string · optionnel · ios | android
    rules only

  Exemple d'appel

  {"name": "get_app_setup", "arguments": {"topic": "providers"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_component≈ 178 tokens

  Everything needed to write a correct call site for one component: props with types, defaults and allowed values, what draws on iOS and on Android, the providers it needs at the app root, its dependencies, and the runtime rules that stop it rendering blank.

  Paramètres, retour & exemple (2)

  Paramètres

  • slug · string · requis
    e.g. "button"
  • platform · string · optionnel · ios | android
    only the rules that hold there

  Exemple d'appel

  {"name": "get_component", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• install_component≈ 195 tokens

  Needs a subscription, except for the free foundation components. Adds one component to an existing project: the files it and its dependencies need in install order with exact target paths, the single expo install line, the providers it needs and its runtime rules. A backend recipe's id, such as "supabase", adds that integration: its files and the per-app wiring an export writes.

  Paramètres, retour & exemple (1)

  Paramètres

  • slug · string · requis
    e.g. "button", or a recipe id such as "supabase"

  Exemple d'appel

  {"name": "install_component", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• propose_app≈ 459 tokens

  Your agent can design an app with you: send an app in opointo's design format (the AppSpec emit_app builds from) and get back a link that opens it in the Designer as a new, unsaved design. The person sees every screen, changes what they like, and hands it back for emit_app. into: the code in the person's line; it lands in their open design. dryRun checks without making a link; format: true returns the format and every block, "photos" the sample photos, or with app: { version: 1 } a short plan's.

  Paramètres, retour & exemple (4)

  Paramètres

  • app · object · optionnel
    The design: { name, tabs: [{ screenId, label }], screens: [{ id, name, composition: { screen: { content: { children: [node] }, chrome: { header?, headerItems?, floating: [] }, overlays: [] } } }], onboardingScreenIds: [], pushed: [{ screenId, fromScreenId, presentation }], theme? }. A node is { id, slug, props }: slug is "wireframe:<block>" such as "wireframe:list-row" (a list whose rows open one screen is one row block with repeats: "true" and its sample rows in rows: [{ title, ... }]) or a component from find_component, and a content node opens a screen with navigate: { to, presentation } beside its props. A top bar is header: { id, slug: "header", props: {} }, titled by the screen's name; a sheet has none. entryScreenId is only for a splash screen before the tabs. Titles and composition metadata are set by the builder.
  • into · string · optionnel
  • dryRun · boolean · optionnel
    check the design and report, without making a link
  • format · boolean|string · optionnel

  Exemple d'appel

  {"name": "propose_app", "arguments": {"app": {}, "into": "texte", "dryRun": true, "format": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• propose_screen≈ 269 tokens

  Your agent can design a single screen with you: send one screen in opointo's design format (the Composition add_screen builds from) and get back a link that opens it in the Designer as a new, unsaved design the person can change. into: as propose_app's. dryRun checks without making a link; format: true returns the format. For a whole app, use propose_app.

  Paramètres, retour & exemple (4)

  Paramètres

  • into · string · optionnel
  • dryRun · boolean · optionnel
    check the screen and report, without making a link
  • format · boolean · optionnel
  • composition · object · optionnel
    One screen: { name, screen: { content: { children: [node] }, chrome: { header?, headerItems?, floating: [] }, overlays: [] } }. A node is { id, slug, props }: slug is "wireframe:<block>" or a component from find_component.

  Exemple d'appel

  {"name": "propose_screen", "arguments": {"into": "texte", "dryRun": true, "format": true, "composition": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• update_components≈ 313 tokens

  Needs a subscription. Reads the project's .opointo/files.json and returns only the opointo-supplied files that changed since export, so it works months later with no share code. Never touches the customer's own screens, and flags the rare change that needs a code edit rather than a copy.

  Paramètres, retour & exemple (4)

  Paramètres

  • page · number · optionnel
    only when the answer's page.next asks for it
  • current · array · optionnel
    only when a split-unverified blocker asks: each named file's hash, from its command
  • manifest · object · requis
    the parsed .opointo/files.json (the object or its files array)
  • acceptSplit · array · optionnel
    only once the customer agreed: the paths split-customer-edited blockers name

  Exemple d'appel

  {"name": "update_components", "arguments": {"manifest": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• verify_app≈ 648 tokens

  Needs a subscription. Checks an emitted app before it is built: missing files, altered verbatim files, absent packages, the expo-router config merge, whether the installed Xcode can build it, and whether a change needs a new native build.

  Paramètres, retour & exemple (5)

  Paramètres

  • appId · string · optionnel
    emit_app's share code; `appId` in .opointo/files.json
  • files · array · requis
    each file written, hidden .opointo/files.json included: { path, bytes }, from the project root
  • config · object · optionnel
  • toolchain · object · optionnel
  • dependencies · array · optionnel
    package.json dependencies' keys

  Exemple d'appel

  {"name": "verify_app", "arguments": {"files": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://opointo.com/api/mcp