8am MyCase
Look up MyCase cases, billing, trust balances, documents and messages from Claude.
Run a trademark clearance search from Claude: one mark and one jurisdiction per search, 194 registers.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Haloo Trademark Clearance MCP server runs Haloo's trademark clearance search from Claude. You give a proposed mark, one jurisdiction and its Nice classes; Haloo searches that official register and returns ranked prior marks, a GREEN, YELLOW or RED triage band and a clearance memo. Each search spends one prepaid Haloo usage unit.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Because your Haloo account has no prepaid usage units left. Each clearance search consumes one unit, and when none remain the connector returns a payment_required result with a billing link where you can buy more. Haloo's docs do not publish unit prices or bundle sizes, so check the billing page for the current offer before you run a batch of jurisdictions.
No. Haloo says a failed search is terminal and its unit is refunded, and invalid input such as an unsupported jurisdiction or a Nice class outside 1 to 45 is rejected before anything is charged. If the refund call itself fails, the unit shows refund pending and the hold expires in about 30 minutes. Polling a search with get_clearance_report never costs a unit.
Most Haloo clearances finish in about 10 minutes, and some take up to about 30, according to Haloo's connector docs. A search runs in the background after you submit it, and Claude checks progress with get_clearance_report at the interval the server suggests, roughly every five minutes. A search that stops progressing for an unusually long time reports a stale status.
initialize returned HTTP 401 with a WWW-Authenticate challenge carrying scope="mcp:tools" and naming the RFC 9728 descriptor at https://connect.haloo.ai/trademark-search/.well-known/oauth-protected-resource/mcp, which listed https://my.haloo.ai/public-mcp as the authorization server and the docs page above as resource_documentation (2026-11-18). · retrieved 2026-11-18Connect Haloo Trademark Clearance once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.