Likeness clearance and identity license terms for a named person. A listing is never permission.
Scored across 10 tools
Each tool targets a distinct resource+action, and the descriptions actively route the agent between near-neighbours (check_identity vs search_catalog, get_license vs get_public_license, search_mentions vs list_license_mentions). The public/account-scoped split is stated explicitly on every tool, so misselection is unlikely.
The dominant pattern is verb_noun (check_identity, get_license, list_licenses, search_catalog, search_mentions), applied consistently across the read operations. Three tools break the pattern with bare nouns (discovery, health, license_types), but these are meta/utility endpoints and remain unambiguous.
Ten tools is well within a healthy range and every one earns its place: identity checks, catalog search, public and private license reads, two mention surfaces, plus three lightweight meta tools (health, discovery, license_types). Nothing feels padded or redundant.
The read-side lifecycle is well covered: discover → check identity → search catalog → fetch terms → monitor mentions, with clear next-step handoffs. Gaps are minor but real: there is no tool to fetch a single mention's detail, no account/profile introspection tool, and no way to initiate a licensing request (presumably intentional, since decisions happen on weir.ai).
Start here when anyone asks whether a real person's name, image or likeness can be used — in an ad, a campaign, generated media or a contract. Checks whether that person has publicly declared how their likeness may be used on WEIR AI. Required: name (full name, at least 3 characters). Returns status blocked, protect, earn (licensable), open, or no_public_declaration, plus terms_url when a public license matches. Private licenses always return no_public_declaration, so this never reveals whether someone is a member. no_public_declaration is not permission. To browse who is licensable rather than check one named person, use search_catalog. [Public, no account needed]
Inputs: name (required).
Read WEIR AI's public discovery document (public endpoints, base URL, rate limits). Use when you need to learn the API surface; for licensing questions use search_catalog instead. [Public, no account needed]
Inputs: no named parameters.
Get full detail of a license the connected account can access, by external_id. Use for the owner's own records; for the public catalog use get_public_license. Licenses the account can't access return NOT_FOUND_OR_NOT_PUBLIC. Needs license:read. [Needs a connected WEIR AI account; scope license:read]
Inputs: external_id (required).
Retrieve the public status, license category, available terms information, and terms link for a specific public WEIR license ID (e.g. WRT2TVR2A). Returns found:false with code NOT_FOUND_OR_NOT_PUBLIC when the ID is private or doesn't exist; that never reveals whether a private license exists and is never permission. Next step: share terms_url so the person can review the terms on WEIR AI; any licensing decision is made by the person there. [Public, no account needed]
Inputs: external_id (required).
Check whether the WEIR AI API is up. Use only when a call fails and you need to tell the user if WEIR AI is down. Returns {status, version, timestamp}. [Public, no account needed]
Inputs: no named parameters.
Explain WEIR AI's license types (open, earn, protect, blocked) in plain English. Use before explaining catalog results or when the user asks what a type allows. [Public, no account needed]
Inputs: no named parameters.
Retrieve detected mentions for a license the connected user is authorized to monitor. Detection is not proof of infringement. Use the external_id already named in the conversation (e.g. from get_public_license); don't ask the user to repeat it. Returns rows with source link, date, type and status, ready for a table. Optional page, per_page 1-100. Needs mention:read; if AUTHENTICATION_REQUIRED, explain WEIR AI needs account authorization, then retry the same request once connected. [Needs a connected WEIR AI account; scope mention:read]
Inputs: external_id (required), page, per_page.
List licenses the connected WEIR AI account owns or manages (including roster clients the account is permitted to see). Use for 'my licenses' or as the first step of monitoring. Optional page, per_page 1-100. Needs a connected WEIR AI account with license:read; if it returns AUTHENTICATION_REQUIRED, tell the user WEIR AI needs account authorization through their assistant's connection settings. [Needs a connected WEIR AI account; scope license:read]
Inputs: page, per_page.
Search publicly discoverable WEIR AI identity licenses. Use when a user wants to find publicly listed likeness licensing options (e.g. for a campaign). Returns entries with license type, verification status and terms_url for reading the rights holder's published terms. Optional: search (text), license_type, limit 1-100, offset. 'Anonymous' names are a rights-holder privacy choice. Search results do not establish permission. Next step: get_public_license for one entry. To check one named person's clearance, use check_identity instead. [Public, no account needed]
Inputs: limit, offset, search, license_type.
Search WEIR AI's supported web and social media sources for potential mentions associated with a person's name. The person does not need an existing WEIR identity or license. Results are candidate matches, not verified identification or evidence of infringement. Required: name (a person's full name; the same name checks as weir.ai/search apply). Optional: limit 1-50. When the user has connected their WEIR AI account, results follow their own plan; without a connection some results are hidden (redacted:true). Give the user results_url to see what their plan allows. Never claim a match is the person. [Public, no account needed]
Inputs: name (required), limit.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Likeness rights, cleared: a use of a person's face, voice or persona, checked against their terms.
US & EU trademark, domain & handle clearance — a signed three-state verdict, not legal advice.
Identity-rights registry lookups before AI generation: is a face, voice or persona registered?
Commercially licensed image generation and editing with IP indemnification.
Add one secure layer between your agents and this server.
