Server data from the Official MCP Registry
Image risk scoring, EXIF, reverse-image backlinks, and image content detection via PicDefense.io.
Image risk scoring, EXIF, reverse-image backlinks, and image content detection via PicDefense.io.
Remote endpoints: streamable-http: https://mcp.picdefense.io/mcp
Valid MCP server (4 strong, 4 medium validity signals). 1 known CVE in dependencies Package registry verified. Imported from the Official MCP Registry.
Endpoint verified · Requires authentication · 3 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: PICDEFENSE_API_TOKEN
Available as Local & Remote
This plugin can run on your machine or connect to a hosted endpoint. during install.
From the project's GitHub README.
A Model Context Protocol server for the PicDefense.io API — let AI agents run reverse-image risk analysis, EXIF extraction, image backlink discovery, and image content detection (face / landmark / logo / label / SafeSearch) on any image URL.
/mcp) and legacy SSE (/sse)/docs| Tool | Description |
|---|---|
picdefense_get_credits | Remaining account credit balance |
picdefense_check_image_risk | Reverse-image risk analysis + picrisk score (core tool) |
picdefense_extract_exif | Extract EXIF metadata (camera, timestamps, GPS) |
picdefense_detect_face | Detect a human face in an image |
picdefense_detect_landmark | Detect a recognizable landmark |
picdefense_detect_logo | Detect a brand logo |
picdefense_safesearch | Content-safety (adult/violence/racy/…) assessment |
picdefense_find_backlinks | Find pages where an image appears |
picdefense_detect_labels | Detect descriptive labels for image contents |
All image tools take a single url (a public http/https image URL). Most tools
consume account credits per call — use picdefense_get_credits to check your balance.
Every request authenticates with your PicDefense API token, which is your user id and API key joined by a colon:
USERID:APIKEY
Find both in your PicDefense.io account settings: https://app.picdefense.io/?returnUrl=https://app.picdefense.io/dashboard/settings
The token is sent as the X-API-TOKEN header to the API (https://app.picdefense.io/api/v2).
The hosted server runs at https://mcp.picdefense.io. Add it to Claude Code:
# Streamable HTTP (recommended)
claude mcp add -t http picdefense "https://mcp.picdefense.io/mcp" \
--header "X-API-Token: USERID:APIKEY"
# or SSE
claude mcp add -t sse picdefense "https://mcp.picdefense.io/sse?token=USERID:APIKEY"
Quick HTTP smoke test:
curl -X POST https://mcp.picdefense.io/mcp \
-H "Content-Type: application/json" \
-H "X-API-Token: USERID:APIKEY" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Claude Desktop launches MCP servers as local commands, so reach the hosted server
through the mcp-remote bridge (requires
Node.js installed). See claude_desktop_config.example.json:
{
"mcpServers": {
"picdefense": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.picdefense.io/sse?token=YOUR_USERID:YOUR_APIKEY"
]
}
}
}
Edit your claude_desktop_config.json (Settings → Developer → Edit Config), add the
mcpServers block above with your USERID:APIKEY, then fully quit and reopen Claude Desktop.
Testing against a plain-HTTP server (e.g.
http://<host>:6910) instead of HTTPS?mcp-remoteblocks non-HTTPS origins unless the host islocalhost— append"--allow-http"to theargsarray, or reach it over an SSH tunnel tolocalhost.
Run the published package directly. Requires Node.js installed.
{
"mcpServers": {
"picdefense": {
"command": "npx",
"args": [
"-y",
"@picdefenseio/mcp-server",
"--api-token",
"USERID:APIKEY"
]
}
}
}
You can also pass the token via the PICDEFENSE_API_TOKEN env var instead of --api-token.
Clone and build, then point Claude Desktop at the built entry point:
git clone https://github.com/rchanllc/picdefenseio-mcp-server.git
cd picdefenseio-mcp-server
npm install
npm run build
Then use "command": "node" with "args": ["/absolute/path/to/dist/index.js", "--api-token", "USERID:APIKEY"].
| Variable | Default | Description |
|---|---|---|
PICDEFENSE_API_TOKEN | — | USERID:APIKEY (stdio only; hosted server reads it per-connection) |
PICDEFENSE_API_BASE_URL | https://app.picdefense.io/api/v2 | API base URL |
PORT | 6910 | Hosted server listen port |
npm run dev:sse # tsx watch, auto-reload
# via docker compose
docker compose up --build -d
# or the helper script (handles build + health check)
./deploy.sh
The container is named picdefenseio_mcp and listens on port 6910.
| Method | Path | Purpose |
|---|---|---|
| GET | /health | Health check (used by Docker + CI) |
| GET | /api/info | Server + transport info |
| GET | /tools | List available tools |
| GET | /docs | Swagger UI for the underlying API |
| GET | /sse?token=USERID:APIKEY | Open an SSE MCP session |
| POST | /messages?sessionId=<id> | SSE session message channel |
| POST | /mcp | Streamable HTTP MCP (header X-API-Token) |
There is no CI/CD in this repo — host it yourself. On your server:
git clone https://github.com/rchanllc/picdefenseio-mcp-server.git
cd picdefenseio-mcp-server
docker compose up --build -d # or: ./deploy.sh
The container is named picdefenseio_mcp and listens on 6910. To update,
git pull and re-run docker compose up --build -d.
Front it with nginx at https://mcp.picdefense.io → 127.0.0.1:6910
(proxy_buffering off and a long read timeout are recommended for the /sse path).
┌──────────────┐ ┌────────────────────────┐ ┌─────────────────────────┐
│ MCP Client │───▶│ PicDefense MCP Server │───▶│ PicDefense.io API v2 │
│ (Claude etc.)│ │ (port 6910) │ │ app.picdefense.io/api/v2│
└──────────────┘ └────────────────────────┘ └─────────────────────────┘
token (USERID:APIKEY) forwarded as X-API-TOKEN ───────────▶
Each connection builds its own API client + MCP server bound to the caller's token, so the service is multi-tenant and stateless with respect to credentials.
MIT — see LICENSE.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.