# SocialShot AI (remote · api.socialshot.ai)

AI product photos for ecommerce: turn product images into studio, lifestyle and on-model photos.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `api.socialshot.ai`: 74/100 (this document), [markdown](https://verifymcp.io/servers/ai-socialshot-socialshot/api.md), [page](https://verifymcp.io/servers/ai-socialshot-socialshot/api)

## Channel facts

- Endpoint: `https://api.socialshot.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 798 tokens (~159/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 80/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 41% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the SocialShot AI MCP server?

SocialShot AI is a hosted endpoint at https://api.socialshot.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ai-socialshot-socialshot 'https://api.socialshot.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-socialshot-socialshot": {
      "url": "https://api.socialshot.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-socialshot-socialshot": {
      "type": "http",
      "url": "https://api.socialshot.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-socialshot-socialshot]
url = "https://api.socialshot.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-socialshot-socialshot": {
      "type": "remote",
      "url": "https://api.socialshot.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-socialshot-socialshot --url 'https://api.socialshot.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-socialshot-socialshot:
    url: "https://api.socialshot.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-socialshot-socialshot": {
      "Transport": "http",
      "Url": "https://api.socialshot.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-socialshot-socialshot -t streamable-http -u 'https://api.socialshot.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-socialshot-socialshot": {
      "type": "http",
      "url": "https://api.socialshot.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 69, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-09 (score 68)

First indexed and scored.

## MCP tools (5)

### `get_account` (~48 tokens)

Get SocialShot account

Shop metadata, plan, credit balance and dailyCap {used, limit, resetsAt} (the rolling 24-hour API credit cap) for this API key. Free; call before spending credits.

### `list_options` (~21 tokens)

List generation options

Catalog of accepted generation options (currently the output tiers). Free.

### `create_photoshoot_batch` (~477 tokens)

Create photoshoot batch

COSTS MONEY: every successful submission spends real, paid credits from the account's SocialShot balance (about credits_estimated in the result; higher tier / output_quality cost more). Only call it when the user has asked for images to be generated, and check get_account (credits, dailyCap) first. Queues AI product-photoshoot generation for 1-50 publicly reachable product image URLs (one output each) and returns batch_id, total and credits_estimated immediately; poll with wait_for_job or get_job. Identical inputs never charge twice: they reuse an idempotency_key derived from the inputs, so the server replays the ORIGINAL batch (idempotent_replay: true) and no new images are made. Pass force_new: true only when the user explicitly wants a new, separately charged run of the same inputs.

Input parameters:

- `angle` (string)
- `aspect_ratio` (string)
- `backdrop` (string): Studio backdrop colour (default "white").
- `backdrop_id` (string)
- `background` (string): Scene background (default "urban street").
- `background_id` (string)
- `brand_name` (string)
- `composition` (string)
- `defaults` (object): Batch-wide overrides applied to every item.
- `force_new` (boolean): Start a new, separately charged batch even though identical inputs ran before. Only on the user's explicit request.
- `garment_fit` (string)
- `idempotency_key` (string): Optional. Reuse to safely retry the same request; derived from the inputs if omitted.
- `include_human_model` (boolean): On-model shot (default true).
- `items` (array, required): 1-50 product images; one output image each.
- `lighting` (string)
- `logo_alignment` (string)
- `logo_enabled` (boolean)
- `output_quality` (string): 1k (default), 2k or 4k. Higher costs more credits.
- `pose` (string)
- `product_category` (string)
- `scene_type` (string, required): studio = clean backdrop; lifestyle = styled scene.
- `style_mood` (string)
- `tier` (string): economy (default), standard or premium. Higher tiers cost more credits.

### `get_job` (~63 tokens)

Get batch status

Status of a photoshoot batch: per-item status and output_url. The batch is done when `settled` >= `expected_total`. `total` only counts rows written so far, so it can lag while the queue drains.

Input parameters:

- `batch_id` (string, required)

### `wait_for_job` (~101 tokens)

Wait for batch

Poll a batch (backoff 2s up to 10s) until every item is completed or failed, or until timeout. Pass expected_total (the `total` from create_photoshoot_batch) until the server reports its own. On timeout returns done=false with the latest status; call again to keep waiting.

Input parameters:

- `batch_id` (string, required)
- `expected_total` (integer)
- `timeout_seconds` (integer): Default 50.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-socialshot-socialshot/api#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 73
- 2026-11-19: 73
- 2026-11-18: 72
- 2026-11-17: 72
- 2026-11-16: 71
- 2026-11-15: 71
- 2026-11-14: 71
- 2026-11-13: 70
- 2026-11-12: 70
- 2026-11-11: 69
- 2026-11-10: 69
- 2026-11-09: 68

## Common questions

### What is the SocialShot AI MCP server?

SocialShot AI is an MCP server listed in the public MCP registry as ai.socialshot/socialshot. AI product photos for ecommerce: turn product images into studio, lifestyle and on-model photos. This page covers its hosted endpoint (https://api.socialshot.ai/mcp).

### Is the SocialShot AI MCP server safe to use?

SocialShot AI scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the SocialShot AI MCP server expose?

SocialShot AI exposes 5 tools: get_account, list_options, create_photoshoot_batch, get_job, wait_for_job. Their descriptions and schemas cost roughly 710 tokens of context every time the server is loaded.

### Does the SocialShot AI MCP server require authentication?

No. We connected to SocialShot AI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SocialShot AI MCP server still maintained?

SocialShot AI is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the SocialShot AI MCP server?

VerifyMCP ran 13 checks on SocialShot AI, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.socialshot.ai/mcp
- Authorisation metadata: https://api.socialshot.ai/.well-known/oauth-protected-resource/mcp
- Website: https://socialshot.ai/developers
- Changelog RSS feed: https://verifymcp.io/servers/ai-socialshot-socialshot/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-socialshot-socialshot/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-socialshot-socialshot/api.json
- HTML version of this page: https://verifymcp.io/servers/ai-socialshot-socialshot/api
