Emerging

70/100

6 hours ago

themeseed

Item: themeseed
Rating: 70
Author: M8ven

MCP server that analyzes a CMS's active theme and generates realistic demo content tailored to it, letting users judge themes with real-looking articles, images, and embeds.

→ ThemeAnax/themeseed · listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every push why connect →

Who stands behind it

ThemeAnax · Claimed

Source: Glama

Maintenance & responsiveness

as of 2026-08-19

Issues closed (90d): 0 · 0 open

Releases (90d): 2

Active contributors (6mo): 1

⚡ Upgrade to Live Monitored

Connect your repo and M8ven re-verifies it on the push itself. Without it we re-check verified listings about once a day, so a fix can sit unseen. Read-only, one click, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings

✅

No credential exfiltration, no sensitive file access, no obfuscation

Static analysis found nothing flowing your secrets to unexpected places.

✅

Open source with a license and README

Anyone can audit the code, the license is declared, and the publisher documents what it does.

🔐

You'll be asked for 6 credentials: FAL_KEY, GOOGLE_API_KEY, OPENAI_API_KEY, PEXELS_API_KEY, UNSPLASH_ACCESS_KEY, XAI_API_KEY

These are read from process.env at runtime. Make sure you trust where they’ll be sent.

Are you the publisher? Confirm or correct these findings.

// environment variables

To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.

🔐 secretFAL_KEYfal fal-ai/flux/schnell yes

configGHOST_THEMES_DIR

🔐 secretGOOGLE_API_KEYgemini gemini-2.5-flash-image yes

🔐 secretOPENAI_API_KEYopenai gpt-image-1 yes

🔐 secretPEXELS_API_KEYpexels yes

configTHEMESEED_AI_IMAGE_ADAPTERWhichever key is present is used; forces one and

configTHEMESEED_AI_IMAGE_MODELoverrides the model. Each backend asks for output shape

configTHEMESEED_CONFIG_DIR

configTHEMESEED_LOCAL_IMAGE_DIRScans a directory () and picks files whose aspect ratio is closest to

configTHEMESEED_LOG_LEVELdebug turns on verbose diagnostics; all logging goes to stderr, because

configTHEMESEED_STOCK_PROVIDERreturns carries a credit saying exactly that. Set to force one.

🔐 secretUNSPLASH_ACCESS_KEYunsplash yes

🔐 secretXAI_API_KEYgrok grok-imagine-image yes

// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

7/7 tools missing one or more hints — list_sites (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); add_site (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); remove_site (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +4 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

Only 0/7 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Secrets not logged

1 secret value sent to console.log

Redact or omit secret values from log output.

Domain consistency

npm scope @indianic doesn't match GitHub owner themeanax

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail

The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.

// improvement guidance — verified publishers only

We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.

// embed badge in your README

[![M8ven Score](https://m8ven.ai/badge/mcp/themeanax-themeseed-tizj0o)](https://m8ven.ai/mcp/themeanax-themeseed-tizj0o)

Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.

commit: 5088e737d0c54209f5763dca19e2a1dc889e2a2a

code hash: 193f951eaec716ff36eaa76fa904e9797deb6f46d11da508767fb1bc2c0dc939

verified: 8/19/2026, 11:21:56 AM

view raw JSON →

Check MCPs from inside your assistant

Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check

check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern

How to add it →Free · no account needed · works in any MCP client