Back to MCP servers

WEIR AI

https://wapi.weir.ai/mcp
● healthy

Likeness clearance and identity license terms for a named person. A listing is never permission.

What we measured

Over the last 30 days we probed this MCP server 5 times on 4 days; it answered 5 (100%). Median response 444 ms, 95th percentile 551 ms.

When we called tools/list it returned 10 tools, including health, discovery, license_types, over MCP protocol revision 2025-03-26.

Among the 53,642 reachable MCP servers in our snapshot of 2026-11-13 01:12 UTC, it is faster than 43% and higher on readiness than 75%.

From agent-tools.cloud's own probes, last checked 2026-11-12. How we measure

Tools (10)

As returned by the server's own tools/list when we called it.

health
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,…
discovery
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 sear…
license_types
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.…
search_catalog
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…
check_identity
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 th…
get_public_license
Retrieve the public status, license category, available terms information, and terms link for a specific public WEIR license ID (e.g. WRT2TVR2A). Returns found:…
search_mentions
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 identi…
list_licenses
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 st…
get_license
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. L…
list_license_mentions
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…
Transport
streamable-http
Auth
—
Cost
—
Protocol revision
2025-03-26
negotiated, not declared

MCP readiness

B · 84/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. For x402 and A2A listings it contributes up to 15 of the 100 quality points; for MCP listings it is shown for reference only. Search order and leaderboards use the separate quality grade (here B+, 88.3/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake 10/10 initialize and tools/list both answered.
Live MCP endpoint 25/25 Endpoint answers the MCP initialize handshake (551 ms).
Protocol revision 5/10 Speaks MCP 2025-03-26, 3 revision(s) behind 2026-07-28.
Signed descriptor n/a No MCP standard defines a signed server descriptor.
Uptime (30 days) 15/15 5/5 probes succeeded over 30 days (100%).
Tool declaration 10/10 Lists 10 tool(s) with descriptions.
Verified identity 7/10 Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
Freshness + modern flags 4/5 seen in a source within 7 days.
Auth declaration 0/5 How to authenticate is not stated.
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Responsive (551 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-12.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,642 reachable MCP servers in our daily snapshot (2026-11-13 01:12 UTC). Display only; it does not change search order.

Readiness
Higher than 75% of peers
This listing 84 · peer median 81
Latency
Faster than 43% of peers
This listing 415 ms · peer median 349 ms

Where it loses the most points, and how to win them back

  • Protocol revision −5 — Support the current protocol revision.
    Now: Speaks MCP 2025-03-26, 3 revision(s) behind 2026-07-28.
  • Auth declaration −5 — State how to authenticate (an auth scheme, or that none is needed).
    Now: How to authenticate is not stated.
  • Verified identity −3 — Claim the listing and prove control of its domain.
    Now: Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

mcp-registry since 2026-11-09

How to connect

MCP endpoint (streamable-http)
https://wapi.weir.ai/mcp
JSON-RPC initialize probe
curl -X POST https://wapi.weir.ai/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Homepage
https://weir.ai/developers/mcp