opointo MCP server
com.opointo/opointoopointo.comstreamable-httpv0.4.0Scanned
Design an app in a browser, get an Expo project you own, iOS and Android. Free lookups, paid build.
11 tools: 8 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 4 findings
Tools listed without sign-in. Remote posture
With Anlyon
8 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the opointo MCP server can do
The opointo MCP server is published by opointo.com, a domain the MCP Registry verified. It has 11 tools. It can create or change data (8 tools: propose_app, propose_screen, emit_app, add_screen and 4 more), but cannot delete data. 3 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 4 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.
Last scanned Nov 21, 2026, version 0.4.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
11 tools
Changes things 8Claude Code: ask
add_screenNeeds a subscription.1 finding
Why it is in this group
- The name "add_screen" says "add": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "add_screen" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "add_screen" says "add": a word for a change.
Description, as the server wrote it Needs a subscription. Adds one screen designed in the Architect to a React Native / Expo app. 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.
Annotations the server declares
- title: Add a screen to an app
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
check_snippetScans React Native TSX that uses these components for the mistakes that render a blank screen with no error: animated opacity on glass, the flex: 1 collapse, a clipped lens, a cond…1 finding
Why it is in this group
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "check_snippet" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.
Description, as the server wrote it Scans React Native TSX that uses these components for the mistakes that render a blank screen 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.
Annotations the server declares
- title: Check code for blank-render bugs
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
emit_appNeeds a subscription.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Needs a subscription. Generates the code of a working Expo / React Native app from a design in the Architect: 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.
Annotations the server declares
- title: Build an app from a design
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
install_componentNeeds a subscription, except for the free foundation components.1 finding
Why it is in this group
- The name "install_component" says "install": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "install_component" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "install_component" says "install": a word for a change.
Description, as the server wrote it Needs a subscription, except for the free foundation components. Adds one React Native component to an existing Expo 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.
Annotations the server declares
- title: Install a component
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
propose_appDesigns a mobile app for iOS and Android with the person, the free step before a build.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Designs a mobile app for iOS and Android with the person, the free step before a build. Send one sentence as idea to create a new app, or a short plan or a full design as app, and get back a link that opens it in the Architect as a new, unsaved design: the person sees every screen, changes it and hands it back for emit_app. The link and its code last 7 days. format: true returns the format; dryRun checks without making a link; into sends it to the design the person has open.
Annotations the server declares
- title: Propose an app design
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
propose_screenDesigns a single screen of a mobile app with the person: send one screen in the design format add_screen builds from and get back a link that opens it in the Architect for the pers…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Designs a single screen of a mobile app with the person: send one screen in the design format add_screen builds from and get back a link that opens it in the Architect for the person to change. The link and its code last 7 days. dryRun checks without making a link; format: true returns the format. A whole app is propose_app's.
Annotations the server declares
- title: Propose a screen design
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
update_componentsNeeds a subscription.1 finding
Why it is in this group
- The name "update_components" says "update": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "update_components" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "update_components" says "update": a word for a change.
Description, as the server wrote it Needs a subscription. Updates the React Native components opointo supplied: from the project's .opointo/files.json it returns only the 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.
Annotations the server declares
- title: Update supplied components
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
verify_appNeeds a subscription.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Needs a subscription. Checks an emitted Expo app before a build: missing files, altered verbatim files, absent packages, expo-router's config merge, whether installed Xcode can build it, and whether a change needs a native rebuild.
Annotations the server declares
- title: Verify an emitted app
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 3Show 3 read-only tools
find_componentFinds the React Native / Expo component for a mobile app's need in plain words, such as a button, a tab bar or a bottom sheet: Liquid Glass on iOS 26, Material 3 Expressive on Andr…No findings
Why it is in this group
- The name "find_component" says "find": a word for reading.
Description, as the server wrote it Finds the React Native / Expo component for a mobile app's need in plain words, such as a button, a tab bar or a bottom sheet: Liquid Glass on iOS 26, Material 3 Expressive on Android. 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 and its purpose.
Annotations the server declares
- title: Find a component
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_app_setupHow a React Native / Expo 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 toke…No findings
Why it is in this group
- The name "get_app_setup" says "get": a word for reading.
Description, as the server wrote it How a React Native / Expo 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, the rules that hold across the whole catalog, or propose_app's two formats, plan and design. An app built by emit_app has the first three wired.
Annotations the server declares
- title: Get the app setup
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_componentEverything needed to write a correct React Native call site for one component: props with types, defaults and allowed values, a minimal example call, what draws on iOS and on Andro…No findings
Why it is in this group
- The name "get_component" says "get": a word for reading.
Description, as the server wrote it Everything needed to write a correct React Native call site for one component: props with types, defaults and allowed values, a minimal example call, 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.
Annotations the server declares
- title: Get a component
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:44 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 8
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://opointo.com/.well-known/oauth-protected-resource/api/mcp
- Authorization servers
- https://opointo.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 8 tools that change things (8 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://opointo.com/api/mcp: tools/list returned 11 tools to an anonymous client, including check_snippet (write), emit_app (write), add_screen (write), install_component (write), update_components (write) and 3 more
Findings
Matches of fixed checks, with the text they matched.
- Warnadd_screen
The server marks "add_screen" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "add_screen" says "add": a word for a change.
The server marks "update_components" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "update_components" says "update": a word for a change.
The server marks "install_component" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "install_component" says "install": a word for a change.
- Warncheck_snippet
The server marks "check_snippet" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools11 changed.~11 changedView diff
- Changed:add_screenChanges thingsdescription
- Changed:check_snippetChanges thingsdescription
- Changed:emit_appChanges thingsdescription
- Changed:find_componentOnly readsdescription
- Changed:get_app_setupOnly readsdescriptioninputSchema
- Changed:get_componentOnly readsdescription
- Changed:install_componentChanges thingsdescription
- Changed:propose_appChanges thingsdescriptioninputSchema
- Changed:propose_screenChanges thingsdescriptioninputSchema
- Changed:update_componentsChanges thingsdescription
- Changed:verify_appChanges thingsdescriptioninputSchema
Tools1 changed.~1 changedView diff
- Changed:verify_appChanges thingsdescriptioninputSchema
Tools5 changed.~5 changedView diff
- Changed:add_screenChanges thingsdescription
- Changed:emit_appChanges thingsdescriptioninputSchema
- Changed:propose_appChanges thingsdescription
- Changed:propose_screenChanges thingsdescription
- Changed:verify_appChanges thingsinputSchema
Install
Pinned to version 0.4.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http opointo https://opointo.com/api/mcpclaude mcp add --transport http opointo https://opointo.com/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__opointo__find_component",
"mcp__opointo__get_component",
"mcp__opointo__get_app_setup"
],
"ask": [
"mcp__opointo__propose_app",
"mcp__opointo__propose_screen",
"mcp__opointo__emit_app",
"mcp__opointo__add_screen",
"mcp__opointo__verify_app",
"mcp__opointo__update_components",
"mcp__opointo__install_component",
"mcp__opointo__check_snippet"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as opointo. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.opointo/opointo/verify?hash=502898d6a7fcd6c51c996fe4c9be602c801ef17056a49b00766c0425793c5a01" | jq -e '.changed == false'Pinned hash 502898d6a7fc, from Nov 21, 2026, 11:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.opointo/opointo/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.opointo/opointo)Source: MCP Registry · repository. Synced Nov 21, 2026, 11:17 UTC.
opointo MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the opointo MCP server safe?
- No scan can promise that. What its definitions show: 11 tools, 8 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the opointo MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the opointo MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the opointo MCP server have?
- 11 tools: 8 write, 3 read. propose_app, propose_screen, emit_app, add_screen, verify_app, update_components, install_component, check_snippet and 3 more.
Does the opointo MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the opointo MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the opointo MCP server changed its tools?
- Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.