mcp-registry/io.github.resemble-ai/resemble-mcp · v1.30.0
Also listed as glama/resemble-ai/resemble-ai-mcp-server
As of 2026-10-25 18:20 UTC, the Resemble Ai Resemble MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 4 minutes.
Resemble AI: deepfake detection, media intelligence, and watermarking actions, plus docs tools.
Claude Code
claude mcp add --transport http resemble-ai-resemble-mcp-server https://mcp.resemble.ai/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"resemble-ai-resemble-mcp-server": {
"type": "http",
"url": "https://mcp.resemble.ai/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
18 of 18 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
57 parameter(s) across 16 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 16 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.resemble-ai%2Fresemble-mcp/fixes
{
"name": "agent_detection_create_site",
"description": "Create an Agent Detection integration for a website and return its\n publishable key (pk_live_...) and the script snippet to install. domain is\n the site's domain, e.g. example.com. If the team already has an integration\n for that domain, the existing one is returned instead of a duplicate.\n\n The publishable key is safe to put in a public web page: it only sends\n telemetry, only from the listed domains. Never put the Resemble API key in\n a page. Paste the snippet into the <head>",
"inputSchema": {
"type": "object",
"title": "agent_detection_create_siteArguments",
"required": [
"domain"
],
"properties": {
"name": {
"type": "string",
"title": "Name",
"default": ""
},
"domain": {
"type": "string",
"title": "Domain"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "agent_detection_get_analytics",
"description": "Summarise who is visiting a website: people vs AI agents. Returns totals\n (visits, decided, agents, people, agent_share, gated), counts per visitor\n class (human, computer_use_agent, browser_automation, scripted_client), and\n breakdowns by page, day, and network. Use this to show how much traffic\n comes from agents and which pages they use, so the site can be made easier\n for helpful agents and protected from harmful ones.\n\n Filters are optional: site_id (one integration), sett",
"inputSchema": {
"type": "object",
"title": "agent_detection_get_analyticsArguments",
"properties": {
"since": {
"type": "string",
"title": "Since",
"default": ""
},
"until": {
"type": "string",
"title": "Until",
"default": ""
},
"settled": {
"type": "string",
"title": "Settled",
"default": ""
},
"site_id": {
"anyOf": [
{
"type": "integer"
},
{
"type": "null"
}
],
"title": "Site Id",
"default": null
},
"page_path": {
"type": "string",
"title": "Page Path",
"default": ""
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "agent_detection_get_session",
"description": "Get one website visit and the evidence behind its verdict: the feature\n vector it was decided from, plain-language observations, and each model\n read. When the visit was recorded, the raw event stream is available;\n it is omitted unless include_events is true, and then capped at the first\n 200 events. The verdict is advisory: it comes from browser signals, which\n a determined attacker can fake.",
"inputSchema": {
"type": "object",
"title": "agent_detection_get_sessionArguments",
"required": [
"session_id"
],
"properties": {
"session_id": {
"type": "integer",
"title": "Session Id"
},
"include_events": {
"type": "boolean",
"title": "Include Events",
"default": false
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.resemble-ai/resemble-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.resemble-ai/resemble-mcp"}) over MCP.
detect_deepfake ~351 tokensagent_detection_get_analytics ~273 tokensrun_detect_agent_investigation ~273 tokensagent_detection_list_sessions ~262 tokensdetect_ai_text ~256 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.resemble-ai%2Fresemble-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.resemble-ai%2Fresemble-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.resemble-ai%2Fresemble-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.resemble-ai%2Fresemble-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.resemble-ai%2Fresemble-mcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:942edbbf8ae127a9…, first seen 2026-10-17, included at leaf 4108 of 67,739. Version history · verify what your client received.
Compare: most reliable security servers · most reliable analytics servers · most reliable media servers · most reliable ml servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-25 18:20 UTC, the Resemble Ai Resemble MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 4 minutes.
Resemble Ai Resemble MCP server advertises 24 tools, including agent_detection_create_site, agent_detection_get_analytics, agent_detection_get_session, agent_detection_list_sessions, agent_detection_list_sites.
Point your MCP client at this streamable-http endpoint: https://mcp.resemble.ai/mcp
Glimind scanned all 18 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.