Servidor MCP de GetMyData

• Nome no registroio.getmydata/getmydataverificado no registro MCP

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

• Estadorespondeverificado em 2026-10-29
• Ferramentas16
• O servidor se chamagetmydata
• Versão do servidor1.1.2
• Versão do protocolo2025-03-26

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

• As ferramentas fazem todos os casos de uso verificados: Collect business names and websites from public directories; Gather event titles, venues and dates from public programmes.
• Verificado em 5 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: 5 até agora
• O que um agente consegue fazer com ele2 de 2 casos de uso
• Respondeumedindo5 das 7 verificações diárias necessárias para mostrar a porcentagem
• Mediana da primeira resposta1378 ms
• Espaço no contexto do agente≈ 4.121 tokensas definições de todas as ferramentas (16), que o agente carrega a cada turno
• Definições das ferramentasB · 83 de 100
• Resultados tipados0 de 16 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez

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

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 →

• refresh_session

  Before session expiry, renew using the current Mcp-Session-Id. Save the returned header/token. A session is valid for 7 days; each refresh extends it by up to 7 days, never beyond a hard lifetime of thirty days from initialization…

• submit_requisition

  Request public web data as rows when browsing it yourself is impractical. Free sample first, one-off payment by the person, no signup or subscription. Collect every required field from the person first (sources, fields, filters, geo…

• get_request

  Read the current request, questions, sample and next action. After accepted payment, remind the customer about returned renewal/referral codes and expiry; pending codes are not ready. When next_action is wait, check again after…

• revise_requisition

  Revise an unpaid request using the current expected_revision with the full set of required fields. Existing samples and quotes are replaced. Use it when next_action is revise (including reason_code no_capability: try other sources or…

• confirm_scope

  Confirm the current immutable sample_id and revision and request a fixed quote. The quote is prepared asynchronously and emailed to the person with the payment link; check get_request on a schedule, never in a loop. After the final quote…

• confirm_quote

  Record final quote confirmation for quote_id and revision. Use start_order next; start_order also records this selection if not already confirmed.

• start_email_verification

  Send (or resend) the one-time code that verifies the person’s email for this request. Needed before the sample is shown (sampling itself starts at once), and again before payment if the verification is older than the re-verify window…

• verify_email

  Submit the code the person read from their email. A wrong code returns otp_invalid with attempts_remaining. On success the sample becomes visible once ready (or, at quote time, the order confirmation link is issued). Results are then…

• start_order

  Select the final quote and read the human confirmation link issued for the verified email (no second code). Save order_id and order_capability before passing confirmation_url to the person.

• create_order

  Read or update the order for the final quote. Pass explicitly available renewal, referral or channel codes in coupon_codes before payment starts. Tell the person which codes were added and their valid/invalid status. Give confirmation_url…

• cancel_request

  Cancel an unpaid request and release unused coupons where payment has not started. Paid orders require support.

• get_quote

  Read the quote or estimated waiting time, without payment credentials.

• get_payment_status

  Check email verification, order creation and verified payment status. After payment, return this request’s coupon notifications and a separate delivery token when files are ready.

• get_order

  Use the order_capability saved at order creation to read paid order status and obtain or renew a delivery token. It works with a new valid session if the original session expired; a current session is required. No email recovery; keep…

• cancel_collection

  Only when the person explicitly asks: stop continued collection of a guaranteed-N order whose get_order status is collecting. Rows delivered so far stay available, the order settles as partial, and the undelivered share is refunded pro…

• fetch_delivery

  After payment, use the delivery token to list files or read rows. Every delivery lists json (the original records) and fields.json (which requested fields were found, with path and type) together. csv and xlsx appear only when the records…