_ registry / mcp streamable-http · checked 35m ago

opointo

https://opointo.com

Registry code: b86cd59dccb46c12

api record

opointo turns an app designed in its Designer into a real React Native / Expo project, native on both platforms: Liquid Glass on iOS 26, Material 3 Expressive on Android. Free with no account: find_component, get_component, get_app_setup and check_snippet, for using the components without a blank screen, and propose_app and propose_screen, for designing with the person. With a subscription, emit_app, add_screen, install_component, update_components and verify_app write and check the code; a paid call asks the person to sign in, or takes a licence key or agent token as a Bearer header.

endpoint
https://opointo.com/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is opointo live?
Yes — it answered the hub's last check (checked 35m ago). It answered 100% of checks over the last 30 days.
Is opointo free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does opointo have?
11 tools: get_app_setup, get_component, propose_screen, update_components, check_snippet, add_screen, propose_app, find_component, ….
Is opointo safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
1,002ms

last good check

priced tools
0

of 11 tools

_ answered our checks, 90 days 341 checks · signed record
  • degraded → live
_ what it is for
topic
developer tools code & repositories
used for
  • find react native components
  • check tsx snippet for mistakes
  • emit expo app from a design
  • install components into a project
takes → gives
text, code → code
tools
6 reads5 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 11 tools
1 open3 auth-required 7 never probed 4 of 11 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • find_component reads open 3h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "need": {
      "type": "string",
      "description": "e.g. \"a progress bar for an upload\""
    },
    "category": {
      "enum": [
        "controls",
        "chrome",
        "surfaces"
      ],
      "type": "string"
    }
  }
}
    arguments 17 lines
  • install_component changes data auth-required 3h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "e.g. \"button\", or a recipe id such as \"supabase\""
    }
  }
}
    arguments 12 lines
  • verify_app reads auth-required 20h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "files"
  ],
  "properties": {
    "appId": {
      "type": "string",
      "description": "emit_app's share code; `appId` in .opointo/files.json"
    },
    "files": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "path"
        ],
        "properties": {
          "sha": {
            "type": "string",
            "description": "optional; replaces the byte check"
          },
          "path": {
            "type": "string"
          },
          "bytes": {
            "type": "number",
            "description": "bytes on disk as `wc -c` reports, not characters"
          }
        }
      },
      "description": "each file written, hidden .opointo/files.json included: { path, bytes }, from the project root"
    },
    "config": {
      "type": "object",
      "properties": {
        "icon": {
          "type": "string",
          "description": "app.json"
        },
        "main": {
          "type": "string",
          "description": "package.json \"main\""
        },
        "scheme": {
          "type": "string",
          "description": "app.json"
        },
        "plugins": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "app.json"
        },
        "release": {
          "type": "string"
        },
        "sources": {
          "type": "string"
        },
        "moduleSuffixes": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "tsconfig compilerOptions"
        },
        "supportsTablet": {
          "type": "boolean",
          "description": "app.json ios"
        },
        "monochromeImage": {
          "type": "string",
          "description": "app.json android.adaptiveIcon"
        },
        "nativeModulesDir": {
          "type": "string",
          "description": "package.json expo.autolinking; omit if unset"
        },
        "privacyPolicyUrl": {
          "type": "string"
        },
        "userInterfaceStyle": {
          "type": "string",
          "description": "app.json"
        }
      }
    },
    "toolchain": {
      "type": "object",
      "properties": {
        "xcode": {
          "type": "string",
          "description": "`xcodebuild -version`, e.g. \"26.2\"; omit without Xcode"
        },
        "expoSdk": {
          "type": "string",
          "description": "the INSTALLED expo version, e.g. \"56.0.15\" (`npm ls expo`)"
        },
        "nativeFingerprint": {
          "type": "string"
        },
        "enableSceneSupport": {
          "type": "boolean",
          "description": "app.json expo-build-properties ios.enableSceneSupport"
        },
        "expoBuildProperties": {
          "type": "string",
          "description": "INSTALLED expo-build-properties version; omit if absent"
        },
        "lastBuildFingerprint": {
          "type": "string"
        }
      }
    },
    "dependencies": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "package.json dependencies' keys"
    }
  }
}
    arguments 125 lines
  • emit_app changes data auth-required 20h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "appId"
  ],
  "properties": {
    "page": {
      "type": "number",
      "description": "for step write or review; each page names the next"
    },
    "step": {
      "type": "string",
      "description": "a step id from the recipe, or \"review\" for the screen list"
    },
    "appId": {
      "type": "string",
      "description": "the share code from the Designer's \"Send app to agent\", e.g. \"34ca4babb2\""
    },
    "override": {
      "type": "boolean",
      "description": "emit even with screens flagged not ready; ask the customer first"
    }
  }
}
    arguments 24 lines
  • get_app_setup reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "topic"
  ],
  "properties": {
    "topic": {
      "enum": [
        "providers",
        "theme",
        "rules"
      ],
      "type": "string"
    },
    "platform": {
      "enum": [
        "ios",
        "android"
      ],
      "type": "string",
      "description": "rules only"
    }
  }
}
    arguments 24 lines
  • get_component reads unknown 3h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "e.g. \"button\""
    },
    "platform": {
      "enum": [
        "ios",
        "android"
      ],
      "type": "string",
      "description": "only the rules that hold there"
    }
  }
}
    arguments 20 lines
  • propose_screen changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "into": {
      "type": "string"
    },
    "dryRun": {
      "type": "boolean",
      "description": "check the screen and report, without making a link"
    },
    "format": {
      "type": "boolean"
    },
    "composition": {
      "type": "object",
      "description": "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."
    }
  }
}
    arguments 19 lines
  • update_components reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "manifest"
  ],
  "properties": {
    "page": {
      "type": "number",
      "description": "only when the answer's page.next asks for it"
    },
    "current": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "path"
        ],
        "properties": {
          "sha": {
            "type": "string"
          },
          "path": {
            "type": "string"
          },
          "missing": {
            "type": "boolean"
          }
        }
      },
      "description": "only when a split-unverified blocker asks: each named file's hash, from its command"
    },
    "manifest": {
      "type": "object",
      "description": "the parsed .opointo/files.json (the object or its files array)"
    },
    "acceptSplit": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "only once the customer agreed: the paths split-customer-edited blockers name"
    }
  }
}
    arguments 44 lines
  • check_snippet reads unknown 20h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "the TSX to check"
    }
  }
}
    arguments 12 lines
  • add_screen changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "appId"
  ],
  "properties": {
    "tab": {
      "type": "string",
      "description": "nest it in this tab's stack; omit to place it where the design does"
    },
    "appId": {
      "type": "string",
      "description": "the share code from \"Send app to agent\""
    },
    "screen": {
      "type": "string",
      "description": "the new screen's name in that design"
    },
    "manifest": {
      "type": "object",
      "description": "the parsed .opointo/files.json"
    },
    "componentName": {
      "type": "string",
      "description": "only to add a second copy of a screen; omit for the export's name"
    }
  }
}
    arguments 28 lines
  • propose_app changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "app": {
      "type": "object",
      "description": "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": {
      "type": "string"
    },
    "dryRun": {
      "type": "boolean",
      "description": "check the design and report, without making a link"
    },
    "format": {
      "type": [
        "boolean",
        "string"
      ]
    }
  }
}
    arguments 22 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id b86cd59dccb46c12.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b86cd59dccb46c12/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/b86cd59dccb46c12/badge.svg)](https://brick.blue/agent/b86cd59dccb46c12?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.