Servidor MCP de Spoofy

• Nome no registrosocial.spoofy/mcpverificado no registro MCP

O nome no registro fica sob spoofy.social. 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
• Ferramentas17
• O servidor se chamaspoofy
• Versão do servidor1.2.0
• Versão do protocolo2025-06-18

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

• As ferramentas fazem todos os casos de uso verificados: Order followers for an X account; Add views to a YouTube video over several days; Split a budget between likes and followers on one post.

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 MCP78 de 100responde 100 · faz o trabalho 100 · definições 100 · contexto 78 · conexão 100 · reduzida pelos sinais de alerta abaixo
• O que um agente consegue fazer com ele3 de 3 casos de uso
• Respondeuem 100% dos dias9 de 9 verificações diárias
• Mediana da primeira resposta223 ms
• Espaço no contexto do agente≈ 6.680 tokensas definições de todas as ferramentas (17), que o agente carrega a cada turno
• Definições das ferramentasA · 100 de 100
• Resultados tipados0 de 17 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez

• Todas as ferramentas passam nas seis verificações.

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 →

• find_services

  Find what Spoofy can do for a link or a goal, with prices. ALWAYS call this first: service ids come from here. Give `link` (any profile, post, video, channel, group, token page or website URL) and/or `goal` in plain words, e.g. "500…

• get_quote

  Exact price in USD for a quantity of one service (from find_services). Checks the quantity is within the service range. Free; spends nothing. Use it to tell the user the cost before place_order. For services with an `input`, pass the same…

• place_order

  Place an order. THIS SPENDS THE USER'S REAL BALANCE (USD) and starts delivery to the link; it cannot be undone except by cancel_order where the service allows it. Before calling: get the price with get_quote and get the user's explicit…

• place_orders

  Place up to 25 orders in one go — several services, one link or several — paid together from the balance. THIS SPENDS THE USER'S REAL BALANCE (USD) and starts delivery. Use it when the user wants several things at once (e.g. followers +…

• get_order

  Status and progress of one order: status (pending, processing, completed, partial, refunded, cancelled, failed), start count, delivered, remains, charge and refunds in USD, and whether it can be cancelled now.

• list_orders

  The user's orders, newest first. Filter by status; page with `before` = the smallest order number already seen.

• cancel_order

  Ask to cancel a pending or processing order (only when the order says cancelable: true). Whatever was not delivered is refunded to the balance in USD. Confirm with the user first.

• get_balance

  The user's spendable balance in USD. Orders are paid from it.

• get_top_up_info

  How the user adds money to the balance: stablecoins (USDC, USDT or USDG, on the networks that are on) sent to their own deposit address — one address for every EVM network, another on Solana — credited 1 coin = $1, plus the top-up page…

• create_automation

  Set up an automation: Spoofy places ordinary orders for the user on a plan. Kinds: spread (a total over time, e.g. {"kind":"spread","service":12,"link":"…","quantity":10000,"over":"3d"}; pace "steady" or "front" for an S-curve growth…

• list_automations

  The user's automations, newest first, with progress (runs placed, delivered), spend against budget and the next run. Filter by status.

• get_automation

  One automation with its timeline: every run, the order it placed and what that delivered, or why a run waits or was skipped (balance, budget, a daily limit).

• update_automation

  Change a new-post automation's settings (kind feed) while it runs, as PATCH /api/v1/automations/{id} takes them: each post's amount — quantity, or quantity_min + quantity_max (each post gets a random whole number in the range, within one…

• pause_automation

  Stop placing new runs until it is resumed (orders already running keep delivering). Nothing is charged while paused.

• resume_automation

  Carry on with a paused automation: the rest of the plan moves by the time it was paused. After a price change, resuming accepts the new price for the runs left — tell the user first.

• cancel_automation

  Stop an automation for good: every future run is cancelled. Orders already running finish, unless cancel_running: true asks those that allow it to cancel too (the undelivered part is refunded). Confirm with the user first.

• add_automation_link

  For an automation of kind per_link ("a new post each run"): the link of its next run — the new post, video or track the user wants it on. The run goes out at once as an ordinary order at the price the plan was set up with, charged from…