llms.txt
# Mobbin
> Mobbin is a searchable design-reference library of real mobile apps, web apps, and websites. Use it to find and compare individual screens, multi-step product flows, UI patterns, and website sections from shipped digital products.
## When to use Mobbin
Use Mobbin when an agent needs to:
- Find real examples of screens, UI patterns, product flows, or website sections.
- Compare how shipped products solve the same design problem.
- Ground an interface critique or design recommendation in visual references.
Use `search_screens` for individual interface states, `search_flows` for ordered journeys, and `search_sections` for website composition. Prefer Mobbin MCP for screen, flow, and section searches; use the REST API for repeatable programmatic screen searches.
Compare several relevant products, preserve the product name and Mobbin URL, and separate visible observations from recommendations.
## Important limitations
- A Mobbin example shows that a product used a design; it does not prove that the design improved conversion or another metric.
- A recurring pattern is a convention, not automatically a best practice.
- Check capture metadata when recency matters.
- Do not copy protected designs, branding, text, or assets verbatim.
- Evaluate accessibility and suitability for the intended audience separately.
## Programmatic access
- Mobbin MCP uses Streamable HTTP and OAuth. It is available on Pro, Team, and Enterprise plans.
- MCP tools are `search_screens`, `search_flows`, and `search_sections`; the current tool set is read-only.
- The REST API uses workspace bearer keys and is available on Team and Enterprise plans.
- MCP and API requests are limited to 60 requests per 60 seconds. Respect `Retry-After` after an HTTP 429 response.
## Start here
- [Product overview](https://mobbin.com/index.md): What Mobbin contains, who it serves, and the available access methods.
- [Pricing and plan access](https://mobbin.com/pricing.md): Current prices, billing terms, plan limits, MCP eligibility, and API eligibility.
- [Mobbin MCP](https://mobbin.com/mcp.md): Agent tools, authentication, setup, rate limits, usage guidance, and examples.
- [Complete agent context](https://mobbin.com/llms-full.txt): Consolidated product, access, workflow, pricing, and catalog context.
## Product and support
- [Explore Mobbin](https://mobbin.com/explore): Browse design references by platform, product, category, flow, screen pattern, and UI element.
- [Human-facing MCP page](https://mobbin.com/mcp): Product explanation, examples, setup overview, and frequently asked questions.
- [Mobbin documentation](https://docs.mobbin.com/overview): MCP and REST API documentation.
- [OpenAPI specification](https://docs.mobbin.com/openapi.json): Machine-readable REST API description.
- [Support](https://help.mobbin.com/en/contact-us): Contact Mobbin support.
Last reviewed: 2026-09-22.
security.txt
Contact: mailto:security@mobbin.com
Acknowledgments: https://mobbin.com/security/hall-of-fame.txt
Preferred-Languages: en
Canonical: https://mobbin.com/.well-known/security.txt
# Vulnerability Disclosure Program
At Mobbin, we consider the security of our systems a top priority. But no matter how much effort we put into system security, there can still be vulnerabilities present.
If you discover a vulnerability, we would like to know about it so we can take steps to address it as quickly as possible. We would like to ask you to help us better protect our clients and our systems.
## Out of scope vulnerabilities
- Clickjacking on pages with no sensitive actions.
- Unauthenticated/logout/login CSRF.
- Attacks requiring MITM or physical access to a user's device.
- Any activity that could lead to the disruption of our service (DoS).
- Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS.
- Email spoofing.
- Missing DNSSEC, CAA, CSP headers.
- Lack of Secure or HTTP only flag on non-sensitive cookies.
- Deadlinks.
## Please do the following
- E-mail your findings to security@mobbin.com in the following format
- Subject: [CVSS Score]: [Vulnerability]
- Body:
- CVSS Scoring
- Vulnerability Description
- Reproduction Steps
- Do not run automated scanners on our infrastructure or dashboard. If you wish to do this, contact us and we will set up a sandbox for you.
- Do not take advantage of the vulnerability or problem you have discovered, for example by downloading more data than necessary to demonstrate the vulnerability or deleting or modifying other people's data.
- Do not reveal the problem to others until it has been resolved.
- Do not use attacks on physical security, social engineering, distributed denial of service, spam or applications of third parties.
- Do provide sufficient information to reproduce the problem, so we will be able to resolve it as quickly as possible. Usually, the IP address or the URL of the affected system and a description of the vulnerability will be sufficient, but complex vulnerabilities may require further explanation.
## Disclosure guidelines
- In order to protect our customers, do not reveal the problem to others until we have researched, addressed and informed our affected customers.
- If you want to publicly share your research about Mobbin at a conference, in a blog or any other public forum, you should share a draft with us for review and approval at least 90 days prior to the publication date. Please note that the following should not be included:
- Data regarding any Mobbin customer projects
- Mobbin customers' data
- information about Mobbin employees, contractors or partners
- We may take some time to get back to you. Please be patient with us.
- Mobbin reserves the right to update the terms of this program without notice.
## What we promise
- We will respond to your report as soon as we can.
- If you have followed the instructions above, we will not take any legal action against you in regard to the report.
- If your disclosure is sufficiently significant and if you have been cordial throughout the exchange, you will be given a reward payout if the disclosure was not previously known. Making demands or being rude may disqualify you from your reward.
- We will handle your report with strict confidentiality, and not pass on your personal details to third parties without your permission.
- We will keep you informed of the progress towards resolving the problem.
- In the public information concerning the problem reported, we will give your name as the discoverer of the problem (unless you desire otherwise).
We strive to resolve all problems as quickly as possible, and we would like to play an active role in the ultimate publication on the problem after it is resolved.
