Safe Bite
REMOTE · WWW.SAFEBITER.COM
Restaurant inspections for Chicago, NYC, Minneapolis, Milwaukee, Austin, and Denver.
Available components
Last scanned (22 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 22 Oct 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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability85
- 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
- Tool/resource definitions use about 765 tokens (~69/item across 11 items; 4 tools + 7 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 22 Oct 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 21 Oct 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 20 Oct 26 +4
- Stability: unverified → 0.03 ▲ functional
- MCP protocol: fail → pass ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 19 Oct 26 65
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 22 Oct 2026 · Probed https://www.safebiter.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.safebiter.com | CN=YR1,O=Let's Encrypt,C=US | 4 Oct 2026 | 2 Jan 2027 | RSA 2048 | SHA256-RSA | 5ae35c41e63c4776e2f6b8f5cdcef4ae20e |
| SANs: *.safebiter.com, safebiter.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 insecure
Validation of www.safebiter.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| safebiter.com. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.safebiter.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.safebiter.com/mcp | HTTPS enforced | 308 | https://www.safebiter.com/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 →
find_nearby_restaurants ~205
Find restaurants within a given radius of a location and return each restaurant's last 3 inspections (newest first). Accepts either explicit latitude/longitude or an address string (geocoded via Google Maps). Default radius is a quarter mile (0.25).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Optional street address; resolved to lat/lng via Google Maps Geocoding API. Used only if latitude/longitude are not supplied. |
| city | string | – | Optional city filter. |
| history_n | integer | – | How many recent inspections to include per restaurant. Default 3. |
| latitude | number | – | Center latitude in decimal degrees. Required if no address is provided. |
| limit | integer | – | Max restaurants to return (1-100). |
| longitude | number | – | Center longitude in decimal degrees. Required if no address is provided. |
| radius_miles | number | – | Search radius in miles. Defaults to 0.25 (a quarter mile). |
No output schema declared.
No examples provided.
get_city_inspections ~160
Get restaurant inspection records for one city: chicago, nyc, minneapolis, milwaukee, austin, or denver. Page by repeating the call with the previous response's next_offset until has_more is false. The response includes total_count, offset, limit, has_more, and next_offset.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City to query: chicago, nyc, minneapolis, milwaukee, austin, or denver. |
| limit | integer | – | Number of records per request (1-500). Use 500 to get maximum data per call for large datasets. |
| offset | integer | – | Number of records to skip, for pagination. Pass the previous response's next_offset to get the next page. Default 0. |
No output schema declared.
No examples provided.
get_milwaukee_inspections ~122
Get Milwaukee restaurant food inspection data with full pagination support. Response includes pagination metadata (total_count, offset, limit, has_more, next_offset) to guide further requests. To page through all records, repeat the call passing next_offset until has_more is false.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of records per request (1-500). Use 500 to get maximum data per call. |
| offset | integer | – | Number of records to skip, for pagination. Pass the previous response's next_offset to get the next page. Default 0. |
No output schema declared.
No examples provided.
search_restaurants ~150
Fuzzy-search restaurants by name across Chicago, NYC, Minneapolis, Milwaukee, Austin, and Denver. Tolerates misspellings and partial names. Returns one entry per restaurant with its recent inspections, newest first, and a similarity score.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Optional city scope. |
| history_n | integer | – | How many recent inspections to include per restaurant. Default 3. |
| limit | integer | – | Max number of matches to return (1-50). |
| query | string | yes | Restaurant name or partial name (e.g., 'giordanos', 'shake shak'). |
| threshold | number | – | Fuzzy match threshold between 0 and 1 (higher = stricter). |
No output schema declared.
No examples provided.
How do I install the Safe Bite MCP server?
Safe Bite is a hosted endpoint at https://www.safebiter.com/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 · www.safebiter.com
claude mcp add --transport http andrewvg23-safe-bite 'https://www.safebiter.com/mcp'
What is the Safe Bite MCP server?
Safe Bite is an MCP server listed in the public MCP registry as io.github.AndrewVG23/safe-bite. Restaurant inspections for Chicago, NYC, Minneapolis, Milwaukee, Austin, and Denver. This page covers its hosted endpoint (https://www.safebiter.com/mcp).
Is the Safe Bite MCP server safe to use?
Safe Bite scores 70 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 Safe Bite MCP server expose?
Safe Bite exposes 4 tools: get_milwaukee_inspections, get_city_inspections, search_restaurants, find_nearby_restaurants. Their descriptions and schemas cost roughly 637 tokens of context every time the server is loaded.
Does the Safe Bite MCP server require authentication?
No. We connected to Safe Bite without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Safe Bite MCP server still maintained?
Safe Bite is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.