Lumethic Photo Verification
REMOTE · API.LUMETHIC.COM · SCANNED SEP 20
Verify photos are real camera captures, not AI: C2PA and RAW+JPEG forensics. OAuth or API key.
Available components
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. How we score → Why this is hard to score →
Endpoint Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the Lumethic Photo Verification MCP server?
Lumethic Photo Verification is a hosted endpoint at https://api.lumethic.com/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.
remote · api.lumethic.com
claude mcp add --transport http com-lumethic-verify 'https://api.lumethic.com/mcp'
{
"mcpServers": {
"com-lumethic-verify": {
"url": "https://api.lumethic.com/mcp"
}
}
} {
"servers": {
"com-lumethic-verify": {
"type": "http",
"url": "https://api.lumethic.com/mcp"
}
}
} [mcp_servers.com-lumethic-verify] url = "https://api.lumethic.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-lumethic-verify": {
"type": "remote",
"url": "https://api.lumethic.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-lumethic-verify --url 'https://api.lumethic.com/mcp' --transport streamable-http
mcp_servers:
com-lumethic-verify:
url: "https://api.lumethic.com/mcp" {
"McpServers": {
"com-lumethic-verify": {
"Transport": "http",
"Url": "https://api.lumethic.com/mcp"
}
}
} assistant mcp add com-lumethic-verify -t streamable-http -u 'https://api.lumethic.com/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Sept 26 −41
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: unverified → pass ▲ security
- First check of Authorization: pass security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 3 Sept 26 0
- Tool “list_verifications” rewrote its description, which is the text the model reads security
- New tool “list_tags” functional
- “list_verifications” added an optional parameter “tag_match” cosmetic
- “list_verifications” added an optional parameter “tags” cosmetic
- 30 Aug 26 0
- Schema quality: 1208 → 1396 ▼ functional
- Schema quality: excellent → good functional
- New tool “get_psd_export_status” functional
- New tool “request_psd_export” functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://api.lumethic.com/mcp
TLS valid
Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.lumethic.com | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 8 Jun 2026 | 22 Dec 2026 | RSA 2048 | SHA256-RSA | b89ce2c9c1f1bbbdd2ea333af37d812 |
| SANs: api.lumethic.com | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.lumethic.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| lumethic.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer scope="verifications:read verifications:write shares:write portfolio:write listings:read account:read offline_access", resource_metadata="https://api.lumethic.com/.well-known/oauth-protected-resource/mcp"
Bearer scope="verifications:read verifications:write shares:write portfolio:write listings:read account:read offline_access", resource_metadata="https://api.lumethic.com/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| www-authenticate | Bearer scope="verifications:read verifications:write shares:write portfolio:write listings:read account:read offline_access", resource_metadata="https://api.lumethic.com/.well-known/oauth-protected-resource/mcp" |
Protected resource metadata
| Document | https://api.lumethic.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://api.lumethic.com/mcp |
| Authorisation server | https://api.lumethic.com/ |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.lumethic.com/mcp | Auth required | 401 | |
| http (plaintext) | http://api.lumethic.com/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_verification_upload ~66
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_account_usage ~39
Get the authenticated account's monthly verification quota: plan, used, limit, and remaining. Call this before verify_photo to check the free-tier allowance.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_listing ~50
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.
| Name | Type | Req | Description |
|---|---|---|---|
| listing_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_psd_export_status ~55
Poll the state of a verification's PSD export: status (pending|queued|in_progress|completed|failed), file size, canvas dimensions, downloads used, and download expiry.
| Name | Type | Req | Description |
|---|---|---|---|
| verification_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_verification ~87
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).
| Name | Type | Req | Description |
|---|---|---|---|
| verification_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_verification_share ~37
Get the current sharing configuration (access type, share URL, invited emails) for a verification.
| Name | Type | Req | Description |
|---|---|---|---|
| verification_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_my_listings ~39
List the marketplace listings owned by your account (with pricing and sales totals).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_tags ~60
List the account's tag vocabulary: id, name, colour and how many verifications carry each tag. Tags are assigned in the web app or via PUT /v1/verifications/{id}/tags; pass the names to list_verifications' tags filter.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_verifications ~129
List the account's verifications, most recent first. Optional filters: status (pending|queued|in_progress|completed|failed), result (true=authentic, false=not), tags (list of tag names, case-insensitive) and tag_match ('all' = every listed tag must be on the verification, the default; 'any' = at least one). Use list_tags to discover names.
| Name | Type | Req | Description |
|---|---|---|---|
| offset | integer | – | – |
| result | – | – | – |
| size | integer | – | – |
| status | – | – | – |
| tag_match | string | – | – |
| tags | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
request_psd_export ~133
Request a layered flicker-comparison PSD for a completed RAW+JPEG verification you own: the original photo, the pixel-registered RAW rendition, and the SSIM difference heatmap as layers, for A/B toggling in Photoshop. Professional plan only (monthly allowance included, metered beyond it). Generation is asynchronous — poll get_psd_export_status until status is 'completed', then download the file from the verification page in the web app. Idempotent: re-requesting returns the existing export's state, and a failed export is retried at no extra charge.
| Name | Type | Req | Description |
|---|---|---|---|
| verification_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
share_verification ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| access_type | string | yes | – |
| invite_emails | – | – | – |
| verification_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
unshare_verification ~34
Disable sharing for a verification, making it private and invalidating its share link.
| Name | Type | Req | Description |
|---|---|---|---|
| verification_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
verify_content_credentials ~213
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.
| Name | Type | Req | Description |
|---|---|---|---|
| anonymous_user_id | – | – | – |
| image_base64 | – | – | – |
| image_filename | string | – | – |
| image_object_key | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
verify_photo ~182
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).
| Name | Type | Req | Description |
|---|---|---|---|
| anonymous_user_id | – | – | – |
| image_base64 | – | – | – |
| image_filename | string | – | – |
| image_object_key | – | – | – |
| raw_base64 | – | – | – |
| raw_filename | string | – | – |
| raw_object_key | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Lumethic Photo Verification MCP server?
Lumethic Photo Verification is an MCP server listed in the public MCP registry as com.lumethic/verify. Verify photos are real camera captures, not AI: C2PA and RAW+JPEG forensics. OAuth or API key. This page covers its hosted endpoint (https://api.lumethic.com/mcp).
Is the Lumethic Photo Verification MCP server safe to use?
Lumethic Photo Verification scores 37 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 Lumethic Photo Verification MCP server expose?
Lumethic Photo Verification exposes 14 tools: get_account_usage, create_verification_upload, verify_photo, verify_content_credentials, get_verification, and 9 more. Their descriptions and schemas cost roughly 1,213 tokens of context every time the server is loaded.
Does the Lumethic Photo Verification MCP server require authentication?
Yes. Lumethic Photo Verification asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Lumethic Photo Verification MCP server still maintained?
Lumethic Photo Verification is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.