YesTechie — UniFi Network & Security Integrator
REMOTE · YESTECHIE.COM
UniFi quotes, case studies and network, camera, access config guides from a nationwide integrator.
Available components
Last scanned (16 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Cloud Infrastructure
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 Security66
- 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 20 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 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 Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2536 tokens (~126/item across 20 items; 20 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 Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage76
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 27% 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 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 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
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
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: no authorisation is required to call this server, and 20 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 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.
- 25 Oct 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.
- 23 Oct 26 +4
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_about” rewrote its description, which is the text the model reads security
- Tool “get_clients” rewrote its description, which is the text the model reads security
- Tool “get_contact_info” rewrote its description, which is the text the model reads security
- Tool “get_coverage” rewrote its description, which is the text the model reads security
- Tool “get_join_our_team” rewrote its description, which is the text the model reads security
- Tool “get_pricing” rewrote its description, which is the text the model reads security
- Tool “get_site_info” rewrote its description, which is the text the model reads security
- Tool “get_team” rewrote its description, which is the text the model reads security
- Tool “get_unifi_questions” rewrote its description, which is the text the model reads security
- Tool “list_articles” rewrote its description, which is the text the model reads security
- Tool “list_pages” rewrote its description, which is the text the model reads security
- Tool “list_projects” rewrote its description, which is the text the model reads security
- Tool “list_services” rewrote its description, which is the text the model reads security
- Tool “submit_contact” rewrote its description, which is the text the model reads security
- Tool “submit_join_application” rewrote its description, which is the text the model reads security
- Tool “unifi_estimate” rewrote its description, which is the text the model reads security
- Schema quality: 108 → 126 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Destructive annotations: 0 → pass functional
- New tool “get_article” functional
- New tool “get_page” functional
- New tool “get_project” functional
- New tool “get_service” functional
- 22 Oct 26 60
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 5 Nov 2026 · Probed https://yestechie.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=yestechie.com | CN=WR3,O=Google Trust Services,C=US | 17 Oct 2026 | 15 Jan 2027 | RSA 2048 | SHA256-RSA | 6c9378323e247c740908bfe4bcff486d |
| SANs: yestechie.com, www.yestechie.com | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of yestechie.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| yestechie.com. | DS published | 23482, 64374 | 13, 13 | Verified |
| yestechie.com. | Verified address RRset verified with the apex keys |
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=31536000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://yestechie.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://yestechie.com/api/mcp | HTTPS enforced | 301 | https://yestechie.com:443/api/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 →
get_about About ~66
Company description, founders, office, contact and credentials. Use when the person asks who YesTechie is or whether it is licensed. (REST: GET /api/agent/v0/about)
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | – |
| fields | string | – | Comma-separated field names |
No output schema declared.
No examples provided.
get_article Article ~105
One practical configuration guide or technical article in full (UniFi network, Wi-Fi, cameras, access control, cabling): title, summary, author, tags, step-by-step body, headings, images and source links. Use when you know which guide answers the person (from list_articles) and need its steps. (REST: GET /api/agent/v0/articles/{idOrSlug})
| Name | Type | Req | Description |
|---|---|---|---|
| idOrSlug | string | yes | Numeric id or slug from the list tool |
No output schema declared.
No examples provided.
get_clients Clients ~65
Client logos, map count, deployments by state and city. Use when the person asks who YesTechie has worked for. (REST: GET /api/agent/v0/clients)
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | – |
| fields | string | – | Comma-separated field names |
No output schema declared.
No examples provided.
get_contact_info Contact info ~41
Office address, phone and email. Use when the person wants to reach YesTechie themselves. (REST: GET /api/agent/v0/contact-info)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_coverage Coverage ~72
Check whether YesTechie serves a location: California HQ, deployments by state and city, travel policy. Use when the person asks if YesTechie works in their area, or before quoting a site outside California. (REST: GET /api/agent/v0/coverage)
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | – |
No output schema declared.
No examples provided.
get_join_our_team Join our team ~50
Hiring page text, office address, phone and email. Use when the person asks about jobs at YesTechie. (REST: GET /api/agent/v0/join-our-team)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_page Page ~64
One published yestechie.com page as plain text with its canonical URL. Use when you need the full text of a page to cite (find the slug with list_pages). (REST: GET /api/agent/v0/pages/{slug})
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
get_pricing List prices ~126
Catalog list prices (USD, pre-tax, before scope): equipment (MSRP) or labor (standard rates). Use when the person asks what one item or labor task costs; use unifi_estimate for a whole project. (REST: GET /api/agent/v0/pricing/{equipment|labor})
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| detail | string | – | – |
| fields | string | – | Comma-separated field names |
| kind | string | yes | – |
| limit | integer | – | – |
| page | integer | – | – |
| q | string | – | – |
No output schema declared.
No examples provided.
get_project Project ~99
One completed YesTechie project case study in full: title, summary, tags, the write-up (typically client background and challenge, solution and equipment, results), headings, photos and videos. Use when the person wants details of a real deployment like theirs (find it with list_projects). (REST: GET /api/agent/v0/projects/{idOrSlug})
| Name | Type | Req | Description |
|---|---|---|---|
| idOrSlug | string | yes | Numeric id or slug from the list tool |
No output schema declared.
No examples provided.
get_service Service ~74
One YesTechie service in full: what is included and how it is delivered. Use when the person asks about a specific service (find it with list_services). (REST: GET /api/agent/v0/services/{idOrSlug})
| Name | Type | Req | Description |
|---|---|---|---|
| idOrSlug | string | yes | Numeric id or slug from the list tool |
No output schema declared.
No examples provided.
get_site_info Site index ~49
Every public YesTechie agent endpoint with URL, methods, auth and size. Use when you are unsure which tool fits; start here. (REST: GET /api/agent/v0/site)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_team Team ~80
Published founders (list), or one founder in full with idOrSlug. Use when the person asks who runs YesTechie. (REST: GET /api/agent/v0/team[/{idOrSlug}])
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | – |
| fields | string | – | Comma-separated field names |
| idOrSlug | string | – | – |
No output schema declared.
No examples provided.
get_unifi_questions Estimate questions ~62
Step 1: returns the questions and JSON template to fill for unifi_estimate. Use when the person wants a price for a project. (REST: GET /api/agent/v0/unifi_estimate/questions)
| Name | Type | Req | Description |
|---|---|---|---|
| view | string | – | – |
No output schema declared.
No examples provided.
list_articles Articles ~185
Practical configuration guides and technical articles: UniFi network, Wi-Fi, cameras (Protect) and access control (Access, Identity, intercom), plus cabling and home networking. One item returns title, summary, author, tags, the full step-by-step body, headings and source links. Use when the person asks how to set up, configure or choose UniFi network, Wi-Fi, camera or door-access gear. Lean list (id, slug, url, title, summary, date; page/limit/fields/detail), or one item in full with idOrSlug. (REST: GET /api/agent/v0/articles[/{idOrSlug}])
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | – |
| fields | string | – | Comma-separated field names |
| idOrSlug | string | – | – |
| limit | integer | – | – |
| page | integer | – | – |
No output schema declared.
No examples provided.
list_pages Pages ~63
Every published page with its canonical URL, or one page as plain text with slug. Use when you need to cite or link a yestechie.com page. (REST: GET /api/agent/v0/pages[/{slug}])
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | – | – |
No output schema declared.
No examples provided.
list_projects Projects ~170
Completed YesTechie projects: real case studies from installs (warehouses, plants, offices, schools, churches, gated sites). One item returns title, summary, tags, the full write-up (typically client background and challenge, solution and equipment, results), headings, photos and videos. Use when the person wants real deployment examples / case studies. Lean list (id, slug, url, title, summary, date; page/limit/fields/detail), or one item in full with idOrSlug. (REST: GET /api/agent/v0/projects[/{idOrSlug}])
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | – |
| fields | string | – | Comma-separated field names |
| idOrSlug | string | – | – |
| limit | integer | – | – |
| page | integer | – | – |
No output schema declared.
No examples provided.
list_services Services ~129
Published YesTechie services (what we install and operate). Use when the person asks what YesTechie does or whether it offers a service. Lean list (id, slug, url, title, summary, date; page/limit/fields/detail), or one item in full with idOrSlug. (REST: GET /api/agent/v0/services[/{idOrSlug}])
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | – |
| fields | string | – | Comma-separated field names |
| idOrSlug | string | – | – |
| limit | integer | – | – |
| page | integer | – | – |
No output schema declared.
No examples provided.
submit_contact Contact YesTechie ~158
Request a site survey or callback. Attach quoteRef. Use when the person explicitly asks to be contacted and has supplied name and email or phone; it sends a real email. 3 per IP and 2 per email per day. (REST: POST /api/agent/v0/contact)
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| fullName | string | yes | – |
| idempotencyKey | string | – | Sent as the Idempotency-Key header (retry safely) |
| message | string | yes | – |
| organization | string | – | – |
| phone | string | – | – |
| quoteRef | string | – | Optional: the quoteRef from get_quote / unifi_estimate (valid 24 h). Attaches that estimate to the request. |
No output schema declared.
No examples provided.
submit_join_application Join our team ~141
Apply to join the team, exactly like the /join-our-team form. Use when the person asks to apply. Sends real email to YesTechie and a confirmation to the sender: call only when the person asked you to. 3 per IP and 2 per email per day. (REST: POST /api/agent/v0/join-our-team)
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| fullName | string | yes | – |
| idempotencyKey | string | – | Sent as the Idempotency-Key header (retry safely) |
| message | string | yes | – |
| organization | string | – | – |
| phone | string | – | – |
No output schema declared.
No examples provided.
unifi_estimate UniFi estimate ~134
Itemized price for a UniFi Wi-Fi, camera and door-access install at a given site address. Input the filled question set from get_unifi_questions. Returns equipment, labor, travel lines, totals and a quoteRef. Nothing is saved or sent. Use when the person wants a price for Wi-Fi, cameras or door access at a real address. (REST: POST /api/agent/v0/unifi_estimate)
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | yes | The filled question set template (site, infra, wifi, cameras, access, doors[], doorDefaults, gates[], ...) |
| detail | string | – | – |
No output schema declared.
No examples provided.
How do I install the YesTechie — UniFi Network & Security Integrator MCP server?
YesTechie — UniFi Network & Security Integrator is a hosted endpoint at https://yestechie.com/api/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 · yestechie.com
claude mcp add --transport http com-yestechie-site 'https://yestechie.com/api/mcp'
What is the YesTechie — UniFi Network & Security Integrator MCP server?
YesTechie — UniFi Network & Security Integrator is an MCP server listed in the public MCP registry as com.yestechie/site. UniFi quotes, case studies and network, camera, access config guides from a nationwide integrator. This page covers its hosted endpoint (https://yestechie.com/api/mcp).
Is the YesTechie — UniFi Network & Security Integrator MCP server safe to use?
YesTechie — UniFi Network & Security Integrator 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 YesTechie — UniFi Network & Security Integrator MCP server expose?
YesTechie — UniFi Network & Security Integrator exposes 20 tools: get_site_info, get_about, get_team, get_contact_info, get_join_our_team, and 15 more. Their descriptions and schemas cost roughly 1,933 tokens of context every time the server is loaded.
Does the YesTechie — UniFi Network & Security Integrator MCP server require authentication?
No. We connected to YesTechie — UniFi Network & Security Integrator without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the YesTechie — UniFi Network & Security Integrator MCP server still maintained?
YesTechie — UniFi Network & Security Integrator is still listed as active in the MCP registry. We last reached this channel on 5 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 YesTechie — UniFi Network & Security Integrator MCP server?
VerifyMCP ran 12 checks on YesTechie — UniFi Network & Security Integrator, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about YesTechie — UniFi Network & Security Integrator: Authorization. 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.