CraterView.ai
REMOTE · MCP.CRATERVIEW.AI
Enlarge, denoise and restore photos, or check if one was made by AI, on your CraterView.ai account.
Available components
Last scanned (20 hours ago)
Scores higher than 71% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Design and Media
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 Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4609 tokens (~307/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 0
- Schema quality: 342 → 307 ▲ functional
- Stability: unverified → 0.03 ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 20 Nov 26 +39
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 100 functional
- First check of Tool coverage: 100 functional
- 6 Nov 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
- 17 Oct 26 0
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 21 Nov 2026 · Probed https://mcp.craterview.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=craterview.ai | CN=WE1,O=Google Trust Services,C=US | 23 Oct 2026 | 21 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | c3d7034e823e5662136b15287f1d04a4 |
| SANs: craterview.ai, mcp.craterview.ai, *.mcp.craterview.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.craterview.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| craterview.ai. | No DS | 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 tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://mcp.craterview.ai/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://mcp.craterview.ai/.well-known/oauth-protected-resource/mcp" | Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| x-content-type-options | nosniff |
Protected resource metadata
| Document | https://mcp.craterview.ai/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.craterview.ai/mcp |
| Authorisation server | https://mcp.craterview.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.craterview.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.craterview.ai/mcp | HTTPS enforced | 301 | https://mcp.craterview.ai/mcp |
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 →
check_content ~245
Content Check (cv-content-check-v1, free): Screens an image against the service's content policy without changing it. `job.result.verdict` (`passed`, `flagged`): `flagged` when the image may fall outside what the service allows, `passed` when it was checked and nothing was found. The same answer as the job's `flagged` field. This check changes nothing and costs nothing, so it needs no go-ahead: call it when its answer would help, and say what it found. Send the image as `input_key`: upload_photo answers with one. An answer's `job` is the job as the API states it. On a finished job, `usage` is the account as get_usage answers it. Most images finish inside this call, with the answer in `job.result`. A slower one answers with `job.status` queued or running: collect it with get_job and `job.id`. Calling this tool again would run the work again.
| Name | Type | Req | Description |
|---|---|---|---|
| input_key | string | yes | The image: the `input_key` upload_photo answered with, or a File ID the user copied from their CraterView.ai workspace. |
No output schema declared.
No examples provided.
check_real ~246
Real Check (cv-real-check-v2, free): Estimates whether an image was produced by a generative model (`generated`) rather than captured by a camera (`real`). `job.result.verdict` (`generated`, `real`, `uncertain`): Which way the evidence points. `job.result.generated_probability`: The estimated probability that the image was generated, from 0 to 1. This check changes nothing and costs nothing, so it needs no go-ahead: call it when its answer would help, and say what it found. Send the image as `input_key`: upload_photo answers with one. An answer's `job` is the job as the API states it. On a finished job, `usage` is the account as get_usage answers it. Most images finish inside this call, with the answer in `job.result`. A slower one answers with `job.status` queued or running: collect it with get_job and `job.id`. Calling this tool again would run the work again.
| Name | Type | Req | Description |
|---|---|---|---|
| input_key | string | yes | The image: the `input_key` upload_photo answered with, or a File ID the user copied from their CraterView.ai workspace. |
No output schema declared.
No examples provided.
delete_job_media ~117
Delete this job's images now — the copy of your image the job worked from, the result, its preview, and any kept copy — rather than waiting for them to expire on schedule. A job you shared leaves the gallery with them. The file you uploaded is not part of the job: it is deleted on its own, shortly after the upload. Not reversible: call this only after the user has said to.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job's `id`, from the tool that ran it or from list_jobs. |
No output schema declared.
No examples provided.
denoise_photo ~421
Denoise (cv-denoise-v1, 1 credit an image): Removes noise and grain from a photograph taken in low light or at a high ISO, without enlarging it, and does that much better than Enhance's binning. Suggest it beside Enhance, which is the first to try even on a grainy photograph; on its own, it is for someone who wants only the noise gone. The photograph or region comes back at its own size. To make a noisy photograph larger, use Enhance with binning on the original instead: it might not work well on this model's result. Only the user starts a run: call this only after they have said to, free jobs too. "Make this sharper" asks for a result, not a run: say what you would use and what it will cost, then wait. `quote` runs nothing and is free: call it without asking. Send the image as `input_key`: upload_photo answers with one. An answer's `job` is the job as the API states it. On a finished job, `usage` is the account as get_usage answers it. Most images finish inside this call, with links in `job.result.output` and a small preview of the result to check it by. A slower one answers with `job.status` queued or running: collect it with get_job and `job.id`. Calling this tool again would run the work and charge for it twice.
| Name | Type | Req | Description |
|---|---|---|---|
| input_key | string | yes | The image: the `input_key` upload_photo answered with, or a File ID the user copied from their CraterView.ai workspace. |
| params | object | – | Settings for this model. Leave out anything not asked for: each has a default. roi: **look at the image and name the subject.** Everything outside it is discarded, so what comes back is made from th… |
No output schema declared.
No examples provided.
enhance_photo ~583
Enhance (cv-enhance-v3, 1 credit an image up to 6 MP, 2 credits above): Makes a photograph sharper and rebuilds fine detail enlarged up to 4 times. It is the model to suggest first for almost any photograph someone wants improved, a grainy one included. Suggest trying Denoise as well. If the photograph is noisy and being enlarged, set binning for simple noise reduction: pixel binning averages each square of 2x2, 3x3 or 4x4 pixels into one before enlarging, which takes noise out and leaves less room to enlarge. Strongly recommended: run it on the original photograph, before Denoise or Restore, because it might not work well on another model's result. Among the photographs it is right for: a soft scan, a small or cropped photograph, and anything the compression flattened. A price in MP counts the part of the image worked on, the whole image or the region sent, divided by 4 at binning 2x2, 9 at 3x3 and 16 at 4x4. Only the user starts a run: call this only after they have said to, free jobs too. "Make this sharper" asks for a result, not a run: say what you would use and what it will cost, then wait. `quote` runs nothing and is free: call it without asking. Send the image as `input_key`: upload_photo answers with one. An answer's `job` is the job as the API states it. On a finished job, `usage` is the account as get_usage answers it. Most images finish inside this call, with links in `job.result.output` and a small preview of the result to check it by. A slower one answers with `job.status` queued or running: collect it with get_job and `job.id`. Calling this tool again would run the work and charge for it twice.
| Name | Type | Req | Description |
|---|---|---|---|
| input_key | string | yes | The image: the `input_key` upload_photo answered with, or a File ID the user copied from their CraterView.ai workspace. |
| params | object | – | Settings for this model. Leave out anything not asked for: each has a default. scale: left out, the largest factor whose result fits inside the model's size limit for this account is used — not the… |
No output schema declared.
No examples provided.
get_job ~159
Read a CraterView.ai job: the result of one that had not finished, or fresh links to one that has. Call this when a tool that runs a job returned a status of queued or running. It waits up to 25 seconds for the job to finish before answering, so there is no need to pause between calls: if it answers that the job is still queued or running, call it again. `flagged`: Whether an automated check thought this job's images may fall outside what the service allows. A flag is a warning and does not stop the job. `null` means the images were not all checked.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job's `id`, from the tool that ran it or from list_jobs. |
No output schema declared.
No examples provided.
get_usage ~256
The account's subscription status, credit balance, and which queue your next job goes to. `community`: Whether your next job runs free on the community queue: smaller size limits on some models and longer waits at busy times. True without credit or a subscription, or once a limited subscription's monthly allowance is spent. Otherwise the job runs on paid compute. `subscribed`: Whether the account has a live subscription, limited or unlimited. Stays true even after a limited subscription's credit allowance is spent. Read `community` to know if the next job would go to the free community queue or to the faster paid queue. `credits_remaining` and `subscription_allowance_remaining`: Credits and subscription allowance remaining for the faster paid queue. Neither goes below zero. Zero does not block work, and no top-up is needed to run jobs. Read `community` to know if the next job would go to the free community queue or to the faster paid queue. `subscription_allowance`: Allowance a limited subscription adds every month for paid compute. Null for an unlimited subscription or none. It adds nothing to `credits_remaining`. The user buys credit or a subscription at https://craterview.ai/dashboard#buy; no tool buys anything.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
keep_job_media ~78
Retain this job's images past the ordinary expiry, because the owner asked. To stop keeping them, the user does that in their job history at https://craterview.ai/dashboard; delete_job_media removes them now.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job's `id`, from the tool that ran it or from list_jobs. |
No output schema declared.
No examples provided.
list_jobs ~122
Your jobs, most recent first. `flagged`: Whether an automated check thought this job's images may fall outside what the service allows. A flag is a warning and does not stop the job. `null` means the images were not all checked. Use get_job with its `id` for more detail, such as the job's image links.
| Name | Type | Req | Description |
|---|---|---|---|
| before | string | – | Lists jobs older than this one: the answer's `next_before`, for the next page. |
| limit | integer | – | How many jobs to list; 5 if left out. |
No output schema declared.
No examples provided.
make_headshot ~329
Headshot (cv-headshot-v1, 1 credit an image): Turns a photograph with a face in it into a professional headshot. Only the user starts a run: call this only after they have said to, free jobs too. "Make this sharper" asks for a result, not a run: say what you would use and what it will cost, then wait. `quote` runs nothing and is free: call it without asking. Send the image as `input_key`: upload_photo answers with one. An answer's `job` is the job as the API states it. On a finished job, `usage` is the account as get_usage answers it. Most images finish inside this call, with links in `job.result.output` and a small preview of the result to check it by. A slower one answers with `job.status` queued or running: collect it with get_job and `job.id`. Calling this tool again would run the work and charge for it twice.
| Name | Type | Req | Description |
|---|---|---|---|
| input_key | string | yes | The image: the `input_key` upload_photo answered with, or a File ID the user copied from their CraterView.ai workspace. |
| params | object | – | Settings for this model. Leave out anything not asked for: each has a default. roi: **look at the image and name the subject.** Everything outside it is discarded, so what comes back is made from th… |
No output schema declared.
No examples provided.
quote ~373
Quote a CraterView.ai job without running it: what it would charge for this image, the settings it would send and, for an enlargement by scale, the result's size in megapixels. It never uploads, queues or charges anything. Send the model and the params its tool would be sent, and the image as `input_key` — or, in place of it, image_width and image_height, which prices a file still on the user's computer without taking it off. For a link, call upload_photo first, which needs no asking. An answer's `quote` is the quote as POST /v1/quotes states it, and `quote.params` is what to send the tool. `credits_at_most`: In place of `credits`, where the price is not known yet: the most the job can be charged. A model priced by the faces it redraws knows only after the run, and a price by size needs the image's size.
| Name | Type | Req | Description |
|---|---|---|---|
| image_height | integer | – | In place of the image: the image file's height in pixels. |
| image_width | integer | – | In place of the image: the image file's width in pixels. |
| input_key | string | – | The image: the `input_key` upload_photo answered with, or a File ID the user copied from their CraterView.ai workspace. |
| model | string | yes | The model the job would run: cv-enhance-v3 is enhance_photo, cv-faces-v1 is redraw_small_faces, cv-headshot-v1 is make_headshot, cv-denoise-v1 is denoise_photo, cv-restore-v1 is restore_photo, cv-con… |
| params | object | – | The params that tool would be sent. |
No output schema declared.
No examples provided.
redraw_small_faces ~319
Small face enhancement (cv-faces-v1, 1 credit an image up to 6 faces redrawn, 2 credits above): Makes small, blurry or distorted faces look natural. For the people in a group photograph whose faces came out small and distorted after enlarging: run it on the enlarged result rather than the original. An image with no face small enough is refused and costs nothing. Only the user starts a run: call this only after they have said to, free jobs too. "Make this sharper" asks for a result, not a run: say what you would use and what it will cost, then wait. `quote` runs nothing and is free: call it without asking. Send the image as `input_key`: upload_photo answers with one. An answer's `job` is the job as the API states it. On a finished job, `usage` is the account as get_usage answers it. Most images finish inside this call, with links in `job.result.output` and a small preview of the result to check it by. A slower one answers with `job.status` queued or running: collect it with get_job and `job.id`. Calling this tool again would run the work and charge for it twice.
| Name | Type | Req | Description |
|---|---|---|---|
| input_key | string | yes | The image: the `input_key` upload_photo answered with, or a File ID the user copied from their CraterView.ai workspace. |
| params | object | – | Settings for this model. Leave out anything not asked for: each has a default. |
No output schema declared.
No examples provided.
restore_photo ~436
Restore (cv-restore-v1, 1 credit an image): Tears, creases, scratches, dust and grain are removed and washed-out colour is corrected. The photograph comes back at its own size, or enlarged up to 4 times with scale. Prefer enhance_photo for enlargements and try denoise_photo for very noisy images. Before a black-and-white photograph of people is returned in colour, ask the user who is in it and what they know of its colours, and send that as `context`. Without `context`, every colour, skin tone and damaged detail is a guess. Only the user starts a run: call this only after they have said to, free jobs too. "Make this sharper" asks for a result, not a run: say what you would use and what it will cost, then wait. `quote` runs nothing and is free: call it without asking. Send the image as `input_key`: upload_photo answers with one. An answer's `job` is the job as the API states it. On a finished job, `usage` is the account as get_usage answers it. Most images finish inside this call, with links in `job.result.output` and a small preview of the result to check it by. A slower one answers with `job.status` queued or running: collect it with get_job and `job.id`. Calling this tool again would run the work and charge for it twice.
| Name | Type | Req | Description |
|---|---|---|---|
| input_key | string | yes | The image: the `input_key` upload_photo answered with, or a File ID the user copied from their CraterView.ai workspace. |
| params | object | – | Settings for this model. Leave out anything not asked for: each has a default. roi: **look at the image and name the subject.** Everything outside it is discarded, so what comes back is made from th… |
No output schema declared.
No examples provided.
upload_photo ~393
Makes an image available for viewing and jobs. Returns the image's `input_key`. Runs nothing and charges nothing. Give one of: - image_url, for an image already online. - content_type and content_length, for a file on this computer that your shell can read. The answer has a `curl` command that sends it straight to storage, and the file is there once that has succeeded. - job_id, for the result file from another job. - image_base64, only for a very small file you cannot send any other way. If you cannot send the image, because you can only see it in this conversation or your shell cannot reach storage, ask the user to choose the photo at https://craterview.ai/app and give you its File ID, which is the `input_key`, or for a link to it. The `input_key` is valid for a day after the image was uploaded.
| Name | Type | Req | Description |
|---|---|---|---|
| content_length | integer | – | For a file on this computer, with content_type: its exact size in bytes, read in your shell so the image never enters your context. Limit is 300MB. |
| content_type | string | – | For a file on this computer, with content_length: the file's type. |
| image_base64 | string | – | A base64-encoded image file. Limit is 8MB decoded. This is in your context and potentially costs several million tokens. Only for a small file you cannot send any other way. An image you can only see… |
| image_url | string | – | A public or signed http(s) link to a PNG, JPEG, WebP, HEIC, HEIF or TIFF image. Limit is 300MB. |
| job_id | string | – | The job `id` of the result to make available for viewing and further jobs. |
No output schema declared.
No examples provided.
view_photo ~280
Look at an image: an upload or a finished job's result, the whole of it or a part, as an image you can see. Accepts `input_key` or `job_id`. Each look is a free job, needs no go-ahead and is not shown on the user's dashboard. Look at the whole image first and then look closer. Each result includes the region of interest (`roi`) of the current view in fractions of the whole image, ready to send to a job. To look closer, set `within` to your current view and select `roi` as fractions within the current view. Repeat to zoom further.
| Name | Type | Req | Description |
|---|---|---|---|
| input_key | string | – | The image: the `input_key` upload_photo answered with, or a File ID the user copied from their CraterView.ai workspace. |
| job_id | string | – | A finished job's `id`, to look at its result. |
| max_side | integer | – | If needed, the returned view will be scaled down to have width and height within `max_side`. |
| roi | object | – | The region of the image to look at, as fractions of the width and height (from top left) of either the entire image or of another region in `within`. |
| within | object | – | The reference `roi`, typically one an earlier answer returned for this image. |
No output schema declared.
No examples provided.
How do I install the CraterView.ai MCP server?
CraterView.ai is a hosted endpoint at https://mcp.craterview.ai/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 · mcp.craterview.ai
claude mcp add --transport http ai-craterview-mcp 'https://mcp.craterview.ai/mcp'
What is the CraterView.ai MCP server?
CraterView.ai is an MCP server listed in the public MCP registry as ai.craterview/mcp. Enlarge, denoise and restore photos, or check if one was made by AI, on your CraterView.ai account. This page covers its hosted endpoint (https://mcp.craterview.ai/mcp).
Is the CraterView.ai MCP server safe to use?
CraterView.ai scores 78 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 CraterView.ai MCP server expose?
CraterView.ai exposes 15 tools: upload_photo, enhance_photo, redraw_small_faces, make_headshot, denoise_photo, and 10 more. Their descriptions and schemas cost roughly 4,357 tokens of context every time the server is loaded.
Does the CraterView.ai MCP server require authentication?
Yes. CraterView.ai 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 CraterView.ai MCP server still maintained?
CraterView.ai is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the CraterView.ai MCP server?
VerifyMCP ran 13 checks on CraterView.ai, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.