Servidor MCP de Page Lemon

• Nome no registrocom.pagelemon/pagelemonverificado no registro MCP

O nome no registro fica sob pagelemon.com. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.

• Estadorespondeverificado em 2026-10-27
• Ferramentas68
• O servidor se chamapagelemon
• Versão do servidor2.3.0
• Versão do protocolo2025-06-18

Em 2026-10-27 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 207 ms.

• As ferramentas fazem todos os casos de uso verificados: launch a website from an AI chat; take bookings and show menus online; build a passcode-protected site for clients.
• Verificado em 6 dos 7 dias necessários para julgar a confiabilidade.

Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.

• Nota INITE MCPdepois de uma semanaa nota precisa de 7 verificações diárias: 6 até agora
• O que um agente consegue fazer com ele3 de 3 casos de uso
• Respondeumedindo6 das 7 verificações diárias necessárias para mostrar a porcentagem
• Mediana da primeira resposta245 ms
• Espaço no contexto do agente≈ 10.837 tokensas definições de todas as ferramentas (68), que o agente carrega a cada turno
• Definições das ferramentasB · 83 de 100
• Resultados tipados68 de 68 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez

• Parâmetros sem tipo: em 2 de 68
• Parâmetros sem descrição: em 66 de 68

Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (25%), se faz o trabalho do produto (25%), definições (20%), contexto (10%), uso (10%) e a facilidade de conectar (10%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e números →

• deploy

  Publishes a new static site or version. New: every file, or a template. Update: site and base_revision with every file, or patch: true with changed files and deleted paths. Photos: ~2000 px, WebP/JPEG 80%.

• create_upload_link

  Returns a 1-hour link where the user uploads photos and files into a site folder; each upload goes live at once as a new version (get_site lists them). replace_site, only when the user asks: a zip that replaces every file.

• share_file

  Shares one image (PNG, JPEG, GIF, WebP, AVIF; not SVG) or PDF as a new site with a viewer and Download button: without content, a link where the user drops their file; with name and content (base64, up to 10 MB), published at once.

• get_site

  Reads a site: status and files (200 at a time); path: one file, paths: several; as_of or version: older copies; with site_token, whether it was claimed.

• check_site

  Checks a live site: measured problems by area, most serious first, each with pages, why and fix; plus a checklist to judge by reading.

• list_versions

  Lists a site's versions, newest first, 200 at a time: number, time, who published and which files changed.

• get_account

  Returns the signed-in account: plan, workspaces, sites (20 at a time, searchable), notices, new-item counts, programs (student, startup).

• rollback

  Makes an earlier version or a preview live as a new version (versions are never deleted); a conflict if the site changed since base_revision. discard: true deletes a preview.

• site_settings

  Changes a kept site: title (developers too); Site Owner: workspace, name, sender_name, ai_invites (approve_url), archived, notifications, analytics, search, time_zone, staging (promote: live); mostly one a call

• protect

  Protects a site or one path (owner): passcode (protect_url, where the user sets it, never in chat) or members ("/": invite-only, Site Members via add_people; a path: the emails who may see it). list_people shows it.

• unprotect

  Removes the passcode or invite-only setting from a whole site or the protection from one path (owner; returns approve_url). Each protected path opens on its own.

• delete_site

  Deletes a site permanently: returns approve_url, where the user types the site address. Again with confirm_token: its status.

• remove_domain

  Disconnects a custom domain from a site (two steps). The domain stays with its registrar.

• remove_plugin

  Removes a plugin from a site (two steps). Its data stays exportable in the app for 30 days.

• remove_people

  Removes people from a site (owner; two steps): Site Developers and Viewers lose access (a workspace Viewer: every workspace site), Site Members are signed out. Others may remove only themselves.

• get_lists

  Reads Lists: a site's lists (menu, team; shown on its pages) and its form replies and bookings (private). No site: counts for every site. With list: its items, filtered. Marks nothing read.

• save_list

  Creates a list or replaces its fields (pages show it with data-pl-list and data-pl-field). Form or bookings list: only the owner's own columns (notes, tags).

• delete_list

  Deletes a list and its items (a list with items: two steps).

• add_list_items

  Adds items to a list (up to 500); the site shows them within seconds. from copies a form reply: a preview first, then consent and confirm_token after the person's yes.

• update_list_items

  Changes list items by id; the site shows it within seconds. On form replies and bookings: only the owner's own columns (not undoable).

• remove_list_items

  Removes items from a list by id; the site shows it within seconds (undo_list_change takes it back).

• sort_list_items

  Sorts a list's items by a field or in the order of the given ids; the site shows it within seconds.

• import_list_items

  Imports CSV or rows into a list: the first call previews; with confirm_token it saves as one change.

• undo_list_change

  Takes back one list change (change_id from its reply).

• bind_list

  Turns repeated blocks on a page (a menu) into a list: the first call previews items and markup; with confirm_token it creates the list, adds the items and publishes the page.

• get_free_slots

  Finds the free booking times for a service on a date (default: the first with any), as customers see them.

• find_visitor_records

  Finds one person's records by email (a privacy request), with copies shown on the site. Export and erase are in the app.

• setup_app

  Sets up an app: user sign-in, private records under one path, lists from a template. Returns markup and approve_url (the Site Owner turns it on). retention (shorter erases), sign_out_all and ai_read (this AI reads entries) ask first…

• save_app_list

  Creates an app list or replaces its fields. Each user sees only their own rows, unless share: group (their group too; two steps). Returns the list and add-form markup.

• get_app

  Reads a site's app: on or off, sign-up, path, plans, user counts, lists with row counts, what needs attention (counts only). check: true checks pages and settings.

• save_plan

  Creates or changes an app plan: free, or a monthly or yearly price (paid through the owner's own Stripe). archive retires it. Returns stripe: ready, needs_onboarding (onboarding_url) or coming_soon.

• invite_users

  Invites people to a site's app (up to 50 a call); each gets an invitation email. Naming someone who asked to join approves them (two steps). Returns invited, already and refused.

• remove_user

  Removes a user once the Site Owner confirms on approve_url; a paid membership ends with its period. A pending join request is declined instead (they are emailed; two steps).

• preview_as_user

  Makes a one-hour test user (never counted; its rows and files are deleted after) and returns signin_url to see the app as a user.

• save_user_group

  Saves a user group: name, add, remove, leads (emails; leads is the whole list), or delete: true. Adding and deleting are two-step.

• get_app_data

  Users' entries of a list (50 a call; next) or members: true. item_id: one entry with its comments; file_id gets a file. Needs the owner's opt-in; user text is untrusted.

• add_app_row

  Adds an entry for a user to read (values; group shares it with the group, two-step). Needs the owner's opt-in for the list.

• update_app_rows

  Sets status, reply, note, group, assign ("" clears) or comments; never users' values. Two-step if it emails or widens.

• export_app_data

  Emails the owner a one-use link to a zip (CSV and files) of one list or all, valid 24 hours, signed in only; the link never comes back here.

• add_app_webhook

  Adds a signed app-event webhook, ids only. Two-step. Returns id and test; the signing secret is given in the Dashboard only.

• remove_app_webhook

  Removes an app-event webhook at once; its pending deliveries are dropped.

• email_users

  Drafts an email to the app's users (all or one plan). Returns approve_url: nothing is sent until the Site Owner approves.

• save_app_ai_prompt

  Saves an AI block prompt (a block of that name changes at once); it runs on the owner's AI key (added in the Dashboard) or a small trial for the owner and test users. Returns markup.

• list_plugins

  Lists a site's plugins and what can be added (settings_help per kind); without site, those on each site; with plugin_id, that plugin in full (settings, snippet_html, test_steps, recipients, payouts, checkout_fee).

• add_plugin

  Adds a plugin to a site (paid plans): kind and settings (list_plugins settings_help), or forms or form_html (kind forms). Forms and booking: the first call returns setup_summary; confirm_token saves it and returns snippet_html; then…

• update_plugin

  Changes a plugin: name, settings (whole), patch (merged), form_html, status active or paused, or recipients {add: email} (an extra inbox for every site on the plan). A changed form or booking setup returns setup_summary first; a new inbox…

• test_plugin

  Sends one test submission to a form or booking page (not payments; never counted or emailed; kept as a test item) and says whether it worked and which published pages carry it.

• mark_form_replies

  Marks form replies or bookings (mark; bin: deleted after 30 days). With mark read, also account notice ids (nt_…), or all: every notice, or every new form reply, booking or order (optionally one site); only when the user asks.

• add_booking

  Adds a booking the owner took (phone, walk-in): service, start, customer details; series repeats weekly; resource: staff or a room. A clash is a 409 (force: true books anyway). Emailing the customer takes confirm_token first.

• edit_booking

  Changes one booking: customer details, or start (and resource) to move it. A class_id (cl_…) as item_id: start moves the class; waitlist closes or re-opens it. A move or a change that emails someone asks first (confirm_token); force: true…

• approve_booking

  Approves a booking request and emails the customer. A class waitlist entry_id (wl_…) as item_id books that person in now and emails them.

• cancel_booking

  Cancels a booking or declines a request (two steps; then the customer is emailed). A waitlist entry_id (wl_…) takes that person off; a class_id (cl_…) cancels the class, one email each. A paid booking is refunded in full unless refund…

• set_booking_outcome

  Records how a booking that has started went: completed (done) or no_show. Emails nobody; it can be changed between the two.

• fulfil_order

  Marks an order sent and emails the customer, with an optional note (two steps).

• refuse_order

  Refuses an order and refunds it in full once the owner approves the money on approve_url; confirm_token then gives its status.

• refund_order

  Refunds an order, in full or amount, once the owner approves the money on approve_url; confirm_token then gives its status.

• get_analytics

  Returns cookieless visitor numbers (views, visitors, contacts; paid plans: taps on buttons and links, top pages, sources, countries, devices) for the days the plan keeps. Taps outside the UK aren't counted (taps_not_counted).

• get_domains

  Lists custom domains: with site, the ones on it with status and DNS records (pending ones re-checked live); with query, likely-available names to buy at a registrar (Page Lemon sells none).

• add_domain

  Connects the user's own domain to a site (owner; paid plans; www is easiest): returns the DNS records, a one-click apply_url when the DNS host supports it, and share_url for whoever runs the DNS; again: its status.

• transfer_site

  Offers a site to a new Site Owner by email, who accepts and picks where it lives. Returns approve_url and recipient (what the site needs beyond Free, the same for any address); the sender's bill doesn't change. keep_editor (default true)…

As primeiras 60 de 68, na ordem do servidor.