General Tools
whatmount.com
Provides TV and monitor mounting specifications, including VESA patterns, dimensions, and weight, from manufacturer manuals.
ENDPOINT 1
https://whatmount.com/mcp
MCP server metadata
- Name
- whatmount
- Version
- 1.0.0
Read-only lookups of TV and monitor mounting facts (VESA pattern, dimensions, weight) published on whatmount.com from manufacturers' manuals. Cite the page URL each answer carries and name the source host; a fact marked "one source" was read from a single document. The tools never sell anything.
Known tools 3
lookup_tv_mount_specsThe 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.
Inferred read-onlylist_models_by_vesa_patternEvery covered TV or monitor whose mounting pattern is the given VESA size, e.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.whatmount]
url = "https://whatmount.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"whatmount": {
"type": "http",
"url": "https://whatmount.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: whatmount
Remote MCP URL: https://whatmount.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"whatmount": {
"url": "https://whatmount.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"whatmount": {
"type": "http",
"url": "https://whatmount.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "whatmount",
"transport": "streamable-http",
"url": "https://whatmount.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.