x-twitter.searchLABSCO SUMMARY
One key instead of a dozen signups.
No single capability here is unique; not having to register separately for X, a backlink provider, a Maps key and a screenshot service — each with its own auth and billing — is. Failed calls are not charged, which matters most when an agent is exploring a catalog it has never used.
What it is
A hosted catalog of data and action capabilities exposed as MCP tools through a single endpoint. Every capability is also a REST endpoint with the same request shape and the same key, so agents call tools by name instead of HTTP paths.
What you get
- Clerk — users, organizations, sessions, invitations, API keys, machines, webhooks and instance settings inside your own Clerk application
- Domains — purchasable availability, quotes and registration, owned domains and DNS host records, plus public DNS, WHOIS, RDAP and TLD metadata
- Search and trends — Google Search keyword intelligence and traffic insights, Google Trends interest over time, related queries and regional breakdowns
- SEO — backlink analysis, domain authority, URL metrics and keyword research
- Social and media — X posts, users, timelines and bookmarks, with publish, reply and repost through connected accounts; YouTube and TikTok data; Rotten Tomatoes scores, reviews, cast and filmography
- Places — Google Maps place search, nearby lookups, place details, reviews and photos
- Utility — website screenshots, file upload and download, and free catalog-discovery helpers
Requirements
Nothing to install — connect to https://mcp.vee3.io/mcp over Streamable HTTP and pass VEE3_API_KEY as a request header. Keys come from app.vee3.io/dashboard/keys and there is a free tier. Tool calls are billed by token, and failed calls are not charged.
Setup effort
Add the hosted endpoint plus a key — paste it into your client, then supply credentials
USE CASES
01
Checking whether a product name is available
Brainstorm names, then test .com availability and register the one that survives, without leaving the conversation.
02
Reading what people posted about a topic this week
Search X for recent posts and summarise the discussion rather than guessing at it.
03
Finding topics with real search demand
Google Trends and keyword intelligence before writing, instead of after publishing.
04
Looking at a page the way a visitor would
Screenshot a public site and have the assistant judge design, readability and navigation from the image.
05
Managing your own Clerk users from chat
Users, organizations and sessions in your own Clerk application, read and changed through the same key.
6 tools
Listed in project docs. Your client may show a different list.
website-screenshots.capturegoogle-trends.interest_over_timedomains.check_availabilitygoogle-search.keyword_traffic_insightsyoutube.searchBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
VEE3_API_KEY in your environment
INSTALLATION
Connect your client
This one is configured rather than run — your client needs the configuration block, not a command.
Server setup
Configuration file
JSON
{
"mcpServers": {
"vee3": {
"url": "https://mcp.vee3.io/mcp",
"headers": {
"VEE3_API_KEY": "${env:VEE3_API_KEY}"
}
}
}
}VEE3_API_KEY (required): Your Vee3 API key. Create one at app.vee3.io/dashboard/keys. Pass it as a request header on the hosted MCP connection.
Hosted endpoint
ENDPOINT URL
https://mcp.vee3.io/mcpAdd this hosted endpoint to your MCP client using the credentials listed under Requirements.
