KnownGate
REMOTE · MCP.KNOWNGATE.COM
Food verification for people and AI agents: evidence-backed verdicts, with sources and dates.
Available components
Last scanned (9 hours ago)
Scores higher than 96% of remote servers
Reachable. Last reached 6 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 Security91
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 648 tokens (~162/item across 4 items; 4 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 Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Oct 26 0
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Sept 26 0
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 6 Nov 2026 · Probed https://mcp.knowngate.com
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.knowngate.com | CN=YR1,O=Let's Encrypt,C=US | 2 Nov 2026 | 31 Jan 2027 | RSA 2048 | SHA256-RSA | 639e7bacb0e5023503fe55cefce140cc7f3 |
| SANs: mcp.knowngate.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.knowngate.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| knowngate.com. | DS published | 6818 | 13 | Verified |
| mcp.knowngate.com. | Verified address RRset verified with the apex keys |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="knowngate", error="invalid_token"
Bearer realm="knowngate", error="invalid_token"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(self) |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | No resource metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.knowngate.com | Verified | 200 | |
| http (plaintext) | http://mcp.knowngate.com | HTTPS enforced | 308 | https://mcp.knowngate.com/ |
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 →
check_item ~204
Rule one food subject against the household premise (restrictions, thresholds, or both). Needs a key (Authorization: Bearer kg_live_…); create a free one with the register tool. Returns one of four verdicts (no_conflict_found, conflict_found, ask_one_question, couldnt_verify) with typed hits, source kind and read date. Unknown counts as no; the word safe is never used.
| Name | Type | Req | Description |
|---|---|---|---|
| restrictions | array | yes | Household restrictions. FDA-9 keys ("peanut", "sesame", "milk", …) as strings, or { key, note } when a note matters (e.g. { key: "tree_nut", note: "cashew" }). May be empty when thresholds carry the… |
| subject | object | yes | – |
| thresholds | array | – | Numeric premise (beta): per-serving nutrient bounds ruled against the product's typed panel. Unknown values refuse honestly, never zero. An empty array means no numeric limits. |
No output schema declared.
No examples provided.
check_plan ~192
Rule a set of items at once: a recipe's ingredients, a basket, several days. Needs a key (Authorization: Bearer kg_live_…); create a free one with the register tool. Up to 25 subjects, one call, one verdict per item plus a summary line. Each item carries its own evidence, source and read date.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| restrictions | array | yes | Household restrictions. FDA-9 keys ("peanut", "sesame", "milk", …) as strings, or { key, note } when a note matters (e.g. { key: "tree_nut", note: "cashew" }). May be empty when thresholds carry the… |
| thresholds | array | – | Numeric premise (beta): per-serving nutrient bounds ruled against the product's typed panel. Unknown values refuse honestly, never zero. An empty array means no numeric limits. |
No output schema declared.
No examples provided.
check_venue ~161
Rule a whole venue's published chart against the household restrictions in one call. Needs a key (Authorization: Bearer kg_live_…); create a free one with the register tool. Returns per-verdict counts, the most severe items, the operator's cross-contact caveat verbatim, and the chart's source and read date. A venue with no machine-readable chart says so honestly.
| Name | Type | Req | Description |
|---|---|---|---|
| restrictions | array | yes | Household restrictions. FDA-9 keys ("peanut", "sesame", "milk", …) as strings, or { key, note } when a note matters (e.g. { key: "tree_nut", note: "cashew" }). May be empty when thresholds carry the… |
| venue | object | yes | – |
No output schema declared.
No examples provided.
register ~91
Sign yourself up for a developer key without leaving MCP. The email is contact and recovery, not a wall. One key per email, free tier (100 checks a month); the key is in this response and never shown again. Nothing on knowngate.com itself needs a key.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | yes | Who is signing up, e.g. your product name |
| contact_email | string | yes | – |
No output schema declared.
No examples provided.
How do I install the KnownGate MCP server?
KnownGate is a hosted endpoint at https://mcp.knowngate.com/, 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 · mcp.knowngate.com
claude mcp add --transport http com-knowngate-verify 'https://mcp.knowngate.com/'
What is the KnownGate MCP server?
KnownGate is an MCP server listed in the public MCP registry as com.knowngate/verify. Food verification for people and AI agents: evidence-backed verdicts, with sources and dates. This page covers its hosted endpoint (https://mcp.knowngate.com).
Is the KnownGate MCP server safe to use?
KnownGate scores 89 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 KnownGate MCP server expose?
KnownGate exposes 4 tools: check_item, check_venue, check_plan, register. Their descriptions and schemas cost roughly 648 tokens of context every time the server is loaded.
Does the KnownGate MCP server require authentication?
Yes. KnownGate 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 KnownGate MCP server still maintained?
KnownGate is still listed as active in the MCP registry. We last reached this channel on 6 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 KnownGate MCP server?
VerifyMCP ran 13 checks on KnownGate, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.