Data Collection
whenwhat.com
Retrieves and lists content from the Milk Interactive website, including pages, projects, team members, and awards.
ENDPOINT 1
https://whenwhat.com/mcp
MCP server metadata
- Name
- Whenwhat
- Version
- 1.0.0
Known tools 8
list_pagesList all pages on the Milk Interactive website with titles, URLs, and descriptions.
Inferred read-onlylist_projectsList all projects/case studies by Milk Interactive with title, description, category tags, and URL.
Inferred read-onlylist_awardsList all awards won by Milk Interactive, grouped by award program, with year and category.
Inferred read-onlylist_faqsList frequently asked questions about Milk Interactive and their services, with answers.
Inferred read-onlyget_company_infoGet detailed company information: name, address, phone, email, social media links, and description.
Potential side effectsCONNECT 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.whenwhat]
url = "https://whenwhat.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"whenwhat": {
"type": "http",
"url": "https://whenwhat.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: whenwhat
Remote MCP URL: https://whenwhat.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": {
"whenwhat": {
"url": "https://whenwhat.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"whenwhat": {
"type": "http",
"url": "https://whenwhat.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "whenwhat",
"transport": "streamable-http",
"url": "https://whenwhat.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.