# Lumethic Photo Verification (remote · api.lumethic.com)

Verify photos are genuine camera captures, not AI-generated: C2PA checks and RAW+JPEG forensics.

- Trust score: 64/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.lumethic.com`: 64/100 (this document), [markdown](https://verifymcp.io/servers/com-lumethic-verify/api.md), [page](https://verifymcp.io/servers/com-lumethic-verify/api)

## Channel facts

- Endpoint: `https://api.lumethic.com/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-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1208 tokens (~100/item across 12 items; 11 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-lumethic-verify https://api.lumethic.com/mcp
```

### Codex

```toml
[mcp_servers.com-lumethic-verify]
url = "https://api.lumethic.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-lumethic-verify --url https://api.lumethic.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-lumethic-verify:
    url: "https://api.lumethic.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-lumethic-verify": {
      "type": "http",
      "url": "https://api.lumethic.com/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-08-02 (score 64, +1)

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

### 2026-07-31 (score 63, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 62, +1)

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

### 2026-07-28 (score 61, +1)

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

### 2026-07-27 (score 60, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 59)

First indexed and scored.

## MCP tools (11)

### `get_account_usage` (~39 tokens)

Get the authenticated account's monthly verification quota: plan, used, limit, and remaining. Call this before verify_photo to check the free-tier allowance.

### `create_verification_upload` (~66 tokens)

Get pre-signed S3 PUT URLs to upload a large RAW + JPEG directly (avoids inlining bytes and bypasses request-size limits). PUT each file to its upload_url, then call verify_photo with the returned object_key values as raw_object_key / image_object_key.

### `verify_photo` (~182 tokens)

Verify a photo's authenticity from a RAW camera file and its JPEG export. Provide the files either inline as raw_base64 + image_base64 (small files), or — for large files — call create_verification_upload first and pass the returned raw_object_key + image_object_key. Returns a verification id; poll get_verification for the result. With an API key this counts against your monthly quota (free tier: 5/month). Without a key it runs on the keyless anonymous tier (rate-limited; returns an anonymous_user_id to reuse; anonymous verifications can't be listed or shared until you register).

Input parameters:

- `anonymous_user_id`
- `image_base64`
- `image_filename` (string)
- `image_object_key`
- `raw_base64`
- `raw_filename` (string)
- `raw_object_key`

### `verify_content_credentials` (~213 tokens)

Verify a single image's authenticity — use this when you only have the image and no RAW camera file. Checks its embedded Content Credentials (C2PA) for capture provenance and AI-generation flags, and runs advisory forensic screens (error-level analysis, double-JPEG artifacts, EXIF timestamp consistency, editing-software traces, screen recapture). Free: it does not consume your verification quota. Provide the image inline as image_base64, or — for large files — call create_verification_upload and pass the returned image_object_key. Returns a verification id; poll get_verification, which on completion includes a structured evidence_report (verdict, per-check findings, coverage). Works without an API key on the keyless anonymous tier (rate-limited; returns an anonymous_user_id to reuse). For the strongest forensic check, use verify_photo with a RAW + JPEG pair instead.

Input parameters:

- `anonymous_user_id`
- `image_base64`
- `image_filename` (string)
- `image_object_key`

### `get_verification` (~87 tokens)

Retrieve a verification by id: processing status and per-algorithm authenticity results. Completed single-image (image_only) verifications also include a verdict and a structured evidence_report with per-check findings and coverage. Works for both API-key callers (scoped to their account) and keyless anonymous callers (any anonymous verification, which are public by link).

Input parameters:

- `verification_id` (string, required)

### `list_verifications` (~72 tokens)

List the account's verifications, most recent first. Optional filters: status (pending|queued|in_progress|completed|failed) and result (true=authentic, false=not).

Input parameters:

- `offset` (integer)
- `result`
- `size` (integer)
- `status`

### `share_verification` (~89 tokens)

Enable or update sharing for a verification you own. access_type is 'anyone_with_link' (public URL) or 'restricted' (only invited emails). Optionally pass invite_emails to grant access. Returns the share URL and invited emails. Anonymous verifications can't be shared.

Input parameters:

- `access_type` (string, required)
- `invite_emails`
- `verification_id` (string, required)

### `get_verification_share` (~37 tokens)

Get the current sharing configuration (access type, share URL, invited emails) for a verification.

Input parameters:

- `verification_id` (string, required)

### `unshare_verification` (~34 tokens)

Disable sharing for a verification, making it private and invalidating its share link.

Input parameters:

- `verification_id` (string, required)

### `get_listing` (~50 tokens)

Fetch a marketplace listing by id: title, description, per-license pricing, terms, and sales totals. There is no public directory — you must know the listing UUID.

Input parameters:

- `listing_id` (string, required)

### `list_my_listings` (~39 tokens)

List the marketplace listings owned by your account (with pricing and sales totals).

Input parameters:

- `limit` (integer)
- `offset` (integer)

## Diagnostics

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

## Score history

- 2026-08-03: 64
- 2026-08-02: 64
- 2026-08-01: 63
- 2026-07-31: 63
- 2026-07-30: 62
- 2026-07-29: 61
- 2026-07-28: 61
- 2026-07-27: 60
- 2026-07-26: 59

## Links

- Remote endpoint: https://api.lumethic.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-lumethic-verify/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-lumethic-verify/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-lumethic-verify/api