Lumethic Photo Verification
REMOTE · API.LUMETHIC.COM · SCANNED AUG 3
Verify photos are genuine camera captures, not AI-generated: C2PA checks and RAW+JPEG forensics.
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1208 tokens (~100/item across 12 items; 11 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.lumethic.com
claude mcp add --transport http com-lumethic-verify 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": {
"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.
- 2 Aug 26 +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.
- 31 Jul 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
- 30 Jul 26 +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.
- 28 Jul 26 +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.
- 27 Jul 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
- 26 Jul 26 59
First indexed and scored.
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 3 Aug 2026 · Probed https://api.lumethic.com/mcp/ · Declared URL 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 |
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 No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 3 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.lumethic.com/mcp | Redirected | 307 | https://api.lumethic.com/mcp/ |
| streamable-http · followed | https://api.lumethic.com/mcp/ | Verified | 200 | |
| 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.
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_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_verifications ~72
List the account's verifications, most recent first. Optional filters: status (pending|queued|in_progress|completed|failed) and result (true=authentic, false=not).
| Name | Type | Req | Description |
|---|---|---|---|
| offset | integer | — | — |
| result | — | — | — |
| size | integer | — | — |
| status | — | — | — |
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.