Safefood 360 MCP by usefulapi
REMOTE · SAFEFOOD-360.USEFULAPI.IO
Read Safefood 360 documents, complaints, suppliers, materials; create complaints, update documents.
Available components
Last scanned (3 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 Oct 2026.
Category Documents and Files
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2235 tokens (~131/item across 17 items; 17 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 Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.0.3 functional
- 24 Oct 26 62
First indexed and scored.
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 25 Oct 2026 · Probed https://safefood-360.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| 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 safefood-360.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://safefood-360.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://safefood-360.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://safefood-360.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://safefood-360.usefulapi.io/mcp |
| Authorisation server | https://safefood-360.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://safefood-360.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/safefood-360/ |
| http (plaintext) | http://safefood-360.usefulapi.io/mcp | Inconclusive | 302 | http://safefood-360.usefulapi.io/mcp |
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 →
safefood360_create_complaint Create complaint ~322
WRITE: record a NEW complaint in Safefood 360 (it may trigger the site's complaint workflow and notifications). Not idempotent: calling it twice creates two complaints. Safefood 360 validates the fields (ids such as source, company and recorded_by are GUIDs from your site's lists) and rejects a request that lacks required ones. POST /complaints/sites/{siteId}/v1/complaints/.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | – | Customer/company id (GUID) the complaint is about. |
| contact_person | object | – | The complainant. |
| date | string | – | When the complaint was received, ISO 8601, e.g. 2026-10-20T09:30:00Z. |
| description | string | yes | What the complaint is about. |
| product_id | string | – | Id (GUID) of the product, material or service complained about. |
| quantity | integer | – | Quantity affected. |
| recorded_by | string | – | User id (GUID) of the person recording the complaint. |
| reference | string | – | The complainant's own reference. |
| risk | string | – | Risk level as named in Safefood 360, e.g. None, Low, Medium, High. |
| sample_details | string | – | Sample request and collection details. |
| source | string | – | Complaint source id (GUID) from the site's list of sources. |
| source_details | string | – | Free-text details of the source. |
| trace_no | string | – | Batch / trace number of the product. |
No output schema declared.
No examples provided.
safefood360_get_batching_record Get batching record ~59
One batching (traceability) record by its id (GUID). GET /batching/sites/{siteId}/v1/batching/records/{recordId}.
| Name | Type | Req | Description |
|---|---|---|---|
| record_id | string | yes | Batching record id (GUID). |
No output schema declared.
No examples provided.
safefood360_get_complaint Get complaint ~62
One complaint by its id (GUID). GET /complaints/sites/{siteId}/v1/complaints/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| complaint_id | string | yes | Complaint id (GUID), e.g. from safefood360_list_complaints. |
No output schema declared.
No examples provided.
safefood360_get_customer Get customer ~56
One customer by its identifier (name, addresses, phone, notes). The vendor offers no customer list. GET /customers/sites/{siteId}/v1/customers/{identifier}.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Customer identifier. |
No output schema declared.
No examples provided.
safefood360_get_document Get document ~63
One controlled document by its identifier: title, description, version, folder, responsible person and workflow. GET /documents/sites/{siteId}/v1/documents/{identifier}.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Document identifier (as shown in Safefood 360). |
No output schema declared.
No examples provided.
safefood360_get_document_review Get document review ~46
One document review by its review number. GET /documents/sites/{siteId}/v1/documentreviews/{no}.
| Name | Type | Req | Description |
|---|---|---|---|
| review_no | string | yes | Document review number. |
No output schema declared.
No examples provided.
safefood360_get_employee Get employee ~70
One employee record by its identifier (training/HR master data of the site). Contains personal data: use it only for the question asked. The vendor offers no employee list. GET /employees/sites/{siteId}/v1/employees/{identifier}.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Employee identifier. |
No output schema declared.
No examples provided.
safefood360_get_final_product Get final product ~74
One final (finished) product by its identifier: name, folder, categories, barcode, specifications and the materials it is made of. The vendor offers no final-product list. GET /finalproducts/sites/{siteId}/v1/finalproducts/{identifier}.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Final product identifier. |
No output schema declared.
No examples provided.
safefood360_get_material Get material ~43
One material by its external id. GET /v1/materials/{externalId}?siteId=.
| Name | Type | Req | Description |
|---|---|---|---|
| external_id | string | yes | Material external id. |
No output schema declared.
No examples provided.
safefood360_get_supplier Get supplier ~44
One supplier by its external id. GET /v1/suppliers/{externalId}?siteId=.
| Name | Type | Req | Description |
|---|---|---|---|
| external_id | string | yes | Supplier external id. |
No output schema declared.
No examples provided.
safefood360_list_complaints List complaints ~195
List customer complaints (number, name, risk, date, company, source, contact person, product/material, description, created/modified). Supports OData $filter, $orderby, $top, $skip and $count. GET /complaints/sites/{siteId}/v1/complaints.
| Name | Type | Req | Description |
|---|---|---|---|
| count | boolean | – | Include the total count of matching records in the reply. |
| filter | string | – | OData $filter, e.g. "date ge 2026-01-01T00:00:00Z" (comparison, logical and string operators). |
| orderby | string | – | OData $orderby, e.g. "date desc,name asc". |
| skip | integer | – | Records to skip (offset). Pass the previous reply's next_skip. |
| top | integer | – | Records per page, 1-1000 (the vendor default is 100). |
No output schema declared.
No examples provided.
safefood360_list_document_reviews List document reviews ~187
List document reviews (the periodic review records of controlled documents). Supports OData $filter, $orderby, $top, $skip and $count; use it to find reviews that are due or overdue. GET /documents/sites/{siteId}/v1/documentreviews/.
| Name | Type | Req | Description |
|---|---|---|---|
| count | boolean | – | Include the total count of matching records in the reply. |
| filter | string | – | OData $filter, e.g. "date ge 2026-01-01T00:00:00Z" (comparison, logical and string operators). |
| orderby | string | – | OData $orderby, e.g. "date desc,name asc". |
| skip | integer | – | Records to skip (offset). Pass the previous reply's next_skip. |
| top | integer | – | Records per page, 1-1000 (the vendor default is 100). |
No output schema declared.
No examples provided.
safefood360_list_documents List documents ~194
List controlled documents of the Safefood 360 site (title, description, version, folder, responsible person, review/approval workflow, created/modified). Supports OData $filter, $orderby, $top, $skip and $count. GET /documents/sites/{siteId}/v1/documents/.
| Name | Type | Req | Description |
|---|---|---|---|
| count | boolean | – | Include the total count of matching records in the reply. |
| filter | string | – | OData $filter, e.g. "date ge 2026-01-01T00:00:00Z" (comparison, logical and string operators). |
| orderby | string | – | OData $orderby, e.g. "date desc,name asc". |
| skip | integer | – | Records to skip (offset). Pass the previous reply's next_skip. |
| top | integer | – | Records per page, 1-1000 (the vendor default is 100). |
No output schema declared.
No examples provided.
safefood360_list_materials List materials ~157
List materials/ingredients (name, our code, supplier code, description, category, countries of origin, risk, archived flag). Paged with start_index and limit; the reply carries recordCount and next_start_index. GET /v1/materials/?siteId=.
| Name | Type | Req | Description |
|---|---|---|---|
| is_archived | boolean | – | true = archived records, false = active records (default: the vendor's default). |
| limit | integer | – | Records per page, 1-100 (default 30). |
| order | string | – | Sort direction. |
| sort | string | – | Field to sort by. |
| start_index | integer | – | Index of the first record (default 0). Pass the previous reply's next_start_index. |
No output schema declared.
No examples provided.
safefood360_list_suppliers List suppliers ~151
List suppliers (name, code, addresses, contacts, approval status, risk, establishment numbers). Paged with start_index and limit; the reply carries recordCount and next_start_index. GET /v1/suppliers/?siteId=.
| Name | Type | Req | Description |
|---|---|---|---|
| is_archived | boolean | – | true = archived records, false = active records (default: the vendor's default). |
| limit | integer | – | Records per page, 1-100 (default 30). |
| order | string | – | Sort direction. |
| sort | string | – | Field to sort by. |
| start_index | integer | – | Index of the first record (default 0). Pass the previous reply's next_start_index. |
No output schema declared.
No examples provided.
safefood360_update_customer Update customer ~121
WRITE: change the name, phone, mobile and/or notes of a customer in Safefood 360 (JSON patch of those fields; others stay as they are). notes REPLACES the existing notes. PATCH /customers/sites/{siteId}/v1/customers/{identifier}.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Customer identifier. |
| mobile | string | – | New mobile number. |
| name | string | – | New customer name. |
| notes | string | – | New notes (replaces the existing notes). |
| phone | string | – | New phone number. |
No output schema declared.
No examples provided.
safefood360_update_document Update document ~116
WRITE: change the title, description and/or folder of a controlled document in Safefood 360 (JSON patch; fields you leave out stay as they are). It does not publish a new version or change the review workflow. Returns the updated document. PATCH /documents/sites/{siteId}/v1/documents/{identifier}.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | New description. |
| folder | string | – | Folder to move the document to. |
| identifier | string | yes | Document identifier. |
| title | string | – | New title. |
No output schema declared.
No examples provided.
How do I install the Safefood 360 MCP by usefulapi server?
Safefood 360 MCP by usefulapi is a hosted endpoint at https://safefood-360.usefulapi.io/mcp, 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 · safefood-360.usefulapi.io
claude mcp add --transport http io-usefulapi-safefood-360 'https://safefood-360.usefulapi.io/mcp'
What is the Safefood 360 MCP by usefulapi server?
Safefood 360 MCP by usefulapi is listed in the public MCP registry as io.usefulapi/safefood-360. Read Safefood 360 documents, complaints, suppliers, materials; create complaints, update documents. This page covers its hosted endpoint (https://safefood-360.usefulapi.io/mcp).
Is the Safefood 360 MCP by usefulapi server safe to use?
Safefood 360 MCP by usefulapi scores 62 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 Safefood 360 MCP by usefulapi server expose?
Safefood 360 MCP by usefulapi exposes 17 tools: safefood360_list_documents, safefood360_get_document, safefood360_list_document_reviews, safefood360_get_document_review, safefood360_list_complaints, and 12 more. Their descriptions and schemas cost roughly 1,960 tokens of context every time the server is loaded.
Does the Safefood 360 MCP by usefulapi server require authentication?
Yes. Safefood 360 MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Safefood 360 MCP by usefulapi server still maintained?
Safefood 360 MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.