Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SentryFi - Wi-Fi Safety

REMOTE · SENTRYFI.MCP.SROFIA.COM

SentryFi Wi-Fi safety app (App Store, Google Play): who is on my Wi-Fi, public Wi-Fi risk.

+3 this week 76 Trust /100

Last scanned (23 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

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 Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • 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
Schema Quality & AI Usability72
  • 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 1703 tokens (~425/item across 4 items; 3 tools + 1 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 Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 93% 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 3 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
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

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 →

Changelog

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 9 Nov 26 70

    First indexed and scored.

Diagnostics

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://sentryfi.mcp.srofia.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=srofia.com CN=WE1,O=Google Trust Services,C=US 3 Nov 2026 1 Feb 2027 ECDSA 256 ECDSA-SHA256 8e52703af1683a1b0edfdc25d59e7550
SANs: srofia.com, sentryfi.mcp.srofia.com, *.sentryfi.mcp.srofia.com
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 sentryfi.mcp.srofia.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
srofia.com. 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://sentryfi.mcp.srofia.com/mcp Verified 200
http (plaintext) http://sentryfi.mcp.srofia.com/mcp HTTPS enforced 301 https://sentryfi.mcp.srofia.com/mcp
MCP tools · 3 exposed · ~1,629 tokens

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 →

Tool Tokens
check_public_wifi_risk ~523

Use this when the user is about to join, or is on, hotel, airport, café (coffee shop), rental, campus or other public Wi-Fi and asks "is public wifi safe", "is hotel wifi safe", whether to do banking or work there, whether a sign-in page or a network name looks fake (evil twin / fake wifi), or what to watch out for. Also use it when they ask who can see their browsing on hotel or café Wi-Fi ("can the wifi owner see my history", "does incognito hide my browsing", "does a VPN protect me on public wifi"): the card shows what the Wi-Fi owner, hotel, other guests or a VPN provider can and cannot see, and how HTTPS, a VPN or encrypted DNS change that. Fill in what the user said; use "unknown" or null for anything they did not say rather than guessing. Returns a 0–100 score (100 = no warning signs) from their answers, the signals behind it, advice per activity, who can see what, and a checklist for that venue. Do not use for home Wi-Fi security or hack worries (use secure_my_wifi), for recommending VPN or security products, to monitor or read another person's activity, or for getting onto a network without permission. Does not scan or connect to any network; works only from what the user tells ChatGPT.

NameTypeReqDescription
activitiesarray–What the user wants to do on this network.
certificateWarningboolean|null–true if the device showed a certificate or "not private" warning.
encryptedDnsboolean–Private DNS / DNS over HTTPS turned on.
httpsOnlyboolean–Only HTTPS sites (HTTPS-only mode on).
mobileDataAvailableboolean––
nameConfirmedboolean|null–true if the exact network name was confirmed with staff or an official sign.
securitystring–open = no password; shared_password = one password for everyone (e.g. on a card); private_password = only you have it; enterprise_login = personal username/password (e.g. eduroam).
signInAsksarray–What the sign-in page asks for.
signInPagestring–Whether a sign-in (captive) page appeared and if its address started with https or http.
similarNetworkNamesboolean|null–true if several networks with similar names are visible.
usingVpnboolean––
venuestringyesWhere the Wi-Fi is.

No output schema declared.

No examples provided.

identify_wifi_devices ~330

Use this when the user asks "who is on my wifi", "who is using my wifi", sees an unknown device on their network, wants to identify devices connected to their router, asks "what is this device on my network", or wants a MAC address lookup (MAC address vendor) for one address. Pass the devices they pasted from their own router or app: the name and the first 6 characters of the MAC address (e.g. F0:18:98) for each; only the first 6 characters are used, and the rest of the address and the IP are not needed. For a single lookup pass one entry; if the user does not have the list yet, pass an empty list (and the router brand if known) to get the steps for finding it. Returns the maker of each device from the public IEEE registry, a likely device type, flags (private/randomized address, unknown maker, cameras and smart-home devices), which ones are worth checking, next steps and where to find the list for common routers. Do not use to scan a network, find a person or their location, monitor someone, or get into another person's network. Does not scan or connect to any network; works only from what the user tells ChatGPT.

NameTypeReqDescription
devicesarrayyesDevices from the router or app list, one entry per row. For a single MAC address lookup, pass one entry. Pass an empty list to get the steps for finding the list on the router.
routerBrandstring–Router or internet provider, if known. generic = not sure.

No output schema declared.

No examples provided.

secure_my_wifi ~776

Use this when the user asks how to secure their home Wi-Fi or router ("how to secure my wifi", "secure wifi from hackers", "router security settings"), how to change their Wi-Fi password or where it is shown, whether to turn off WPS or UPnP, whether to set up a guest network for smart-home devices, "can my router or internet provider see my history at home" or "do I need a VPN at home". Also use it when they suspect their own home Wi-Fi or router was hacked ("is my wifi hacked", "is my router hacked", "someone is using my wifi"): fill in the symptom answers they gave (unknown devices, a router login that stopped working, changed DNS, redirects or pop-ups, a Wi-Fi name or password that changed, slow internet, busy router lights) and use null for anything they did not say rather than guessing. Returns a router hardening checklist ranked by impact (admin password, WPA3/WPA2-AES, Wi-Fi password, firmware, WPS, remote admin, UPnP, guest/IoT network, network name, DNS), steps already done marked, brand-specific password steps and a neutral answer on privacy and VPNs at home; when symptoms are given it adds hack signals out of 100 (100 = none of the answers point to a break-in), common causes that are not a hack and ordered first steps. Do not use to hack, crack or get into a network the user does not own, to find or watch another person, to recommend VPN or security products, or for public Wi-Fi safety (use check_public_wifi_risk). Does not scan or connect to any network; works only from what the user tells ChatGPT.

NameTypeReqDescription
adminPasswordDefaultboolean|null–true if the router admin password is still the default one from the sticker or manual.
alreadyDonearray–Steps the user says they have already done; they are marked done and moved to the end.
cantLogIntoRouterboolean|null–true if the router admin password that used to work no longer works.
dnsChangedboolean|null–true if the router or a device shows DNS servers the user did not set.
firmwareOutdatedboolean|null–true if router updates are not installed, or the router no longer gets updates.
lightsAtNightboolean|null–true if the router lights blink a lot when nobody seems to be using it.
needsUpnpboolean|null–true if a game console, voice chat or home server needs UPnP (e.g. "strict NAT" without it).
passwordSharedWidelyboolean|null–true if the Wi-Fi password has been given to many people (neighbours, past guests, ex-roommates).
redirectsOnAllDevicesboolean|null–true if the redirects/pop-ups happen on every device on this Wi-Fi, false if only on one device.
redirectsOrPopupsboolean|null–true if browsers jump to odd sites, fake login pages or show pop-ups.
routerBrandstring–Router or internet provider, if known.
slowInternetboolean|null–true if the internet has become slow.
smartHomestring–How many smart-home devices (cameras, plugs, bulbs, speakers, TVs) are on the network. many = moves the guest/IoT network step up.
unknownDevicesboolean|null–true if the router lists devices the user does not recognise.
wifiSettingsChangedboolean|null–true if the Wi-Fi name or password changed without the user doing it.
wpsOnboolean|null–true if WPS (push-button / PIN pairing) is on.

No output schema declared.

No examples provided.

Install

How do I install the SentryFi - Wi-Fi Safety MCP server?

SentryFi - Wi-Fi Safety is a hosted endpoint at https://sentryfi.mcp.srofia.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 · sentryfi.mcp.srofia.com

# add to Claude Code
claude mcp add --transport http com-srofia-sentryfi 'https://sentryfi.mcp.srofia.com/mcp'
Common questions

What is the SentryFi - Wi-Fi Safety MCP server?

SentryFi - Wi-Fi Safety is an MCP server listed in the public MCP registry as com.srofia/sentryfi. SentryFi Wi-Fi safety app (App Store, Google Play): who is on my Wi-Fi, public Wi-Fi risk. This page covers its hosted endpoint (https://sentryfi.mcp.srofia.com/mcp).

Is the SentryFi - Wi-Fi Safety MCP server safe to use?

SentryFi - Wi-Fi Safety scores 76 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 SentryFi - Wi-Fi Safety MCP server expose?

SentryFi - Wi-Fi Safety exposes 3 tools: check_public_wifi_risk, identify_wifi_devices, secure_my_wifi. Their descriptions and schemas cost roughly 1,629 tokens of context every time the server is loaded.

Does the SentryFi - Wi-Fi Safety MCP server require authentication?

No. We connected to SentryFi - Wi-Fi Safety without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SentryFi - Wi-Fi Safety MCP server still maintained?

SentryFi - Wi-Fi Safety 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 SentryFi - Wi-Fi Safety MCP server?

VerifyMCP ran 14 checks on SentryFi - Wi-Fi Safety, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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.