v0 integration · bring-your-own MCP · SDK-configurable
Use Etymolt in v0.
One SDK call. Workspace-scoped. Sub-2s verdicts.
v0.mcpServers.create registers Etymolt for your workspace. Every v0 prompt that names a project, a route, a deploy target, or a team can call the verdict before the name lands in a Vercel deploy.
Sub-3s p95 · 12.7M US marks · 14 social platforms · free for five
What's available today
Why this, why now
v0 ships the candidate. Etymolt ships the receipt.
v0 is the fastest path from prompt to deployed UI. The missing piece between “the model proposed a name” and “we shipped it to a domain” is a verification layer that does not exist inside the LLM. Etymolt is that layer — trademark, domain, 14 handles, cultural meaning, sound symbolism — called before the deploy.
Two install paths
Programmatic via SDK, or manual via the prompt form.
I · For developers
v0 SDK.
Workspace-scoped registration via the published v0 SDK. Idempotent — re-running does not duplicate.
// install: npm i v0-sdk
import { v0 } from "v0-sdk";
// Register Etymolt as an MCP server for your v0 workspace.
// The server is then available to every v0 prompt without
// extra configuration in the UI.
await v0.mcpServers.create({
name: "Etymolt",
url: "https://api.etymolt.com/mcp",
});No API key required for the free tier. Five verdicts per IP are free.
II · For everyone
Prompt form.
The v0 chat UI exposes an MCP picker. Add Etymolt by URL. Same effect as the SDK call; persisted at the workspace level.
# 1. Open the v0 prompt form
# 2. Click the MCP server picker (Context7 is in the preset list)
# 3. Choose "Add MCP server"
# 4. Paste this URL:
https://api.etymolt.com/mcpThe picker also accepts the preset list (Context7 is the named example).
Direct URL · for any v0 surface that accepts MCP endpoints
https://api.etymolt.com/mcpHow it fires
v0 reaches for Etymolt on every naming intent.
I
You prompt v0.
"Build a SaaS landing for X" or "rename this deploy target" — any prompt that signals naming intent. v0 proposes the candidate.
II
v0 calls verify_brand_name via MCP.
Etymolt fans out across USPTO + RDAP + 14 social probes in parallel. Sub-3s p95. v0 surfaces the verdict in the response with the disclaimer quoted verbatim.
III
Verdict drives the next step.
PROCEED candidates ship. ABANDON candidates do not get baked into a deploy. ITERATE and DUE_DILIGENCE candidates surface with the blocker called out so the next prompt can pick again.
You v0 Etymolt (MCP) │ │ │ │ "build X" │ │ │ ───────────────────▶ │ │ │ │ naming intent fires │ │ │ ─────────────────────▶│ │ │ call: verify_brand_name │ │ │ │ │ ◀─── verdict + score ─┤ │ ◀── verdict + ── │ │ │ disclaimer │ │ │ (verbatim) │ │
The validation stack
Five axes. One signed verdict.
Trademark
USPTO · TTAB · UKIPO · Madrid
Domain & handles
RDAP · WHOIS · 14 platforms
Cultural
7 languages · 20 markets
Linguistic
1.4M-name distinctiveness corpus
Sound symbolism
12 perceptual axes · TTS round-trip
What we are NOT
We don't generate names. We validate them.
v0's model proposes the candidate. Etymolt verifies it across five axes against live ground truth. The two products sit cleanly on different sides of the workflow.
FAQ
Common questions.
How do I install Etymolt in v0?
Two paths. (1) Programmatically: v0.mcpServers.create({ name: "Etymolt", url: "https://api.etymolt.com/mcp" }) using the v0 SDK. (2) Manually: in the v0 prompt form, click the MCP server picker, choose Add MCP server, paste https://api.etymolt.com/mcp. Both register the server for your workspace.
What is the SDK pattern Vercel exposes?
v0 exposes mcpServers.create, mcpServers.list, and mcpServers.delete on the v0-sdk npm package. Treat these like any other workspace-scoped resource. Etymolt's URL is a stable HTTPS endpoint; you do not need a secret to create the resource for the free tier.
Why register Etymolt for a v0 workspace?
v0 prompts that name a project, a route, a deploy target, or a Vercel team produce candidates that the model has not actually verified against live USPTO, RDAP, or social-handle ground truth. Etymolt is the verification primitive that runs before the name lands in a deploy or a repo — five axes, sub-2 seconds.
Does this generate names? Does it compete with v0?
No. Etymolt does not generate names. We validate the names v0's model already proposes. v0 makes the candidates; we return the verdict. The two products sit cleanly on different sides of the workflow.
Does Etymolt see my v0 prompts or generated code?
No. When v0 invokes verify_brand_name, only the name string and an optional category hint travel to api.etymolt.com. No prompt content, no generated code, no deploy artifacts, no Vercel account identifiers. We log: name, timestamp, hashed source IP. Retained 90 days.
Is Etymolt in v0's MCP server registry?
Submission is in flight. Once listed, v0 users can pick Etymolt from the preset list without entering the URL manually. Until then, the SDK and prompt-form paths above register the server for your workspace identically.
What does this cost?
Five verdicts per IP are free. Signed-up users get ten more. After that, ten dollars buys ten more. No subscription. The v0 subscription itself is billed by Vercel — separate line item.
Bureau Model · clearance signal · not legal advice
Bring verdicts into v0.
Bring-your-own MCP · one SDK call, every v0 workspace · see all surfaces →
Clearance signal, not legal advice. Confirm with trademark counsel before adopting a name in commerce. Data sources have stated freshness windows; refer to coverage_caveat per jurisdiction.
NPM · @etymolt/mcp-server