WebAnatomy

Name: WebAnatomy
Author: GabrielAmz

by GabrielAmzversion 0.1.1i★ –iRuns in the cloud

Registry nameai.webanatomy/webanatomy

Install

Overview

Description from the maker (original English)

Help your AI improve landing pages, grounded in 3,500+ scored sections and 500 real pages.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Other
You need to fill in: Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Run this in your terminal

claude mcp add --transport http webanatomy https://mcp.webanatomy.ai/mcp --header 'Authorization: your-value'

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "webanatomy": {
      "url": "https://mcp.webanatomy.ai/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "webanatomy": {
      "type": "http",
      "url": "https://mcp.webanatomy.ai/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

Authorization secret required HTTP header
Bearer token from the WebAnatomy dashboard. WebAnatomy is in private beta: request access and generate a free token at https://www.webanatomy.ai/dashboard/mcp, then send it as 'Bearer '.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain webanatomy.ai (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 32455 servers in this category
Published to the registry more recently than 13% of the other 32455 servers in this category
Basic checks equal to or better than 100% of the other 32455 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is WebAnatomy safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: Authorization

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 5 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, SSTracker free youth training

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

SSTracker free youth training

by sstracker.app

Free youth sports drills, practice plans and age-group answers for parents and coaches.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Web Anatomy

Skills for your AI agent that ship landing pages that work. Built from the plays the best SaaS companies actually shipped, grounded in a scored benchmark library so every recommendation cites a real page instead of generic advice.

$ npx skills add GabrielAmz/web-anatomy

Installs the Web Anatomy skill pack for Claude Code, OpenAI Codex, Cursor, Windsurf, and any agent that supports the Agent Skills spec.

What Web Anatomy is

Most AI agents rework a page from generic advice: add social proof, make the CTA stronger, tighten the headline. Web Anatomy gives the agent evidence instead. The skills read a page as a structure of known sections (hero, value proposition, trust, testimonial, pricing, FAQ, CTA), then ground every move in a benchmark library of real pages scored section by section.

The benchmark behind the skills (numbers to confirm before release):

3,500+ scored sections
500+ landing pages
290+ companies

The skills run standalone with built-in patterns. Connecting the hosted MCP (highly recommended) pulls the live benchmark data and real reference screenshots into every report. See Live benchmark data.

The four altitudes

Web Anatomy works at four zoom levels. The altitude matches the question being asked.

Altitude	The question	Skill
Page	What do the strongest pages in this market do, and how does mine compare?	`find-examples`
Audit	How does my whole page stack up, and what should I change first?	`audit-page`
Section	How do I level up one section, from foundational to best-in-class?	`research-best-practices`
Fix	Write the grounded copy to rework a page or build a new one.	`write-page`

After the copy is written, `build-page` assembles the structure + copy into a shareable wireframe with a coherent, single-exemplar design system. It is the terminal step on both branches (improve and create), so it sits above the altitudes rather than inside one.

Run webanatomy-setup once first. It captures product, ICP, industry, competitors, and proof assets into .agents/webanatomy-context.md, so every skill gives sharper, on-brand recommendations.

Two flows

Improve an existing page: audit-page (diagnose) -> write-page (rewrite the weak sections) -> build-page (optional: assemble the improved page as a shareable wireframe, in your page's own look).
Create a new page: find-examples (pick one exemplar homepage) -> write-page build mode (a light outline adopts the exemplar's section order, then writes the copy) -> build-page (assemble the wireframe in the exemplar's look).

The skills

Skill	Altitude	What it does
`webanatomy-setup`	Foundation	Run once. Captures product, ICP, industry, competitors, proof assets, and priority pages into `.agents/webanatomy-context.md`.
`find-examples`	Page	The market scan. Pulls the top-ranked pages and sections in a market, shows what to steal, and when you share your page, labels how it compares. Absorbs the old `benchmark-compare`.
`audit-page`	Audit	Scores the current page against a CRO rubric, diagnoses it section by section, and returns a prioritized fix list. Runs standalone, no MCP required.
`research-best-practices`	Section	The section deep-dive. Takes one section and returns a tiered improvement ladder (foundational, competitive, best-in-class), each grounded in real benchmark sections.
`write-page`	Fix	The copy engine. Turns a diagnosis, a tier, or a chosen structure into grounded copy-paste sections; reworks an existing page or writes a new one.
`build-page`	Assemble	The terminal assembler. Takes a structure + its copy and lays them out as a shareable wireframe with a single-exemplar design system (a benchmark page for a new page, your own page when improving).
`moodboard`	Page	The section-by-section visual board. Captures the live page section by section and pulls benchmarks from the MCP, then composes each section as current-state-large + problems + a benchmark screenshot grid + discipline-tagged practices + recommendation. Where `find-examples` shows what to steal, `moodboard` composes the whole page as a visual reference you build from.

Visual Reports

Web Anatomy does not rely on chat to render screenshots. The output skills write local visual artifacts:

.webanatomy/

├── find-examples/ ├── audit-page/ ├── research-best-practices/ ├── moodboard/ │ └── page-date/ │ ├── report.md │ ├── report.html │ └── references/ ├── write-page/ │ └── topic-date/ │ ├── report.md │ ├── report.html │ └── references/ │ ├── current.png │ └── company-section.png └── build-page/ └── page-date/ ├── wireframe.html ├── design-system.md └── references/

The chat response should stay short: top findings, report path, and any screenshot or MCP limitations. report.html is the product experience.

Live benchmark data (optional, highly recommended)

The skills work on their own, so install them and start immediately. Connecting the hosted Web Anatomy MCP is never mandatory, but highly recommended: it grounds every recommendation in live benchmark data and real reference examples instead of static guidance, which is where the skills are at their best. It needs a beta token and one config command per IDE:

Sign in at https://www.webanatomy.ai/dashboard/mcp to get your token + per-IDE config. You must be signed in, because the page generates your personal token there.

The skills use MCP tools such as search_pages, get_page, search_sections, and get_section when connected, and degrade gracefully to static guidance when not. Scores, thresholds, raw marker coordinates, and benchmark field names stay internal; user-facing reports translate them into plain-English patterns and gap labels.

Want to see the benchmark first? Browse the public scored sections gallery at https://www.webanatomy.ai/best-landing-pages/sections — real landing-page sections, scored, with what makes each one work. It is the same library the MCP serves to your agent, so you can explore it before connecting anything.

Why "Anatomy"

Most AI-agent skill packs frame pages as a job (CRO, copywriting, SEO). Web Anatomy frames them as a structure: hero, proof, problem, solution, pricing, FAQ, CTA. Every section has known patterns, known anti-patterns, and known reference companies.

Every Web Anatomy skill turns a page into parts: hero, proof, problem, solution, pricing, FAQ, CTA. Each part has known patterns, anti-patterns, and benchmark examples. The framework and the evidence travel together.

Compatibility

✅ Claude Code
✅ OpenAI Codex
✅ Cursor
✅ Windsurf
✅ Any agent that reads .agents/skills/ /SKILL.md per the Agent Skills spec

Install options

Option 1 — CLI (any agent):

# Installs the whole pack to .agents/skills/

npx skills add GabrielAmz/web-anatomy

Update later (or just re-run the command above, it's idempotent)

npx skills update GabrielAmz/web-anatomy

Option 2 — Claude Code plugin (version-aware updates):

/plugin marketplace add GabrielAmz/web-anatomy

/plugin install web-anatomy

Claude Code knows the installed version and when a newer one ships. Update with /plugin marketplace update web-anatomy then /plugin update web-anatomy, or turn on auto-update for the marketplace to make it hands-off. Skills install namespaced: /web-anatomy:write-page, /web-anatomy:build-page, and so on.

Option 3 — clone and copy manually:

git clone https://github.com/GabrielAmz/web-anatomy

cp -r web-anatomy/skills/* .agents/skills/

After install, start with webanatomy-setup. The benchmark-backed workflows degrade gracefully when MCP isn't connected, falling back to static/reference guidance, but they are at their best with live benchmark data, so connecting MCP is highly recommended.

Repo layout

skills/ holds the skill pack, the source of truth installed by npx skills add.

Contributing

PRs welcome. See CONTRIBUTING.md for the new-skill recipe: kebab-case, YAML front matter, clear workflow names, and body under 5K tokens.

License

MIT. Use it, fork it, sell it, ship it.

Built by Gabriel Amzallag. The Web Anatomy pack is a public extraction of the patterns powering a private landing-page benchmark and audit tool. The skills give you the framework; the analyzer gives you the data.

WebAnatomy

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

SSTracker free youth training

README from the maker

Web Anatomy

What Web Anatomy is

The four altitudes

Two flows

The skills

Visual Reports

Live benchmark data (optional, highly recommended)

Why "Anatomy"

Compatibility

Install options

Update later (or just re-run the command above, it's idempotent)

Repo layout

Contributing

License