WEIR AI MCP server
ai.weir/weir-aiweir.aistreamable-httpv1.3.1Scanned
Likeness clearance and identity license terms for a named person. A listing is never permission.
10 tools: 3 change things and 7 only read.
- Reads private data · 1
- Reads text others write · 3
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the WEIR AI MCP server can do
The WEIR AI MCP server is published by weir.ai, a domain the MCP Registry verified. It has 10 tools. It can create or change data (3 tools: health, license_types and check_identity), but cannot delete data. 7 tools only read.
1 tool reads private data (discovery); 3 tools bring in text other people can write (discovery, search_mentions and list_license_mentions).
The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 8, 2026, version 1.3.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
10 tools
Changes things 3Claude Code: ask
check_identityStart 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.1 finding
Why it is in this group
- The description's first verb is "start": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "check_identity" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "start": a word for a change.
Description, as the server wrote it 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]
Annotations the server declares
- title: Check likeness clearance for a name
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
healthCheck whether the WEIR AI API is up.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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]
Annotations the server declares
- title: Check API health
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
license_typesExplain WEIR AI's license types (open, earn, protect, blocked) in plain English.1 finding
Why it is in this group
- The name "license_types" says "type": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "license_types" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "license_types" says "type": a word for a change.
Description, as the server wrote it 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]
Annotations the server declares
- title: Explain license types
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 7Show 7 read-only tools
discoveryRead WEIR AI's public discovery document (public endpoints, base URL, rate limits).Reads private dataReads text others writeNo findings
Why it is in this group
- The description's first verb is "read": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "document": it reads documents.
- untrusted-inputThe description's first sentence says "read" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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]
Annotations the server declares
- title: Read service discovery
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_licenseGet full detail of a license the connected account can access, by external_id.No findings
Why it is in this group
- The name "get_license" says "get": a word for reading.
Description, as the server wrote it 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]
Annotations the server declares
- title: Get my license
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_public_licenseRetrieve the public status, license category, available terms information, and terms link for a specific public WEIR license ID (e.g.No findings
Why it is in this group
- The name "get_public_license" says "get": a word for reading.
Description, as the server wrote it 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]
Annotations the server declares
- title: Get one public license
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_license_mentionsRetrieve detected mentions for a license the connected user is authorized to monitor.Reads text others writeNo findings
Why it is in this group
- The name "list_license_mentions" says "list": a word for reading.
What it can reach
- untrusted-inputThe name "list_license_mentions" says "list" and "mention": it reads comments, which other people can write.
- untrusted-inputThe description's first sentence says "retrieve" and "mention": it reads comments, which other people can write.
Description, as the server wrote it 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]
Annotations the server declares
- title: List detected mentions
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_licensesList licenses the connected WEIR AI account owns or manages (including roster clients the account is permitted to see).No findings
Why it is in this group
- The name "list_licenses" says "list": a word for reading.
Description, as the server wrote it 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]
Annotations the server declares
- title: List my licenses
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_catalogSearch publicly discoverable WEIR AI identity licenses.No findings
Why it is in this group
- The name "search_catalog" says "search": a word for reading.
Description, as the server wrote it 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]
Annotations the server declares
- title: Search public license catalog
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_mentionsSearch WEIR AI's supported web and social media sources for potential mentions associated with a person's name.Reads text others writeNo findings
Why it is in this group
- The name "search_mentions" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe name "search_mentions" says "search" and "mention": it reads comments, which other people can write.
- untrusted-inputThe description's first sentence says "search" and "web": it reads web pages, which anyone can write.
Description, as the server wrote it 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]
Annotations the server declares
- title: Search possible mentions of a name
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 16, 2026, 14:20 UTC, unchanged since Nov 9, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-03-26
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://wapi.weir.ai/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://wapi.weir.ai
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://wapi.weir.ai/mcp: tools/list returned 10 tools to an anonymous client, including health (write), license_types (write), check_identity (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnlicense_types
The server marks "license_types" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "license_types" says "type": a word for a change.
- Warncheck_identity
The server marks "check_identity" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "start": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.3.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http weir-ai https://wapi.weir.ai/mcpclaude mcp add --transport http weir-ai https://wapi.weir.ai/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__weir-ai__discovery",
"mcp__weir-ai__search_catalog",
"mcp__weir-ai__get_public_license",
"mcp__weir-ai__search_mentions",
"mcp__weir-ai__list_licenses",
"mcp__weir-ai__get_license",
"mcp__weir-ai__list_license_mentions"
],
"ask": [
"mcp__weir-ai__health",
"mcp__weir-ai__license_types",
"mcp__weir-ai__check_identity"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as weir-ai. Review it before you use it.
Capability tags behind 3 rules
- mcp__weir-ai__discovery private-data, untrusted-input
- mcp__weir-ai__search_mentions untrusted-input
- mcp__weir-ai__list_license_mentions untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/ai.weir/weir-ai/verify?hash=1284bfea6d288cbe9896e2682eb363c1e19549d4e62e9fb2baaeac0d360cea49" | jq -e '.changed == false'Pinned hash 1284bfea6d28, from Nov 8, 2026, 21:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.weir/weir-ai/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.weir/weir-ai)Source: MCP Registry. Synced Nov 8, 2026, 21:17 UTC.
WEIR AI MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the WEIR AI MCP server safe?
- No scan can promise that. What its definitions show: 10 tools, 3 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the WEIR AI MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the WEIR AI MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the WEIR AI MCP server have?
- 10 tools: 3 write, 7 read. health, license_types, check_identity, discovery, search_catalog, get_public_license, search_mentions, list_licenses and 2 more.
Does the WEIR AI MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the WEIR AI MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the WEIR AI MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.