Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

JPG.now MCP Server

REMOTE · JPG.NOW

Convert JPG images to and from popular formats through MCP-compatible AI clients.

Available components

+4 this week 70 Trust /100

Last scanned (23 hours ago)

Scores higher than 55% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Design and Media

Trust breakdown (7 categories)

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 Security74
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 225 tokens (~56/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 4 Nov 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.

  • 3 Nov 26 +1
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.20 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 2 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: 0.13 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 31 Oct 26 +2
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.10 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 30 Oct 26 0
    • Transport: pass → fail ▼ security
  • 29 Oct 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 28 Oct 26 +33
    • HSTS header: unverified → fail ▼ security
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Tool coverage: 0 functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: fair functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: pass functional
    • First check of Tool coverage: 100 functional
  • 27 Oct 26 33

    First indexed and scored.

Diagnostics

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 4 Nov 2026 · Probed https://jpg.now/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=jpg.now CN=YE1,O=Let's Encrypt,C=US 31 Oct 2026 29 Jan 2027 ECDSA 256 ECDSA-SHA384 59c2934dbbfdffc682dafeb469c75aeb534
SANs: jpg.now
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
CN=ISRG Root X1,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 4 Jun 2015 4 Jun 2035 RSA 4096 SHA256-RSA 8210cfb0d240e3594463e0bb63828b00

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of jpg.now. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
now. present 53572 8 Verified
jpg.now. 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
Header Value
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://jpg.now/mcp Verified 400
http (plaintext) http://jpg.now/mcp HTTPS enforced 301 https://jpg.now/mcp
MCP tools · 4 exposed · ~225 tokens

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 →

Tool Tokens
convert_image_url ~108

Download a publicly accessible image or document URL, submit it to JPG.now using a converter slug, and optionally wait for the result. Private-network URLs and embedded URL credentials are rejected.

NameTypeReqDescription
background_color–––
converterstringyes–
height–––
qualityinteger––
source_urlstringyes–
strip_metadataboolean––
timeout_secondsinteger––
wait_for_completionboolean––
width–––

Structured output declared, but exposes no named fields.

No examples provided.

get_api_usage ~24

Return the caller's JPG.now API credits, usage, and rate limit.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_conversion_status ~35

Check a JPG.now conversion job. A completed job includes an absolute, temporary download URL.

NameTypeReqDescription
job_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

list_converters ~58

Search the live JPG.now converter catalog and return valid converter slugs such as png-to-jpg, jpg-to-webp, pdf-to-jpg, and compress-jpg.

NameTypeReqDescription
limitinteger––
searchstring––

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the JPG.now MCP Server server?

JPG.now MCP Server is a hosted endpoint at https://jpg.now/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 · jpg.now

# add to Claude Code
claude mcp add --transport http chrisyau83-jpg-now 'https://jpg.now/mcp'
Common questions

What is the JPG.now MCP Server server?

JPG.now MCP Server is listed in the public MCP registry as io.github.chrisyau83/jpg-now. Convert JPG images to and from popular formats through MCP-compatible AI clients. This page covers its hosted endpoint (https://jpg.now/mcp).

Is the JPG.now MCP Server server safe to use?

JPG.now MCP Server scores 70 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 JPG.now MCP Server server expose?

JPG.now MCP Server exposes 4 tools: list_converters, convert_image_url, get_conversion_status, get_api_usage. Their descriptions and schemas cost roughly 225 tokens of context every time the server is loaded.

Does the JPG.now MCP Server server require authentication?

No. We connected to JPG.now MCP Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the JPG.now MCP Server server still maintained?

JPG.now MCP Server is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.