Scores whether a page reads as AI-generated and names the tells to fix.
Listed on
First seen 19 Oct 2026. One server, whatever directories list it: each directory listing keeps its own page and history.
1
Directories
Collected by InvokeRank
3
Tools
From an anonymous probe
-
ToolBench grade
Not graded by Arcade
-
GitHub stars
No repository data
Tools
| Tool | Description | Behaviour |
|---|---|---|
| check_code | Check a source file or diff for AI 'tells' left in comments: narrating fulfilling a request instead of describing the code ("as requested," "I've added," "here's the updated version") and hedge words. These reveal there was a conversation behind the change that a later reader has no access to. Call this before committing or shipping code an agent wrote. | Read-only |
| check_copy | Check marketing or outreach copy (an email, a landing-page draft, a pitch, a social post) for the tells that make it read as AI-generated: cliché vocabulary (delve, unlock, empower, seamlessly integrate, etc.), negative-parallel framing ("not just X, but Y"), hedge words, heavy em-dash use, and diagnosing a problem with no fix in the same breath. No page or markup needed, just the text. Call this before sending copy to a human. | Read-only |
| check_design | Check a page's HTML/CSS/copy/interaction for the patterns that make AI-generated work read as generic: default fonts, soft tech gradients, pill+arrow buttons, eyebrow labels, a composition with no real width/background variation across sections, uniform card grids, copy tells (AI vocabulary, negative-parallel framing, hedge words, heavy em-dash use), and experience gaps (a diagnosis with no next step, dead-end links). Every finding includes a concrete fix. Call this before presenting UI to a human. | Read-only |
| Directory | Listing | Tier | First seen |
|---|---|---|---|
| Official MCP Registry | Design Check | - | 19 Oct 2026 |