Bolt integration · MCP Connectors marketplace · auto-enable
Use Etymolt in Bolt.
Verification context that prevents your AI from suggesting names that will cause your users legal trouble.
When a Bolt project gets named, Etymolt verifies the candidate against live USPTO, RDAP, and 14 social-handle probes — before the name gets baked into a deploy or a domain purchase. One install, every future project, via the Auto-enable toggle.
Sub-3s p95 · 12.7M US marks · 14 social platforms · free for five
What's available today
Why this, why now
The naming moment is a liability moment.
A name that looks fluent in chat can carry a live USPTO collision, an aftermarket .com priced at five figures, or a handle taken on the platform the user already intends to ship on. Bolt's users discover these collisions only after they have deployed. Etymolt moves the discovery to the moment the name is proposed — the cheapest moment to fix it.
Three steps
Add the connector. Toggle Auto-enable. Done.
I · Open MCP Connectors
Settings → MCP Connectors.
In Bolt, open Settings, choose MCP Connectors. The same surface that lists Notion, Linear, GitHub, Miro, Sentry, Context7, Granola, Jira.
II · Add Etymolt
Paste the URL.
Click Add Connector. Paste this URL.
https://api.etymolt.com/mcpNo API key required for the free tier. Five verdicts per IP are free.
III · Auto-enable
Toggle on.
Switch on Auto-enable for all projects. The verdict now fires on every future Bolt project at the naming moment, without per-project setup.
You can disable per-project from the connector menu later if a project should bypass verification.
Alternative · JSON-config equivalent
For Bolt workspaces that surface raw MCP server config, paste this block. Functionally identical to the URL path.
{
"mcpServers": {
"etymolt": {
"command": "npx",
"args": ["-y", "@etymolt/mcp-server"],
"env": { "ETYMOLT_API_KEY": "(optional — 5 free per IP)" }
}
}
}How it fires
Bolt reaches for Etymolt on every naming intent.
I
You prompt Bolt.
"Scaffold a finance app called X" or "rename this project to Y" — any prompt that signals naming intent. Bolt proposes the candidate.
II
Bolt calls verify_brand_name via MCP.
Etymolt fans out across USPTO + RDAP + 14 social probes in parallel. Sub-3s p95. Bolt surfaces the verdict before the project name is committed to the deploy.
III
Verdict gates the next step.
PROCEED candidates can be deployed. ABANDON candidates are not committed. ITERATE and DUE_DILIGENCE candidates surface with the blocker called out so you can pick again — cheap to fix now, expensive to fix after a domain purchase.
You Bolt Etymolt (MCP) │ │ │ │ "scaffold 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.
Bolt's model proposes candidates. Etymolt verifies them against live ground truth across five axes. The two products sit cleanly on different sides of the workflow. The naming moment in Bolt is the wedge; the verdict is the receipt that keeps the deploy safe.
FAQ
Common questions.
How do I install Etymolt in Bolt?
Open Bolt, go to Settings → MCP Connectors. Click Add Connector and paste https://api.etymolt.com/mcp. Toggle Auto-enable for all projects so the verdict fires on every future project automatically. Save. The etymolt server appears in your tool list immediately. No API key required for the free tier.
Why is Auto-enable for all projects the right toggle?
The naming moment in Bolt happens before a project is named, so a per-project install is too late. Auto-enable makes Etymolt the verification context for every future project the user creates. One install, every naming moment, structurally — that is why we recommend the toggle on.
What is the pitch — why does Bolt need a verification layer?
Bolt generates app scaffolds, repos, and deploys from chat. When the user prompts for a project name, the model proposes candidates that have not been verified against live trademark, domain, or social-handle ground truth. Etymolt is the verification context that prevents the AI from suggesting names that will cause your users legal trouble — five-axis verdict in under two seconds, before the name gets baked into a deploy or domain purchase.
Does this generate names? Does it compete with Bolt?
No. Etymolt does not generate names. We validate the names Bolt's model already proposes. Bolt makes the candidates; we return the verdict. The two products sit cleanly on different sides of the workflow.
Does Etymolt see my Bolt code or project?
No. When Bolt invokes verify_brand_name, only the name string and an optional category hint travel to api.etymolt.com. No project code, no chat history, no deploy artifacts, no StackBlitz account. We log: name, timestamp, hashed source IP. Retained 90 days.
Is Etymolt featured in Bolt's connector marketplace yet?
Featured-slot submission is in flight. Until featured, the install path is the same Settings → MCP Connectors → Add flow. Featured placement reduces install friction for non-developer users. The mechanics of the integration are identical.
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. Bolt seat is billed by StackBlitz — separate line item.
Bureau Model · clearance signal · not legal advice
Bring verdicts into Bolt.
MCP Connector · one URL, every Bolt project · 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