John's Essentials
REMOTE · API.JOHNSESSENTIALS.COM
144 deterministic file tools: PDF, image, media, convert, analyze. Connect in one click (OAuth).
Available components
Last scanned (9 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Documents and Files
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
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. 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 Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 28822 tokens (~184/item across 156 items; 153 tools + 3 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 155 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.
- 30 Oct 26 0
- Stability: fail → pass ▲ security
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 97.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90.
- 30 Sept 26 0
- A breaking change shipped without a version bump: still 1.2.0 ▼ security
- “email_file” changed the type of “file”: string → array ▼ functional
- “email_file” reworded the description of “file” cosmetic
- “photo_face_blur” reworded the description of “manual_faces” cosmetic
- “photo_face_blur” reworded the description of “selected_faces” cosmetic
- “photo_meme_generator” reworded the description of “font” cosmetic
- “photo_shadow_adder” reworded the description of “angle” cosmetic
- 28 Sept 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
- 27 Sept 26 0
- “pdf_delete_pages” reworded the description of “pages” cosmetic
- “pdf_watermark” reworded the description of “pages” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 26 Sept 26 0
- “analyze_audio” reworded the description of “file” cosmetic
- “analyze_video” reworded the description of “file” cosmetic
- “media_extract_audio” reworded the description of “file” cosmetic
- “media_merge_audio” reworded the description of “files” cosmetic
- “media_mute_video” reworded the description of “file” cosmetic
- “media_trim_audio” reworded the description of “file” cosmetic
6 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 25 Sept 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
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 5 Nov 2026 · Probed https://api.johnsessentials.com/mcp/messages
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=johnsessentials.com | CN=YE1,O=Let's Encrypt,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 59d02ba272d0b298667b8b921613b1168e7 |
| SANs: *.johnsessentials.com, johnsessentials.com | ||||||
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.johnsessentials.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| johnsessentials.com. | 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 connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://api.johnsessentials.com/.well-known/oauth-protected-resource", scope="read write"
Bearer resource_metadata="https://api.johnsessentials.com/.well-known/oauth-protected-resource", scope="read write"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| www-authenticate | Bearer resource_metadata="https://api.johnsessentials.com/.well-known/oauth-protected-resource", scope="read write" |
Protected resource metadata
| Document | https://api.johnsessentials.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://api.johnsessentials.com/mcp/messages |
| Authorisation server | https://api.johnsessentials.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.johnsessentials.com/mcp/messages | Verified | 200 | |
| http (plaintext) | http://api.johnsessentials.com/mcp/messages | HTTPS enforced | 301 | https://api.johnsessentials.com/mcp/messages |
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 →
web_extract_table ~235
Extract Table — Extract an HTML table from a public web page at a user-provided http(s) URL, as JSON rows or CSV. [category: web]
| Name | Type | Req | Description |
|---|---|---|---|
| acknowledge_robots | boolean | – | Business plan: read the table even when the site's robots.txt asks bots to stay away. On any other plan this switch does nothing and the page is still refused. |
| output | string | – | How the table comes back: JSON gives rows you can feed to the next step, CSV gives one block of comma-separated text. Either way it is data, not a downloadable file. |
| table_index | integer | – | Which table on the page, counting from 0 for the first one. If the page has fewer tables than this, the error tells you how many it found. |
| timeout_ms | integer | – | How long to wait for the page before giving up, in milliseconds (30000 = 30 seconds). |
| url | string | yes | http(s) URL containing the table |
| user_agent | string | – | Advanced: how we introduce ourselves to the site. Left blank we identify as JohnsEssentialsBot. |
No output schema declared.
No examples provided.
web_fetch ~171
Fetch URL — Fetch the raw (decoded) HTML of a public web page at a user-provided http(s) URL. SSRF-guarded, http/https only, 10 MB body cap, robots-aware. [category: web]
| Name | Type | Req | Description |
|---|---|---|---|
| acknowledge_robots | boolean | – | Business plan only: fetch the page even when the site's rules file (robots.txt) asks crawlers to stay away. On other plans this switch has no effect. |
| timeout_ms | integer | – | How long to wait for the page before giving up, in milliseconds (30000 = 30 seconds). |
| url | string | yes | http(s) URL to fetch |
| user_agent | string | – | What to tell the site we are. Leave blank and we identify honestly as JohnsEssentialsBot/1.0. |
No output schema declared.
No examples provided.
web_scrape_page ~234
Scrape Page — Extract structured data from a public web page at a user-provided http(s) URL: CSS-selector mode returns text per selector; readability mode returns the main article as clean markdown. [category: web]
| Name | Type | Req | Description |
|---|---|---|---|
| acknowledge_robots | boolean | – | Business plan: scrape the page even when the site's robots.txt asks bots to stay away. On any other plan this switch does nothing and the page is still refused. |
| mode | string | – | Readability gives you the page's main article as clean text. Selectors gives you only the specific bits you name below. |
| selectors | object | – | One CSS selector per thing you want, named: {"headline": "h1", "price": ".price"}. Needed only when you pick Selectors above. |
| timeout_ms | integer | – | How long to wait for the page before giving up, in milliseconds (30000 = 30 seconds). |
| url | string | yes | http(s) URL to scrape |
| user_agent | string | – | Advanced: how we introduce ourselves to the site. Left blank we identify as JohnsEssentialsBot. |
No output schema declared.
No examples provided.
How do I install the John's Essentials MCP server?
John's Essentials is a hosted endpoint at https://api.johnsessentials.com/mcp/messages, 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 · api.johnsessentials.com
claude mcp add --transport http com-johnsessentials-johns-essentials 'https://api.johnsessentials.com/mcp/messages'
What is the John's Essentials MCP server?
John's Essentials is an MCP server listed in the public MCP registry as com.johnsessentials/johns-essentials. 144 deterministic file tools: PDF, image, media, convert, analyze. Connect in one click (OAuth). This page covers its hosted endpoint (https://api.johnsessentials.com/mcp/messages).
Is the John's Essentials MCP server safe to use?
John's Essentials scores 95 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 John's Essentials MCP server expose?
John's Essentials exposes 153 tools: pdf_compress, pdf_merge, pdf_split, pdf_rotate, pdf_protect, and 148 more. Their descriptions and schemas cost roughly 28,494 tokens of context every time the server is loaded.
Does the John's Essentials MCP server require authentication?
Yes. John's Essentials 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 John's Essentials MCP server still maintained?
John's Essentials is still listed as active in the MCP registry. We last reached this channel on 5 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 John's Essentials MCP server?
VerifyMCP ran 13 checks on John's Essentials, 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.