Servidor MCP de JuzPost

• Nome no registrocom.juzpost/mcpverificado no registro MCP

O nome no registro fica sob juzpost.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
• Ferramentas19
• O servidor se chamajuzpost
• Versão do servidor2.0.0
• Versão do protocolo2025-06-18

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

• As ferramentas fazem todos os casos de uso verificados: Publish one post to many social networks; Post to connected accounts from an AI assistant.
• Verificado em 2 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: 2 até agora
• O que um agente consegue fazer com ele2 de 2 casos de uso
• Respondeumedindo2 das 7 verificações diárias necessárias para mostrar a porcentagem
• Mediana da primeira resposta291 ms
• Espaço no contexto do agente≈ 13.499 tokensas definições de todas as ferramentas (19), que o agente carrega a cada turno
• Definições das ferramentasA · 92 de 100
• Resultados tipados19 de 19 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez

• Parâmetros sem descrição: em 9 de 19

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 →

• get_context

  Reports who this connection is, the one workspace it acts on (use switch_workspace to change it), the plan, billing state, entitlements, quotas, limits and a plain-language list of what is blocked right now. Use this to see what the…

• list_workspaces

  Lists every workspace the user belongs to, marks the one this connection acts on, and says what each allows through the connector: none (Free or no plan) or full (Solo, Growth, Pro). Use this when the user names another workspace or a…

• switch_workspace

  A connection acts on one workspace at a time. This moves it onto another workspace the user belongs to (id or slug from list_workspaces) for every later call, until switched again, and returns the new context. Use this when the user names…

• list_accounts

  Lists the social accounts connected to the workspace, with health, how many posts are queued on each, and the effective limits for that account. Use this to pick the accounts for create_post and schedule_post, or to check whether an…

• list_options

  Lists the choices one account offers for a setting the schedule needs, read live from the platform. Requests: list_board (pinterest, ids go in pinterest.board_id); list_post_type (wordpress, ids go in wordpress.post_type). Use this when…

• get_platform_limits

  Returns the full publishing rules for one platform or all of them: caption and title limits and units, media counts, sizes, formats, whether media is required, hashtags, mentions, native scheduling, plus the global file rules. Use this…

• list_groups

  Lists channel groups (named sets of accounts) with their member account ids. Use this when the user names a group ("post to my brand accounts") to resolve it to the account ids schedule_post takes. Returns groups[] (id, name, accountIds…

• list_posts

  Lists posts in the workspace: drafts, scheduled, published and failed. Use this to find drafts to schedule, to review the queue, or to find a post id for get_post, update_post or delete_post. Returns posts[] (id, status, type, title…

• get_post

  Fetches one post with its per-account rows: status, publish time, published time and any error per account. Use this after schedule_post to confirm what happened, or when the user asks why a post failed. Returns the post (content, media…

• create_post

  Creates a draft post with everything the composer saves: caption, title, description, hashtags, media, the accounts it goes to, per-account text (account_overrides, channel_overrides), per-account media and covers, and each platform's…

• update_post

  Edits a draft or a scheduled post, the same edit the composer makes: caption, title, description, hashtags, type, media keys, cover, accounts, per-account text, media and covers, platform settings, and the time. Only the fields passed…

• delete_post

  Permanently deletes a draft post and its target rows. Use this only when the user explicitly asks to discard a draft. Returns deleted=true, the post id and what the deleted draft was (title, caption, type, media count). Does NOT delete…

• schedule_post

  Schedules a post to one or more accounts at publish_at (ISO 8601 UTC), or publishes immediately with publish_now=true. This publishes to real accounts. One call does it all: without post_id it creates the post from the content and…

• upload_file

  Shows an upload card where the user picks images or videos from their device (images up to 20 MB, videos up to 200 MB); the card stores the original files in the workspace. Use this in a chat app that shows cards (Claude.ai, Claude…

• upload_media

  Stores the original image or video in the workspace from a file the chat app hands over, a public URL (up to 100 MB) or inline base64 (up to 3 MB), checking the real file type and the storage quota. Use this when the user gives you a link…

• create_upload_url

  Reserves storage for one file and returns a presigned upload_url (valid 1 day) plus the media_key it will be stored under. Images up to 20 MB, videos up to 200 MB. Use this in Claude Code, a terminal or a script, for a local file or any…

• upload_begin

  Called only by the JuzPost upload card, never by the model. Reserves storage for one file and starts a multipart upload. Returns media_key, upload_id, part_size and parts.

• upload_part

  Called only by the JuzPost upload card, never by the model. Stores one part of a file started with upload_begin: the original bytes as base64, exactly part_size bytes except the last part. Returns part_number and bytes.

• upload_finish

  Called only by the JuzPost upload card, never by the model. Completes an upload once every part is stored. Returns media_key, bytes and content_type.