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.

ready→made MCP

REMOTE · API.LEVELS.DEV

Deterministic Figma to Elementor, Gutenberg, Oxygen, Etch and HTML layouts for AI assistants.

Available components

+3 this week 68 Trust /100

Last scanned (16 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 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 Security57
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 926 tokens (~308/item across 3 items; 3 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 Management40
  • Stability observed for 12 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
  • We read all 3 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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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 →

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “convert_figma” rewrote its description, which is the text the model reads security
    • Tool “list_targets” rewrote its description, which is the text the model reads security
  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 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.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 265 → 295 ▼ functional
    • “convert_figma” reworded the description of “refresh” cosmetic
    • “inspect_figma” reworded the description of “refresh” cosmetic
  • 10 Nov 26 0
    • Tool “convert_figma” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
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 21 Nov 2026 · Probed https://api.levels.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.levels.dev CN=YE1,O=Let's Encrypt,C=US 24 Oct 2026 22 Jan 2027 ECDSA 384 ECDSA-SHA384 6368b187892f643c75763ebb38e1920636c
SANs: api.levels.dev
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.levels.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
levels.dev. 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
Header Value
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.levels.dev/mcp Verified 200
http (plaintext) http://api.levels.dev/mcp HTTPS enforced 301 https://api.levels.dev/mcp
MCP tools · 3 exposed · ~784 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_figma ~399

Convert ONE Figma frame into a native WordPress builder layout with ready→made's deterministic spatial engine (same frame → same output, no LLM guessing). Returns the paste-ready payload plus a short instruction on how to paste/import it. Targets: elementor (container JSON for "Paste from other site", or a template file), gutenberg (core block markup), oxygen6, oxygen (Classic), etch, divi (Divi 4 Portability .json or shortcodes, built from the html output, not yet verified in a live Divi install), html (self-contained). Convert sections one at a time (hero, features, footer…). A whole page in one call hits the layer limit. Requires a ready→made Pro or Lifetime plan; free accounts get 3 free trial conversions.

NameTypeReqDescription
figmaTokenstring–A Figma personal access token (figd_…) with the "File content: read" scope. Usually configured once as the x-figma-token header in the MCP client; pass it here only if the header is not set. It is fo…
nodestring–Node id such as "12:345" or "12-345". Overrides node-id in the URL.
optionsobject–Optional tuning.
refreshboolean–Only matters if the user turned on "Cache Figma data" on the ready→made account page (off by default): then ignore the cached copy and refetch from Figma. Without that setting nothing is cached and e…
targetstring–Output format. Default: elementor.
urlstringyesFigma frame URL. In Figma: select the frame, right-click → "Copy link to selection". Must carry node-id (or pass `node`).

No output schema declared.

No examples provided.

inspect_figma ~317

Outline a Figma file or frame WITHOUT converting: layer tree (names, ids, types, sizes), node count, text/image/vector counts, whether the frame is within the convert limit, and a list of section-sized child frames that are good convert_figma candidates. Use it to pick the right frame when the user gives a whole-file link, or when convert_figma says a frame is too large. Free.

NameTypeReqDescription
depthinteger–Levels of children to include. Default 3.
figmaTokenstring–A Figma personal access token (figd_…) with the "File content: read" scope. Usually configured once as the x-figma-token header in the MCP client; pass it here only if the header is not set. It is fo…
nodestring–Node id such as "12:345" or "12-345". Overrides node-id in the URL.
refreshboolean–Only matters if the user turned on "Cache Figma data" on the ready→made account page (off by default): then ignore the cached copy and refetch from Figma. Without that setting nothing is cached and e…
urlstringyesFigma URL (https://www.figma.com/design/<fileKey>/…?node-id=<id>) or a bare file key. Without node-id the whole file is outlined.

No output schema declared.

No examples provided.

list_targets ~68

List the WordPress builder formats ready→made can emit (Elementor, Gutenberg, Oxygen 6, Oxygen Classic, Etch, Divi, plain HTML) with a one-line note on how each output is pasted or imported. Free; call it when unsure which `target` to use.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the ready→made MCP server?

ready→made MCP is a hosted endpoint at https://api.levels.dev/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 · api.levels.dev

# add to Claude Code
claude mcp add --transport http dev-levels-readymade 'https://api.levels.dev/mcp'
Common questions

What is the ready→made MCP server?

ready→made MCP is listed in the public MCP registry as dev.levels/readymade. Deterministic Figma to Elementor, Gutenberg, Oxygen, Etch and HTML layouts for AI assistants. This page covers its hosted endpoint (https://api.levels.dev/mcp).

Is the ready→made MCP server safe to use?

ready→made MCP scores 68 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 ready→made MCP server expose?

ready→made MCP exposes 3 tools: list_targets, inspect_figma, convert_figma. Their descriptions and schemas cost roughly 784 tokens of context every time the server is loaded.

Does the ready→made MCP server require authentication?

No. We connected to ready→made MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ready→made MCP server still maintained?

ready→made MCP 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 ready→made MCP server?

VerifyMCP ran 12 checks on ready→made MCP, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about ready→made MCP: Authorization. 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.