Verified conversions across 205 color spaces: CSS strings, gamut checks, .cube LUTs
SightRadar is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Face recognition: index photos, find a person's photos from a selfie, batches, webhooks, billing.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'SIGHTRADAR_API_KEY=${SIGHTRADAR_API_KEY}' --transport stdio sightradar-mcp '--' npx -y sightradar-mcp
# 2 — ask your agent for something these tools do
# get_balance, get_usage, list_api_keys and 36 more
It needs SIGHTRADAR_API_KEY: this reads it from your environment, so export it first. Remote: OAuth sign-in · Package: API key.
SightRadar costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads SIGHTRADAR_API_KEY (SightRadar API key (frs_...). Create one at https://sightradar.com/dashboard/keys) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx SIGHTRADAR_API_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'SIGHTRADAR_API_KEY=${SIGHTRADAR_API_KEY}' --transport stdio sightradar-mcp '--' npx -y sightradar-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Its publisher also runs it at https://mcp.sightradar.com/mcp: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http sightradar-mcp https://mcp.sightradar.com/mcpIt reaches a system of yours, so it needs your own credential rather than the publisher’s: SIGHTRADAR_API_KEY — SightRadar API key (frs_...). Create one at https://sightradar.com/dashboard/keys. You set it in your own client’s config, on your machine — this marketplace never holds it.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
39 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Current credit balance of the account. 100,000 credits = US$1. Real-time index, search, selfie, detect = 93 credits; compare = 93 per image; batch photo and search_by_point_id = 62. Free.
No parameter schema on file.
Calls and credits spent, per operation. granularity=summary (default) gives totals per op; daily gives a day-by-day series including storage charges; storage gives the daily stored-vector count and storage credits. Use days (1-365) or a from/to date range (YYYY-MM-DD). Free.
No parameter schema on file.
List the account's API keys: id, prefix, name, status, created_at, last_used_at. The secret part is never shown again after creation. Free.
No parameter schema on file.
Create a new API key. The full key (plaintext) is returned ONCE in this answer and cannot be retrieved later: give it to the user and remind them to store it safely. An account can have up to 50 active keys. The account owner gets a security email. Free.
No parameter schema on file.
Revoke an API key immediately; anything using it stops working on its next request. Revoking the key this MCP connection uses disconnects it. Confirm with the user first. Free.
No parameter schema on file.
Account email, name, first/last name and organization name. Free.
No parameter schema on file.
Change the first name, last name or organization shown on the account and invoices. Free.
No parameter schema on file.
Auto-recharge configuration (enabled, threshold_credits, recharge_credits, whether a payment mandate exists, pause state, platform minimums) and recent orders/payments (amount, currency, status, whether an invoice exists). Free.
No parameter schema on file.
Turn automatic top-ups on or off. When the balance drops below threshold_credits the saved payment method is charged for recharge_credits. Enabling needs a saved payment mandate (set up on sightradar.com) and amounts at or above the platform minimums from get_billing_settings. This can charge the…
No parameter schema on file.
Fetch the PDF invoice of a paid order (payment id from get_billing_settings orders). Free.
No parameter schema on file.
Email alert settings (low-balance threshold, daily summary, runway alert) and the extra recipients who get them, with per-recipient categories (billing, webhook_failure). Free.
No parameter schema on file.
Change email alerts. balance_alert_threshold_credits sets the low-balance alert; pass disable_balance_alert=true to turn it off. Fields you omit are unchanged. Free.
No parameter schema on file.
Add, remove or configure an extra email address that receives account alerts. action=add sends a confirmation email the person must click. action=set_category turns one category (billing or webhook_failure) on or off for a recipient. action=remove deletes it. Free.
No parameter schema on file.
People with access to this SightRadar organization and their roles. Inviting, removing and transferring ownership are done by the founder on sightradar.com. Free.
No parameter schema on file.
Queue up to 1000 photo URLs for background processing. op=index stores their faces in the collection; op=match matches them against the collection. Submitting is free; each photo costs 62 credits when it is processed (some accounts pay the real-time 93 for a batch of one photo). The collection is…
No parameter schema on file.
List recent batch jobs newest first with status and succeeded/failed/pending counts. For the next page pass next_before_created and next_before_id from the previous answer. Free.
No parameter schema on file.
Status of one or many batch jobs: status, total_photos, succeeded, failed, pending. Pass batch_id for one, or batch_ids (up to 5000) for many at once; ids you don't own are left out. Free.
No parameter schema on file.
Per-photo results of a batch: external_id, status, face_count and reason_code for failures. Page with after_index = next_after_index. Free.
No parameter schema on file.
Retry batch photos that failed for a given reason, in two steps. First call with execute=false to get a preview: how many photos match, the estimated credit cost and a preview_id (valid 10 minutes, usable once). Show that to the user, then call again with execute=true and the preview_id. Requeued…
No parameter schema on file.
List the face collections on this SightRadar account, with photo, face and selfie counts. Supports substring search and paging. Free.
No parameter schema on file.
Show one collection: status, photo_count, face_count, selfie_count, created_at and purge_after when a deletion is pending. Set verify=true to recount from the vector store instead of the cached counters. Free.
No parameter schema on file.
Create a face collection (for example one per event). Creating one that already exists and is active succeeds without change; one that is being deleted or was deleted returns 409 (use restore_collection or recreate_collection). Indexing into a missing collection also creates it, so this is…
No parameter schema on file.
Delete a collection and every face, selfie and photo record in it. By default this is a SOFT delete: the collection is hidden at once and purged after a 7-day grace period, and restore_collection undoes it until then. immediate=true starts the purge now and cannot be undone. compliance=true…
No parameter schema on file.
Track a collection deletion: phase (not_deleting, deletion_pending, deleting, completed, blocked), whether the data is verified gone (verified_zero), purge_after, attempts and the last error. Free.
No parameter schema on file.
Undo a soft delete while the collection is still in its grace period (status deletion_pending). Fails once the purge has started or for a compliance erasure. Free.
No parameter schema on file.
Bring back an empty collection under the same id after it has been fully deleted (status deleted). The old faces are not recovered. Free.
No parameter schema on file.
Remove every face indexed from one photo. Soft by default (restore_photo undoes it); immediate=true or compliance=true is permanent. Deleting a photo that is already gone still succeeds. Free.
No parameter schema on file.
Undo a soft photo deletion made with delete_photo. Free.
No parameter schema on file.
Detect every face in a photo and store them in a collection so they can be found later by search_faces. Returns each face's point_id, bounding box (ratios of image width/height), detection score and pixel size. Faces below the quality gate (det_score < 0.6 or under 24 px) are counted as rejected.…
No parameter schema on file.
Find the photos in a collection that contain the person in a query image (typically a selfie) or a 512-number embedding. Returns matches [{photo_id, score}] best first, plus photo_ids. When nothing matches, reason says why: no_face (no face found in the query) or low_quality_selfie. Costs 93…
No parameter schema on file.
Find a registered person's photos again without re-sending their selfie: pass the point_id returned by register_selfie for this collection. Cheaper than search_faces. Only selfie point ids (a UUID or an unsigned integer) work here; face point ids from index_photo return reason=point_not_found.…
No parameter schema on file.
Store a user's selfie in a collection so they can be matched against its photos. Returns face_found, the selfie's point_id (use with search_by_point_id) and its 512-number embedding. face_found=false with reason=no_face means no face was found; a face that fails the quality gate (det_score < 0.6…
No parameter schema on file.
Find the faces in an image without storing anything. Returns detected_face_count, gated_face_count (faces that pass the quality gate) and per face: bounding box (ratios), det_score, min_px and quality_passed. Useful to check a photo or selfie before indexing. Costs 93 credits.
No parameter schema on file.
Check whether two images (or embeddings) show the same person. Uses the best face on each side. Returns face_found, similarity (0-1, null when a side has no face), match and the threshold used. Each side is a public URL, a CDN key or a 512-number embedding. Costs 93 credits per image processed:…
No parameter schema on file.
List webhook endpoints (id, url, status, created_at). Optionally filter by status. Free.
No parameter schema on file.
Register a public HTTPS URL to receive batch-completion and deletion events. Each delivery is signed: X-SightRadar-Signature = hex HMAC-SHA256(secret, '<X-SightRadar-Timestamp>.<raw body>'). If you omit secret one is generated and returned ONCE in this answer: tell the user to store it. Free.
No parameter schema on file.
Stop deliveries to a webhook endpoint. Already-disabled endpoints succeed again. Free.
No parameter schema on file.
Deliveries that gave up after all retries (9 attempts): delivery_id, endpoint, url, attempts, last status code and error. Free.
No parameter schema on file.
Send failed deliveries again. Pass delivery_ids to replay specific ones, or omit to replay all of them. Returns how many were requeued. Free.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install SightRadar or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish SightRadar can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.