Model Context Protocol

Verify photo authenticity from any AI agent

Lumethic ships a remote MCP server, so AI agents can check whether a photo is a real, unmodified camera capture — directly inside their toolchain. No SDK to install: point your client at the endpoint and call the tools.

Endpoint

Connect over Streamable HTTP

The server speaks the Model Context Protocol over a Streamable HTTP endpoint. It is stateless, so no session affinity is required.

Production

https://api.lumethic.com/mcp

Transport: Streamable HTTP

Authentication

API key or keyless anonymous tier

Create an API key once and pass it on every request. You can also call the server with no key at all to try it out on the rate-limited anonymous tier.

Authorization header

Send your key as a Bearer token: Authorization: Bearer lk_… — this is what Claude's mcp_servers connector sends via its authorization_token field.

X-API-Key header

Alternatively, pass the key in an X-API-Key: lk_… header.

Keyless anonymous tier

Call the server with no credentials to evaluate it. This tier is rate-limited and meant for trying things out before you register.

Create an API key

Quick start

Connect your client

Add the server to your preferred MCP client. Replace lk_… with your own API key.

Claude Code

claude mcp add --transport http lumethic \
  https://api.lumethic.com/mcp \
  --header "X-API-Key: lk_..."

Claude Messages API

"mcp_servers": [
  {
    "type": "url",
    "name": "lumethic",
    "url": "https://api.lumethic.com/mcp",
    "authorization_token": "lk_..."
  }
]

Python (MCP SDK)

from mcp.client.streamable_http import streamablehttp_client

async with streamablehttp_client(
    "https://api.lumethic.com/mcp",
    headers={"X-API-Key": "lk_..."},
) as (read, write, _):
    ...

Toolset

What agents can call

Once connected, agents have the following tools available. Verification tools work on the anonymous tier; account and marketplace tools require an API key.

verify_photoVerify a photo by passing a RAW file and its JPEG export (inline base64 for small files).

create_verification_uploadGet pre-signed S3 URLs for large RAW files, PUT the bytes directly, then pass the returned object keys to verify_photo.

get_verificationFetch a verification by id; poll until status is completed to read the authenticity result.

list_verificationsList the verifications on your account. Requires an API key.

get_account_usageReport your plan plus used and remaining verifications. Requires an API key.

share_verificationCreate a public share link for a verification.

get_verification_shareRead the current public share state of a verification.

unshare_verificationRevoke a verification's public share link.

get_listingRead a single marketplace listing.

list_my_listingsList your own marketplace listings.

Resource

lumethic://pricing — describes the available plans and their limits.

Workflow

From upload to verdict

A typical authenticity check runs in four steps.

Connect

Point your MCP client at the endpoint and authenticate with an API key (or use the anonymous tier).

Upload

Call verify_photo with the RAW file and its JPEG export. For large RAW files, call create_verification_upload first, PUT the bytes to the pre-signed URLs, then pass the returned object keys.

Poll

Call get_verification by id until status is completed. Processing typically takes a few minutes.

Read the result

Read the authenticity verdict and confidence. A pass is strong evidence the photo is a genuine, unmodified capture.

Error handling

Machine-readable error codes

Tool errors come back with machine-readable codes, so an agent can react and, when needed, prompt the user to register or upgrade.

QUOTA_EXCEEDEDThe plan's verification quota is used up. Prompt the user to register or upgrade.

INVALID_CREDENTIALSThe API key is missing or invalid. Check the Authorization or X-API-Key header.

RATE_LIMIT_EXCEEDEDToo many requests on the keyless anonymous tier. Add an API key or slow down.

Ready to connect an agent?

Create an API key in your dashboard, then point your MCP client at the endpoint. Prefer raw HTTP? The REST API exposes the same verification engine.

Create an API key REST API docs