whatmount — TV and monitor mount facts
REMOTE · WHATMOUNT.COM · SCANNED SEP 24
VESA pattern, dimensions and weight per TV or monitor model, from the makers' manuals. Read-only.
Available components
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 323 tokens (~107/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 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 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the whatmount — TV and monitor mount facts MCP server?
whatmount — TV and monitor mount facts is a hosted endpoint at https://whatmount.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 · whatmount.com
claude mcp add --transport http com-whatmount-lookup 'https://whatmount.com/mcp'
{
"mcpServers": {
"com-whatmount-lookup": {
"url": "https://whatmount.com/mcp"
}
}
} {
"servers": {
"com-whatmount-lookup": {
"type": "http",
"url": "https://whatmount.com/mcp"
}
}
} [mcp_servers.com-whatmount-lookup] url = "https://whatmount.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-whatmount-lookup": {
"type": "remote",
"url": "https://whatmount.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-whatmount-lookup --url 'https://whatmount.com/mcp' --transport streamable-http
mcp_servers:
com-whatmount-lookup:
url: "https://whatmount.com/mcp" {
"McpServers": {
"com-whatmount-lookup": {
"Transport": "http",
"Url": "https://whatmount.com/mcp"
}
}
} assistant mcp add com-whatmount-lookup -t streamable-http -u 'https://whatmount.com/mcp'
{
"mcpServers": {
"com-whatmount-lookup": {
"type": "http",
"url": "https://whatmount.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 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.
- 15 Sept 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.
- 13 Sept 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.
- 11 Sept 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.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
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 24 Sept 2026 · Probed https://whatmount.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=whatmount.com | CN=WE1,O=Google Trust Services,C=US | 24 Aug 2026 | 23 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 9ab90cf4d47b33980efb306a168dd91f |
| SANs: whatmount.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 whatmount.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| whatmount.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://whatmount.com/mcp | Verified | 200 | |
| http (plaintext) | http://whatmount.com/mcp | HTTPS enforced | 301 | https://whatmount.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 →
list_models_by_vesa_pattern Models that use a VESA pattern ~74
Every covered TV or monitor whose mounting pattern is the given VESA size, e.g. 200x200 or 400x300, with page URLs. Useful for "which TVs fit my mount".
| Name | Type | Req | Description |
|---|---|---|---|
| pattern | string | yes | Width x height in mm, e.g. 400x400 |
No output schema declared.
No examples provided.
lookup_tv_mount_specs TV or monitor mount specs by model ~110
The VESA mounting pattern, dimensions with and without stand, weight and screen size for a TV or monitor model number, from the manufacturer's manual or spec sheet, with the whatmount.com page to cite. Give the model number as printed on the label (e.g. UN65TU7000, 65Q650G).
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | Brand, optional, e.g. Samsung |
| model | string | yes | Model number, e.g. QN55Q60A |
No output schema declared.
No examples provided.
search_tv_models Search covered TV and monitor models ~74
Find which TV or monitor models whatmount.com has published mount facts for, by brand, model fragment or screen size. Returns up to 10 with their facts and page URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Brand, model fragment or size, e.g. "Hisense 65" or "TCL Q6" |
No output schema declared.
No examples provided.
What is the whatmount — TV and monitor mount facts MCP server?
whatmount — TV and monitor mount facts is an MCP server listed in the public MCP registry as com.whatmount/lookup. VESA pattern, dimensions and weight per TV or monitor model, from the makers' manuals. Read-only. This page covers its hosted endpoint (https://whatmount.com/mcp).
Is the whatmount — TV and monitor mount facts MCP server safe to use?
whatmount — TV and monitor mount facts scores 79 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 whatmount — TV and monitor mount facts MCP server expose?
whatmount — TV and monitor mount facts exposes 3 tools: lookup_tv_mount_specs, search_tv_models, list_models_by_vesa_pattern. Their descriptions and schemas cost roughly 258 tokens of context every time the server is loaded.
Does the whatmount — TV and monitor mount facts MCP server require authentication?
No. We connected to whatmount — TV and monitor mount facts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the whatmount — TV and monitor mount facts MCP server still maintained?
whatmount — TV and monitor mount facts is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.