Mmcp.market

Taste Bank MCP server

by QuasarG·io.github.QuasarG/taste-bank·v0.2.0

Reusable visual design systems for AI coding agents — browse, fetch, and submit styles via MCP.

B70/100grade B
What users say
No reviews yet
Be the first
Safety scan
B70/100

full report

Adoption
Growing

8 stars

Reviews

Write one

Nobody has reviewed Taste Bank yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Taste Bank tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualityno auth information5/15
  • Maintenancelast push 24 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 70/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

What the publisher says

From the Taste Bank repository's README, as published. We do not edit it. Read it on GitHub

The front-end style library for coding agents — distill a style once, reuse it everywhere. Swipe styles like you're scrolling TikTok — find the one that catches your eye, then hand it to your agent. English | 中文文档

Why Taste Bank

Sound familiar?

- Staring at a blank page, no idea how to lay out your components?

- Layout finally settled — yet the AI's visual style never quite lands?

- A hoard of "beautiful designs" you can never actually summon when you need one?

- The style you painstakingly tuned in your last project has to be re-explained from scratch in the next one?

Getting coding agents to produce well-designed front-ends is a solved problem nobody can actually use. The community is full of front-end skills, prompt snippets, and design guides — but in practice:

  • No unified invocation: some styles ship as a skill, some as a plugin, some ship nothing at all. Actually using them is a chore.
  • No quality bar: without a shared schema, a "style" can be three adjectives in a trench coat — nothing an agent can actually execute.
  • Hard to reuse: great styles die in chat histories instead of being distilled into an asset.
  • No ownership or iteration: no versions, no way to say "only I maintain my styles."

More importantly: the web spawns new styles every day — but not every style is mainstream enough, not every style is your taste. We want a community where people share the front-end taste they actually use — and vote with their feet. Only what truly gets used is truly usable.

Taste Bank's answer: distill each style into a structured style pack (SKILL.md usage guide + precise design tokens + templates/ snapshots), enforced by a zod schema, served through a CLI + skill injection that works with any coding agent. Once a style is in the bank, it's reachable anywhere, versioned, and owned.

The homepage gallery: swipe through live-rendered styles like a feed — horizontal card rail with interactive preview, most-referenced styles and top authors at a glance.

Quick Start

Via CLI (recommended)

One command — installs the CLI globally and teaches your coding agents (Claude Code, Codex, Cursor, ZCode, Kimi Code…) how to use it:

npx taste-bank setup

Then just talk to your agent in plain language:

"Build me a landing page with one of the styles in taste-bank."

Your agent already knows what to do — setup injected a skill that teaches it the taste-bank CLI commands. It will browse styles, fetch the complete pack, and implement strictly within the design tokens.

Prefer the terminal?

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Install directly

The registry entry has no remote endpoint or installable package.

Taste Bank: common questions

Is Taste Bank MCP server safe?
Mostly: it is graded B (70/100). Read the Taste Bank safety report
Does Taste Bank need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Taste Bank maintained?
The last commit was 24 days ago (2026-09-01). The latest release is v0.2.0.
What can I use instead of Taste Bank?
Servers from other publishers that do the same job: Starling Bank MCP server, BankMCP™ MCP server and E Arveldaja MCP server. Compare all Taste Bank alternatives.

Alternatives to Taste Bank

Same job from other publishers: the closest match first, then the best rated.

All Taste Bank alternatives →
  • Starling Bank
    Allow AI systems to view and control your Starling Bank account via MCP.
    B
  • BankMCP™
    Read-only MCP server for your own bank accounts via Enable Banking. Self-hosted, one user.
    A
  • E Arveldaja
    Estonian e-arveldaja (RIK e-Financials) accounting — invoices, bank import, reports.
    B
  • Worldbank
    Query 29,500+ World Bank development indicators for 200+ countries across 60+ years.
    A
  • FiatDock
    MCP marketplace: AI agents buy services from other agents per call in USDC, plus a bank cash-out
    B

More from QuasarG →