NoonAI Automatic Face Detection & Anonymization MCP
Wire YOLO-based automatic face anonymization into an agent so user-uploaded photos and videos can be blurred or redacted before storage or public release.
Overview
com.dyndns-server.noon-ai/automatic-face-anonymization-mcp is a Ship-phase MCP server that uses YOLO to auto-detect faces in images and video and apply face-only blur, redaction, and related masking via streamable HTTP.
What is this MCP server?
- Remote streamable-http MCP at noon-ai.dyndns-server.com (server version 0.1.10)
- YOLO auto-detects faces for face-only anonymization without manual bounding boxes
- Supports blur, hard redaction, and extended masking for bodies and license plates
- Works on both images and video streams from the same NoonAI DIS MCP family
- Open-source server implementation on GitHub (MHNCity/noonai-dis-mcp-server)
- Server package version 0.1.10 in catalog metadata
- Single streamable-http remote URL on noon-ai.dyndns-server.com
- Source repository MHNCity/noonai-dis-mcp-server on GitHub
What problem does it solve?
You need to de-identify faces in media quickly from the agent workflow, but standing up detection models and batch editors eats time you do not have as a solo shipper.
Who is it for?
Indie builders publishing UGC-heavy SaaS, content tools, or launch collateral who want agent-driven face blur without self-hosting YOLO.
Skip if: Teams that require on-prem-only processing, certified biometric erasure audits, or fine-grained legal hold workflows with no third-party remotes.
What do I get? / Deliverables
After you add the remote MCP, your agent can send media to NoonAI and return anonymized assets ready for docs, launches, and compliant storage.
- Face-anonymized images or video segments with blur or redaction applied
- YOLO-detected face regions processed without manual box drawing
- Optional body and license-plate masking on the same pipeline family
Recommended MCP Servers
Journey fit
Face anonymization is a privacy gate you run when preparing to ship features that expose media—launch pages, demos, support attachments, or production UGC pipelines. Security subphase covers de-identification, consent-safe assets, and reducing PII leakage in screenshots, marketing clips, and app screenshots.
How it compares
Hosted vision anonymization MCP integration, not a local FFmpeg script or a generic image-editing agent skill.
Common Questions / FAQ
Who is automatic-face-anonymization-mcp for?
Solo and small-team builders using Claude Code or Cursor who ship apps or marketing assets containing people and need automated face anonymization from the agent.
When should I use automatic-face-anonymization-mcp?
Use it in the Ship security phase before publishing screenshots, beta videos, support exports, or stored user media that may contain identifiable faces.
How do I add automatic-face-anonymization-mcp to my agent?
Add the streamable-http remote URL https://noon-ai.dyndns-server.com/automatic-face-anonymization-mcp to your MCP client config, per your editor’s MCP registration docs, then invoke the server tools from the agent.