Converter Studio
REMOTE · CONVERTER.STUDIO
Convert video, audio, images, PDFs and documents in 67 formats; results come back as links.
Available components
Last scanned (17 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 21 Nov 2026.
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 805 tokens (~134/item across 6 items; 6 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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
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.
- 20 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 19 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 18 Nov 26 70
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://converter.studio/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=converter.studio | CN=YE2,O=Let's Encrypt,C=US | 13 Nov 2026 | 11 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 5aa523235ac6927f0af621e44cbee5f12bc |
| SANs: *.converter.studio, converter.studio | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 converter.studio. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| studio. | DS published | 35741 | 8 | Verified |
| converter.studio. | No DS | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://converter.studio/api/mcp | Verified | 200 | |
| http (plaintext) | http://converter.studio/api/mcp | HTTPS enforced | 301 | https://converter.studio/api/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 →
confirm_conversion Confirm a conversion ~59
Starts a conversion that waits for a go-ahead because it costs more than its maxCredits. Spends the shown credits: ask the user first. Waits up to 100 seconds for the result.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The conversion id |
No output schema declared.
No examples provided.
convert Convert a file ~247
Converts a file to another format and returns a download link (valid 6 hours). The file comes from "url" (a direct link or a Google Drive, Dropbox or OneDrive share link), "uploadId" (from create_upload) or "contentBase64" with "fileName" (files up to 8 MB). Uses credits from the user's converter.studio account; goes ahead on its own up to maxCredits. Waits up to 100 seconds; if not done, call get_conversion.
| Name | Type | Req | Description |
|---|---|---|---|
| contentBase64 | string | – | The file itself, base64 (up to 8 MB) |
| fileName | string | – | The file name, needed with contentBase64 |
| maxCredits | integer | – | Go ahead without asking up to this price (default 20; 0 only prices it) |
| options | object | – | Optional settings (quality, resolution, bitrate…) where the conversion has them |
| to | string | yes | Target format id, e.g. "pdf", "mp4", "jpg" |
| uploadId | string | – | An upload slot id whose file was uploaded |
| url | string | – | A link to the file |
No output schema declared.
No examples provided.
create_upload Create an upload ~92
For a local file bigger than 8 MB: returns a one-time upload URL and a curl command. Run the command in a shell (files over 95 MB need parts, see partBytes), then call convert with the returned uploadId. The slot expires after an hour.
| Name | Type | Req | Description |
|---|---|---|---|
| fileName | string | yes | The file name with its extension |
| sizeBytes | integer | – | The file size, if known |
No output schema declared.
No examples provided.
get_account Get the account ~22
The user's converter.studio plan, credits left and file size limit.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_conversion Get a conversion ~58
The status of a conversion by id, with its download link once done. Waits up to waitSeconds (at most 100) for it to finish.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The conversion id |
| waitSeconds | integer | – | – |
No output schema declared.
No examples provided.
list_formats List formats ~63
Lists the file formats Converter Studio converts and what each converts to. Give "from" (a format id such as "heic" or "mp4") to see the targets of one format. Needs no account.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Only this source format |
No output schema declared.
No examples provided.
How do I install the Converter Studio MCP server?
Converter Studio is a hosted endpoint at https://converter.studio/api/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 · converter.studio
claude mcp add --transport http studio-converter-converter-studio 'https://converter.studio/api/mcp'
What is the Converter Studio MCP server?
Converter Studio is an MCP server listed in the public MCP registry as studio.converter/converter-studio. Convert video, audio, images, PDFs and documents in 67 formats; results come back as links. This page covers its hosted endpoint (https://converter.studio/api/mcp).
Is the Converter Studio MCP server safe to use?
Converter Studio scores 71 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 Converter Studio MCP server expose?
Converter Studio exposes 6 tools: list_formats, create_upload, convert, get_conversion, confirm_conversion, get_account. Their descriptions and schemas cost roughly 541 tokens of context every time the server is loaded.
Does the Converter Studio MCP server require authentication?
No. We connected to Converter Studio without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Converter Studio MCP server still maintained?
Converter Studio 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 Converter Studio MCP server?
VerifyMCP ran 13 checks on Converter Studio, 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.