A search today turned up six trademark MCP servers I had not seen before. Search is the easy part now. Anyone with the USPTO bulk files can put a search tool behind an endpoint in a weekend.
Watching is the part that is not easy.
I work on the monitoring side at IP Defender, so I am biased. But the tests below do not depend on which vendor you pick. Run them on us too.
1. Search answers once. A watch has to remember.
A search tool returns the marks that exist right now. Ask the same question tomorrow and you get a slightly longer list. Nothing in the response tells you which one is new. If your assistant has no record of yesterday's result, a "watch" is just you running the same query again and scrolling.
So the test is one question. Ask the server what changed since a timestamp. Something like "show me new filings since 2026-09-30". A real watch keeps a stored set of watched marks and returns only the delta, with the events attached to each record.
Two hosted servers pass this today in different ways. MarkMesh documents a watch plus a changes-since call. CompuMark's MCP server exposes watch orders and watch results as tools. Both are real watches, not re-runs of a search.
If the tool list has no watch object and no delta call, you are looking at a lookup tool with monitor language in the copy.
2. Registrations arrive too late.
The window that matters sits between publication and registration. In the US you get 30 days from publication to oppose. In the EU you get 3 months from publication of the application. Once the mark registers, the argument gets more expensive.
Ask what date the record is keyed on. Plenty of servers return registered marks only, because registrations are the clean data set. That answers a different question, and it answers it too late to be cheap.
3. Coverage is usually a search claim.
"200 plus jurisdictions" often means the search can reach 200 registers when you ask it. It says nothing about how often anyone watches them. Ask which offices are checked daily, which weekly, and which only on demand.
One detail worth checking. A Madrid filing that designates your country can hurt you exactly like a national filing. If the coverage list is only national offices, the watch has a hole in it.
4. Price behind an OAuth screen.
A lot of servers have no price on the page. You connect, you get a workspace, then a call. If you cannot see a number before the consent screen, budget for that call.
A short checklist
Use this on any trademark MCP server, ours included.
- Can I list my current watches by name
- Can I pick countries per watch
- Is there a changes-since call that returns only new records
- Does it key on publication date, not just registration
- Does it include Madrid designations
- Do alerts carry the register and the record number so a lawyer can check the source
- Can I pause a watch without deleting it
- Is the monthly price visible before I connect
Six yes answers or more is a real watch. Four or fewer and you bought a search box with a subscription fee.
Where we sit
IP Defender runs a hosted remote MCP server at https://www.ipdefender.eu/mcp. OAuth 2 for sign in, no local install. The tools cover watches and alerts, conflicts, pricing, billing and settings, so you can start a watch, add a country, or read your alerts from inside the chat.
The numbers, which are public on our site. 5 AI watch agents, 11 detection layers, 22,000 plus character-fraud patterns for homoglyph tricks, 55 markets, prices from 6 to 15 dollars a month per country per brand, billed daily.
What we do not do. We do not file. We do not oppose. We do not tell you whether two marks are legally confusing. We tell you that a neighbour appeared on a public register while the window is still open, and your lawyer takes it from there.
If you want the exact steps to connect the endpoint to ChatGPT, Claude, Grok or anything else that speaks MCP, that page walks through the setup, including what to do when the connector does not show up.
That is the whole ask. Connect it once, then ask it every Monday what changed.
