# SkinKnowledgeBase.com
> Educational dermatology reference grounded in peer-reviewed and clinical sources. Cosmetic-appearance-focused entity pages organized by Question, Concern, Ingredient, Product, Side Effect, and Source — built for both human readers and AI clients via parallel rendered web + MCP server.
## Primary entity types
- [Questions](https://skinknowledgebase.com/questions/) — answers to common skincare questions, with cited sources and ranked products
- [Concerns](https://skinknowledgebase.com/concerns/) — skin concerns and cosmetic appearance issues, with helpful ingredients and addressing products
- [Ingredients](https://skinknowledgebase.com/ingredients/) — cosmetic ingredients with mechanism, sourcing, and INCI name
- [Products](https://skinknowledgebase.com/products/) — specific product pages with structured facts (brand, line, cost, key ingredients, addressed concerns)
- [Side Effects](https://skinknowledgebase.com/side-effects/) — known cosmetic side effects with implicating ingredients
- [Sources](https://skinknowledgebase.com/sources/) — cited reference papers, dermatology institution pages, and product information
## Alternate page formats
Every public entity page (Question, Concern, Ingredient, Product, Side Effect, Source) exposes machine-readable alternates at the canonical URL plus a `/raw.md` or `/raw.json` suffix.
- Markdown alternates return `Content-Type: text/markdown; charset=utf-8` and are useful for clean ingestion without HTML chrome. Example: https://skinknowledgebase.com/questions/how-do-i-get-rid-of-blackheads-on-my-nose/raw.md
- JSON alternates return `Content-Type: application/json; charset=utf-8` and are useful for structured ingestion. They expose the same canonical envelope used by the MCP `fetch` tool's `structured` field. Example: https://skinknowledgebase.com/questions/how-do-i-get-rid-of-blackheads-on-my-nose/raw.json
- Discovery is available through HTML page `` link tags: `` and ``. Raw alternates are also enumerated as separate URLs in the per-type sitemaps.
## AI access
- **MCP server**: `https://mcp.skinknowledgebase.com/mcp` (JSON-RPC over HTTP POST to `/mcp` via Streamable HTTP transport)
- **Available tools**: `search`, `fetch`, `get_entity`, `get_question_bundle`, `get_ranked_products_for_question`, `get_sources_for_question`, `search_questions`, `search_entities`, `list_entities`
- **Search quality**: natural-language tolerance built in (normalization, synonym expansion, FTS fallback, per-Question search aliases). Loose queries such as "minimize pores" or "vitamin c worth it" reliably hit the intended Question. See https://skinknowledgebase.com/developers for ranking detail and tool schemas.
- **Full content** (Markdown): https://skinknowledgebase.com/llms-full.txt
- **Sitemap**: https://skinknowledgebase.com/sitemap.xml
- **RSS feed**: https://skinknowledgebase.com/feed.xml
## Content discipline
- All claims are cosmetic-appearance only — no medical claims
- Every entity carries cited Sources with verified URLs (HTTP 200 + title-on-page validated)
- Updated continuously as new bundles publish through the editorial chain (Quill → Inky → Hawk → Press)
## Editorial scope
Content covers: cosmetic skincare ingredients (peptides, retinoids, AHAs, vitamins, etc.), skin concerns (wrinkles, acne, redness, puffiness, etc.), product-fact catalog pages, and dermatology-grounded source citations. Not a medical advice site. Defers to clinicians for medical concerns.