CraterView.ai MCP server
ai.craterview/mcpcraterview.aistreamable-httpv5.1.0Scanned
Enlarge, denoise and restore photos, or check if one was made by AI, on your CraterView.ai account.
15 tools: 1 can delete or cancel things, 10 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the CraterView.ai MCP server can do
The CraterView.ai MCP server is published by craterview.ai, a domain the MCP Registry verified. It has 15 tools. It can delete or cancel things (1 tool: delete_job_media) and create or change data (10 tools: upload_photo, enhance_photo, redraw_small_faces, make_headshot and 6 more). 4 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 21, 2026, version 5.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
15 tools
Deletes or cancels 1Claude Code: deny
delete_job_mediaDelete 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.No findings
Why it is in this group
- The name "delete_job_media" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: true
- idempotentHint: true
Changes things 10Claude Code: ask
check_contentContent Check (cv-content-check-v1, free): Screens an image against the service's content policy without changing it.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
check_realReal Check (cv-real-check-v2, free): Estimates whether an image was produced by a generative model (`generated`) rather than captured by a camera (`real`).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
denoise_photoDenoise (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 Enha…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
enhance_photoEnhance (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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
keep_job_mediaRetain this job's images past the ordinary expiry, because the owner asked.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
make_headshotHeadshot (cv-headshot-v1, 1 credit an image): Turns a photograph with a face in it into a professional headshot.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
quoteQuote 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
redraw_small_facesSmall 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
restore_photoRestore (cv-restore-v1, 1 credit an image): Tears, creases, scratches, dust and grain are removed and washed-out colour is corrected.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
upload_photoMakes an image available for viewing and jobs.No findings
Why it is in this group
- The name "upload_photo" says "upload": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
Only reads 4Show 4 read-only tools
get_jobRead a CraterView.ai job: the result of one that had not finished, or fresh links to one that has.No findings
Why it is in this group
- The name "get_job" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
get_usageThe account's subscription status, credit balance, and which queue your next job goes to.No findings
Why it is in this group
- The name "get_usage" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
list_jobsYour jobs, most recent first.No findings
Why it is in this group
- The name "list_jobs" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
view_photoLook at an image: an upload or a finished job's result, the whole of it or a part, as an image you can see.No findings
Why it is in this group
- The name "view_photo" says "view": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:25 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 11
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.craterview.ai/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://mcp.craterview.ai
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 11 tools that change things (1 destructive, 10 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.craterview.ai/mcp: tools/list returned 15 tools to an anonymous client, including delete_job_media (destructive), upload_photo (write), enhance_photo (write), redraw_small_faces (write), make_headshot (write) and 6 more
Posture changes
- Nov 20, 2026
- HTTP status of an anonymous initialize: 401 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 11
- Protocol version: none to 2025-06-18
- WWW-Authenticate on 401: yes to not observed
- resource_metadata in WWW-Authenticate: https://mcp.craterview.ai/.well-known/oauth-protected-resource/mcp to none
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 401 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 11 (and 3 more).View diff
- HTTP status of an anonymous initialize: 401 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 11
- Protocol version: none to 2025-06-18
- WWW-Authenticate on 401: yes to not observed
- resource_metadata in WWW-Authenticate: https://mcp.craterview.ai/.well-known/oauth-protected-resource/mcp to none
Install
Pinned to version 5.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http craterview https://mcp.craterview.ai/mcpclaude mcp add --transport http craterview https://mcp.craterview.ai/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__craterview__view_photo",
"mcp__craterview__get_job",
"mcp__craterview__get_usage",
"mcp__craterview__list_jobs"
],
"ask": [
"mcp__craterview__upload_photo",
"mcp__craterview__enhance_photo",
"mcp__craterview__redraw_small_faces",
"mcp__craterview__make_headshot",
"mcp__craterview__denoise_photo",
"mcp__craterview__restore_photo",
"mcp__craterview__check_content",
"mcp__craterview__check_real",
"mcp__craterview__quote",
"mcp__craterview__keep_job_media"
],
"deny": [
"mcp__craterview__delete_job_media"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as craterview. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/ai.craterview/mcp/verify?hash=ef08214fd295dc939e1175d5ef2b8bf157913ca2b0682c312a15306076d019e8" | jq -e '.changed == false'Pinned hash ef08214fd295, from Nov 21, 2026, 01:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.craterview/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.craterview/mcp)Source: MCP Registry. Synced Nov 21, 2026, 01:17 UTC.
CraterView.ai MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the CraterView.ai MCP server safe?
- No scan can promise that. What its definitions show: 15 tools, 11 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the CraterView.ai MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: delete_job_media.
Can the CraterView.ai MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the CraterView.ai MCP server have?
- 15 tools: 1 destructive, 10 write, 4 read. delete_job_media, upload_photo, enhance_photo, redraw_small_faces, make_headshot, denoise_photo, restore_photo, check_content and 7 more.
Does the CraterView.ai MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the CraterView.ai MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the CraterView.ai MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.