Elysia Tools Docs
EN
Language
ZHESPTRUFRDEEN
Back to site
Browse tools

AI Tools

NSFW Image Content Detector

AI content-moderation classifier using NSFWJS to flag uploaded images as safe or potentially inappropriate. Built for moderation and compliance review of your own files — it analyzes uploads only and is not an image search or discovery tool. Supports JPEG/PNG/WEBP/GIF.

json· JSON resultOpen tool

Quick start

Call this tool from your code in three languages.

cURL
# 1) Request a presigned URL → returns { uploadUrl, storageKey }
curl -X POST 'https://api.elysiatools.com/api/upload/presign/nsfw-image-detector' \
  -H 'Content-Type: application/json' \
  -d '{"filename":"imageFile.ext","contentType":"application/octet-stream","size":12345}'

# 2) PUT the file bytes directly to the presigned uploadUrl
curl -X PUT '<presigned uploadUrl>' \
  --data-binary @/path/to/file.ext

# 3) Call the tool, passing the returned storageKey for each file field
curl -X POST 'https://api.elysiatools.com/en/api/tools/nsfw-image-detector' \
  -F 'imageFile=uploads/2026/01/01/your-tool-1700000000000-abc123.ext' \
  -F 'sensitivity=0.5' \
  -F 'analysisMode=auto'

© 2026 Elysia Tools. Developer documentation.

Back to siteBrowse tools

API reference

Send a POST request with your inputs as JSON. File parameters require a separate upload first.

Endpoint

HTTP
POST https://api.elysiatools.com/en/api/tools/nsfw-image-detector

Parameters

NameTypeRequiredDescription
imageFilefileupload requiredYesGIF files will analyze the first frame only. Supports transparency.
sensitivityrangeNoLower values are more strict, higher values are more permissive
analysisModeselectNo—
File-type parameters must be uploaded first via POST /upload/nsfw-image-detector, then the returned filePath is passed to the corresponding file field.

Response format

JSON result

JSON
{
  "key": {...},
  "metadata": {
    "key": "value"
  },
  "error": "Error message (optional)",
  "message": "Notification message (optional)"
}

MCP integration

Add this tool to your Model Context Protocol server so AI agents can list and call it.

Server configuration

Add this block to your MCP client configuration:

mcp.json
{
  "mcpServers": {
    "elysiatools-nsfw-image-detector": {
      "name": "nsfw-image-detector",
      "description": "AI content-moderation classifier using NSFWJS to flag uploaded images as safe or potentially inappropriate. Built for moderation and compliance review of your own files — it analyzes uploads only and is not an image search or discovery tool. Supports JPEG/PNG/WEBP/GIF.",
      "baseUrl": "https://api.elysiatools.com/mcp/sse?toolId=nsfw-image-detector",
      "command": "",
      "args": [],
      "env": {},
      "isActive": true,
      "type": "sse"
    }
  }
}

List available tools

After connecting to the SSE endpoint, list the exposed tools:

tools/list
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list"
}

Call this tool

Invoke the tool by its id, passing arguments built from its parameters:

tools/call
{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "nsfw-image-detector",
    "arguments": {
  "imageFile": "https://example.com/file.ext",
  "sensitivity": 0.5,
  "analysisMode": "auto"
}
  }
}
Chain multiple tools in one session with a comma-separated toolId list, e.g. /mcp/sse?toolId=png-to-webp,jpg-to-webp,gif-to-webp (max 20).
File parameters accept a public file URL only (https://…). Local paths, data: URIs, and Base64 strings are not supported.

Questions or issues? Contact [email protected]

Browse tools
Open tool