WebDiet
REMOTE · API.MCP.AI
Patient, meal plan, prescription, chart and anthropometry management for dietitians.
Available components
Last scanned (13 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: this server exposes a tool marked destructive (webdiet_patient_delete) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 14332 tokens (~231/item across 62 items; 62 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 10 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 63 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
Checks we ran (11)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
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: this server exposes a tool marked destructive (webdiet_patient_delete) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
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 →
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 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.460 → 0.9.467 functional
- 20 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.459 → 0.9.460 functional
- 19 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.454 → 0.9.459 functional
- 18 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.452 → 0.9.454 functional
- 17 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.450 → 0.9.452 functional
- 16 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.449 → 0.9.450 functional
- 15 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.442 → 0.9.449 functional
- 14 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.429 → 0.9.442 functional
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.mcp.ai/p_webdiet
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.ai | CN=WE1,O=Google Trust Services,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 1bf4d405299e078a0e62ff16cded599b |
| SANs: mcp.ai, *.mcp.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.mcp.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| mcp.ai. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.mcp.ai/p_webdiet | Verified | 200 | |
| http (plaintext) | http://api.mcp.ai/p_webdiet | Inconclusive | 406 |
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 →
webdiet_preconsulta_list_templates ~303
Read pre-consultation questionnaires (Pré-consulta) in WebDiet. Actions: - list_templates → list all questionnaire templates the nutritionist publishes. Each item returns nome, descricao, perguntas[] (decoded), modelo, codigo, "link" (the public short URL https://nutr.se/<short> to share with patients) and "preview_url" (panel preview). USE THIS when the user asks for "o link do questionário de pré-consulta" / "link do formulário". - list_responses → list patient submissions to ANY template. Each response has id, id_code, template_nome, origem (anamnese | questionario), respondedor {nome, telefone, nascimento}, data, texto (decoded plain Q/A), texto_html (original HTML), pdf_url. Use filtros tipo (template name) and nome (responder name) to narrow. - get_response → fetch one response by id (or id_code/codigo). For LINKING a response to an existing patient (vincular), use webdiet_preconsulta_write action=link_to_patient. [Flattened action: list_templates] Bulk support: accepts response_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| limit | number | – | – |
| nome | string | – | – |
| offset | number | – | – |
| response_id | string | – | – |
| response_ids | array | – | – |
| tipo | string | – | – |
No output schema declared.
No examples provided.
webdiet_preconsulta_write_link_to_patient ~267
Vincular (link) a pre-consultation response to an existing patient in WebDiet. Action: link_to_patient — imports the response content into the patient's chart. WebDiet routes automatically based on the response's "origem": • origem=anamnese → response becomes a new anamnese (importarPreanamnese.php) • origem=questionario → response becomes a new diagnostico (criarDiagnosticoPre.php) This is the API-equivalent of the panel's "Vincular ao paciente" button on the Respostas dos questionários page. After linking, the response remains in the responses list — use webdiet_preconsulta_delete to remove it if desired. Tip: when the response's respondedor.nome differs from the patient's nome (e.g. "DALILA JULIAO MARTINS" vs "Dalila CG"), match by telefone or nascimento via webdiet_patient list before linking. [Flattened action: link_to_patient] Bulk support: accepts patient_ids, response_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| patient_id | string | yes | – |
| patient_ids | array | – | – |
| response_id | string | yes | – |
| response_ids | array | – | – |
No output schema declared.
No examples provided.
webdiet_prescription_get_detail ~91
Read meal plan prescriptions in WebDiet. Actions: list (all recent prescriptions — each includes "url" with the full direct link), get_detail (full meals/foods from a prescription URL). Always show the "url" field to the user when they ask for a prescription link. [Flattened action: get_detail]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| link | string | – | – |
No output schema declared.
No examples provided.
webdiet_prescription_list ~89
Read meal plan prescriptions in WebDiet. Actions: list (all recent prescriptions — each includes "url" with the full direct link), get_detail (full meals/foods from a prescription URL). Always show the "url" field to the user when they ask for a prescription link. [Flattened action: list]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| link | string | – | – |
No output schema declared.
No examples provided.
webdiet_prescription_write_create ~933
Create, save or publish meal plan prescriptions in WebDiet. Actions: create (new prescription for patient), save (meals/foods JSON to existing prescription), publish (release prescription to patient — makes it visible on the patient portal/app). IMPORTANT: After creating and saving foods, you MUST call publish to make the prescription visible to the patient. ═══ MÉTODO DE PRESCRIÇÃO — escolha no create ═══ WebDiet tem 3 métodos: • "Convencional" (UI: "Por alimentos", URL: metodoPlanning.php) — DEFAULT e RECOMENDADO. Alimento-por-alimento. Para cálculo de macros automático (proteínas/lipídios/carboidratos/calorias) na tabela "Alimentos prescritos" detalhada, cada alimento DEVE incluir o campo "id" com o WebDiet food-DB ID numérico. Sem id, o alimento AINDA é salvo no método Convencional e aparece no card expandido da refeição com nome + medida caseira, mas sem macros. NÃO vai para a seção qualitativa — o save retorna um warning explicando. • "Equivalentes" (UI: "Por equivalentes", URL: metodoWebdiet.php) — avançado. Prescrição por grupos de equivalentes. Requer IDs do banco. • "Qualitativo" (UI: "Qualitativa", URL: metodoQualitativo.php) — texto livre por refeição. A página do Qualitativo usa estrutura de dados diferente (refs com objetos cardapio) que este adapter ainda não gera corretamente via save. Para prescrições qualitativas, recomendado: criar via UI ou usar metodo="Convencional" sem food IDs (os alimentos aparecem como texto na refeição sem macros, efeito semelhante). ═══ prescricao_json (para o save) ═══ JSON array de refeições. Cada refeição: {nome, horario, alimentos:[...]}. Cada alimento: {nome, quantidade, medida_caseira, peso_gramas, id?}. AUTO-RESOLVE: se "id" não for enviado, o adapter procura automaticamente o melhor match no banco WebDiet (mesmo catálogo do webdiet_food_search) pelo campo "nome" e preenche o id antes de salvar — com isso os macros são calculados mesmo sem pré-chamar webdiet_food_search. O save retorna auto_resolved_foods…
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| metodo | string | – | – |
| nome | string | – | – |
| patient_id | string | yes | – |
| patient_ids | array | – | – |
| prescricao_json | string | – | – |
| prescription_id | string | – | – |
| prescription_ids | array | – | – |
No output schema declared.
No examples provided.
webdiet_prescription_write_publish ~933
Create, save or publish meal plan prescriptions in WebDiet. Actions: create (new prescription for patient), save (meals/foods JSON to existing prescription), publish (release prescription to patient — makes it visible on the patient portal/app). IMPORTANT: After creating and saving foods, you MUST call publish to make the prescription visible to the patient. ═══ MÉTODO DE PRESCRIÇÃO — escolha no create ═══ WebDiet tem 3 métodos: • "Convencional" (UI: "Por alimentos", URL: metodoPlanning.php) — DEFAULT e RECOMENDADO. Alimento-por-alimento. Para cálculo de macros automático (proteínas/lipídios/carboidratos/calorias) na tabela "Alimentos prescritos" detalhada, cada alimento DEVE incluir o campo "id" com o WebDiet food-DB ID numérico. Sem id, o alimento AINDA é salvo no método Convencional e aparece no card expandido da refeição com nome + medida caseira, mas sem macros. NÃO vai para a seção qualitativa — o save retorna um warning explicando. • "Equivalentes" (UI: "Por equivalentes", URL: metodoWebdiet.php) — avançado. Prescrição por grupos de equivalentes. Requer IDs do banco. • "Qualitativo" (UI: "Qualitativa", URL: metodoQualitativo.php) — texto livre por refeição. A página do Qualitativo usa estrutura de dados diferente (refs com objetos cardapio) que este adapter ainda não gera corretamente via save. Para prescrições qualitativas, recomendado: criar via UI ou usar metodo="Convencional" sem food IDs (os alimentos aparecem como texto na refeição sem macros, efeito semelhante). ═══ prescricao_json (para o save) ═══ JSON array de refeições. Cada refeição: {nome, horario, alimentos:[...]}. Cada alimento: {nome, quantidade, medida_caseira, peso_gramas, id?}. AUTO-RESOLVE: se "id" não for enviado, o adapter procura automaticamente o melhor match no banco WebDiet (mesmo catálogo do webdiet_food_search) pelo campo "nome" e preenche o id antes de salvar — com isso os macros são calculados mesmo sem pré-chamar webdiet_food_search. O save retorna auto_resolved_foods…
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| metodo | string | – | – |
| nome | string | – | – |
| patient_id | string | yes | – |
| patient_ids | array | – | – |
| prescricao_json | string | – | – |
| prescription_id | string | – | – |
| prescription_ids | array | – | – |
No output schema declared.
No examples provided.
webdiet_prescription_write_save ~933
Create, save or publish meal plan prescriptions in WebDiet. Actions: create (new prescription for patient), save (meals/foods JSON to existing prescription), publish (release prescription to patient — makes it visible on the patient portal/app). IMPORTANT: After creating and saving foods, you MUST call publish to make the prescription visible to the patient. ═══ MÉTODO DE PRESCRIÇÃO — escolha no create ═══ WebDiet tem 3 métodos: • "Convencional" (UI: "Por alimentos", URL: metodoPlanning.php) — DEFAULT e RECOMENDADO. Alimento-por-alimento. Para cálculo de macros automático (proteínas/lipídios/carboidratos/calorias) na tabela "Alimentos prescritos" detalhada, cada alimento DEVE incluir o campo "id" com o WebDiet food-DB ID numérico. Sem id, o alimento AINDA é salvo no método Convencional e aparece no card expandido da refeição com nome + medida caseira, mas sem macros. NÃO vai para a seção qualitativa — o save retorna um warning explicando. • "Equivalentes" (UI: "Por equivalentes", URL: metodoWebdiet.php) — avançado. Prescrição por grupos de equivalentes. Requer IDs do banco. • "Qualitativo" (UI: "Qualitativa", URL: metodoQualitativo.php) — texto livre por refeição. A página do Qualitativo usa estrutura de dados diferente (refs com objetos cardapio) que este adapter ainda não gera corretamente via save. Para prescrições qualitativas, recomendado: criar via UI ou usar metodo="Convencional" sem food IDs (os alimentos aparecem como texto na refeição sem macros, efeito semelhante). ═══ prescricao_json (para o save) ═══ JSON array de refeições. Cada refeição: {nome, horario, alimentos:[...]}. Cada alimento: {nome, quantidade, medida_caseira, peso_gramas, id?}. AUTO-RESOLVE: se "id" não for enviado, o adapter procura automaticamente o melhor match no banco WebDiet (mesmo catálogo do webdiet_food_search) pelo campo "nome" e preenche o id antes de salvar — com isso os macros são calculados mesmo sem pré-chamar webdiet_food_search. O save retorna auto_resolved_foods…
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| metodo | string | – | – |
| nome | string | – | – |
| patient_id | string | yes | – |
| patient_ids | array | – | – |
| prescricao_json | string | – | – |
| prescription_id | string | – | – |
| prescription_ids | array | – | – |
No output schema declared.
No examples provided.
webdiet_prontuario ~79
Get the clinical record (prontuario) for a WebDiet patient. Returns decoded text with sections: Identificacao, Triagem, Anamnese alimentar, etc. Bulk support: accepts patient_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| patient_id | string | yes | – |
| patient_ids | array | – | – |
No output schema declared.
No examples provided.
webdiet_prontuario_write ~82
Save the clinical record (prontuario) for a WebDiet patient. Pass texto as a JSON array of HTML strings, one per section. Bulk support: accepts patient_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| patient_id | string | yes | – |
| patient_ids | array | – | – |
| texto | string | yes | – |
No output schema declared.
No examples provided.
webdiet_recibo ~150
Generate or update a receipt (recibo) for a financial record in WebDiet. Pass the financeiro_id from webdiet_financeiro list. dados_recibo is a JSON array with 6 fields: [patient_name, cpf, address, city, nutritionist_name, crn_number]. After generating, the recibo_url in the financial record will point to the PDF receipt. Returns the receipt PDF URL that can be shared with the patient. Bulk support: accepts financeiro_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| dados_recibo | string | – | – |
| financeiro_id | string | yes | – |
| financeiro_ids | array | – | – |
| nome | string | yes | – |
No output schema declared.
No examples provided.
webdiet_save_antropometria ~794
Save body measurements (anthropometry) for a patient. Call webdiet_create_antropometria first to get the antropometria_id. All numeric values are strings. Provide raw measurements — calculated fields (IMC, GC%, density, fat mass, lean mass, classifications) are computed automatically server-side using the chosen formula. Sections: basic (peso/altura), skinfolds (10 dobras in mm), circumferences (20 fields in cm, bilateral pairs for limbs), bone diameters (3 fields in cm), bioimpedance (9 fields from scale). Formulas for body fat %: pollock3 (default), pollock7, guedes, petroski, durnin, faulkner, nenhuma. Density conversion: brozek (default) or siri. Side for CMB: esquerdo (default) or direito. Bulk support: accepts patient_ids, antropometria_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| altura_joelho | string | – | – |
| antropometria_id | string | yes | – |
| antropometria_ids | array | – | – |
| bioimpedancia_agua | string | – | – |
| bioimpedancia_gordura | string | – | – |
| bioimpedancia_idade | string | – | – |
| bioimpedancia_massa | string | – | – |
| bioimpedancia_massaGordura | string | – | – |
| bioimpedancia_massalivre | string | – | – |
| bioimpedancia_osseo | string | – | – |
| bioimpedancia_percentualMagra | string | – | – |
| bioimpedancia_visceral | string | – | – |
| c_abdomen | string | – | – |
| c_antebraco | string | – | – |
| c_antebraco_dir | string | – | – |
| c_bracocontraido | string | – | – |
| c_bracocontraido_dir | string | – | – |
| c_bracorelaxado | string | – | – |
| c_bracorelaxado_dir | string | – | – |
| c_cintura | string | – | – |
| c_coxadistal | string | – | – |
| c_coxadistal_dir | string | – | – |
| c_coxamedial | string | – | – |
| c_coxamedial_dir | string | – | – |
| c_coxaproximal | string | – | – |
| c_coxaproximal_dir | string | – | – |
| c_ombro | string | – | – |
| c_panturrilha | string | – | – |
| c_panturrilha_dir | string | – | – |
| c_pescoco | string | – | – |
| c_quadril | string | – | – |
| c_torax | string | – | – |
| diametro_femur | string | – | – |
| diametro_punho | string | – | – |
| diametro_umero | string | – | – |
| dobra_abdominal | string | – | – |
| dobra_axilar | string | – | – |
| dobra_biciptal | string | – | – |
| dobra_coxa | string | – | – |
| dobra_panturrilha | string | – | – |
| dobra_subescapular | string | – | – |
| dobra_supraespinhal | string | – | – |
| dobra_suprailiaca | string | – | – |
| dobra_toraxica | string | – | – |
| dobra_triceptal | string | – | – |
| estatura | string | – | – |
| estatura_sentado | string | – | – |
| formula_escolhida | string | – | – |
| lado | string | – | – |
| massa | string | – | – |
| origem | string | – | – |
| patient_id | string | yes | – |
| patient_ids | array | – | – |
| refAntropometria | string | – | – |
No output schema declared.
No examples provided.
webdiet_upload_anexo ~243
Upload a file (PDF, image, etc.) to a patient's attachments in WebDiet. Three ways to provide the file (use ONE): 1. upload_code — from webdiet_get_upload_command curl (RECOMMENDED for large files) 2. file_url — direct URL to download the file (e.g. https://example.com/report.pdf) 3. file_base64 — base64-encoded file content (small files only) Supported tipos: anexo (patient attachment — default), cloud (WebDiet Cloud storage), prontuario (clinical record), antropometria (body measurement report), exame (lab exam), perfil (patient photo), evolucao (photo evolution). Bulk support: accepts patient_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| file_base64 | string | – | – |
| file_name | string | – | – |
| file_url | string | – | – |
| nome_anexo | string | – | – |
| patient_id | string | yes | – |
| patient_ids | array | – | – |
| salvar_cloud | boolean | – | – |
| tipo | string | – | – |
| upload_code | string | – | – |
No output schema declared.
No examples provided.
How do I install the WebDiet MCP server?
WebDiet is a hosted endpoint at https://api.mcp.ai/p_webdiet, 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.mcp.ai
claude mcp add --transport http mcp-dir-webdiet-mcp 'https://api.mcp.ai/p_webdiet'
What is the WebDiet MCP server?
WebDiet is an MCP server listed in the public MCP registry as io.github.mcp-dir/webdiet-mcp. Patient, meal plan, prescription, chart and anthropometry management for dietitians. This page covers its hosted endpoint (https://api.mcp.ai/p_webdiet).
Is the WebDiet MCP server safe to use?
WebDiet 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 WebDiet MCP server expose?
WebDiet exposes 62 tools: webdiet_list_accounts, webdiet_patient_list, webdiet_patient_get, webdiet_patient_write_create, webdiet_patient_write_update, and 57 more. Their descriptions and schemas cost roughly 14,203 tokens of context every time the server is loaded.
Does the WebDiet MCP server require authentication?
No. We connected to WebDiet without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the WebDiet MCP server still maintained?
WebDiet 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 WebDiet MCP server?
VerifyMCP ran 11 checks on WebDiet, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about WebDiet: Authorization and HTTPS. 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.