Vee3
REMOTE · MCP.VEE3.IO · SCANNED SEP 21
Hosted MCP with 91 agent tools: X, domains, SEO, Maps, Trends, Search, YouTube, TikTok, and more.
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 Security57
- 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 269 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
- 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 Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 39348 tokens (~146/item across 269 items; 269 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 48 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "clerk.delete_domain" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 270 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Vee3 MCP server?
Vee3 is a hosted endpoint at https://mcp.vee3.io/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 · mcp.vee3.io
claude mcp add --transport http vee3io-vee3 'https://mcp.vee3.io/mcp'
{
"mcpServers": {
"vee3io-vee3": {
"url": "https://mcp.vee3.io/mcp"
}
}
} {
"servers": {
"vee3io-vee3": {
"type": "http",
"url": "https://mcp.vee3.io/mcp"
}
}
} [mcp_servers.vee3io-vee3] url = "https://mcp.vee3.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vee3io-vee3": {
"type": "remote",
"url": "https://mcp.vee3.io/mcp",
"enabled": true
}
}
} openclaw mcp add vee3io-vee3 --url 'https://mcp.vee3.io/mcp' --transport streamable-http
mcp_servers:
vee3io-vee3:
url: "https://mcp.vee3.io/mcp" {
"McpServers": {
"vee3io-vee3": {
"Transport": "http",
"Url": "https://mcp.vee3.io/mcp"
}
}
} assistant mcp add vee3io-vee3 -t streamable-http -u 'https://mcp.vee3.io/mcp'
{
"mcpServers": {
"vee3io-vee3": {
"type": "http",
"url": "https://mcp.vee3.io/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.
- 21 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 20 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 19 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 18 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 17 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 16 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 15 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 14 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
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 21 Sept 2026 · Probed https://mcp.vee3.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.vee3.io | CN=WR3,O=Google Trust Services,C=US | 10 Sept 2026 | 9 Dec 2026 | RSA 2048 | SHA256-RSA | 248a528be637c1a5097d6fe4b9f6a11b |
| SANs: mcp.vee3.io | ||||||
| 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 insecure
Validation of mcp.vee3.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| vee3.io. | 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://mcp.vee3.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.vee3.io/mcp | HTTPS enforced | 302 | https://mcp.vee3.io/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 →
x-twitter.delete_post ~152
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| post_id | string | yes | – |
| user_id | – | – | – |
| user_name | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| deleted | – | – | – |
| user_id | – | – | – |
| user_name | – | – | – |
No examples provided.
x-twitter.edit_post ~320
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| made_with_ai | – | – | – |
| media | array | – | – |
| paid_partnership | – | – | – |
| post_id | string | yes | – |
| text | – | – | – |
| user_id | – | – | – |
| user_name | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| post_id | – | – | – |
| text | – | – | – |
| user_id | – | – | – |
| user_name | – | – | – |
No examples provided.
x-twitter.get_bookmarks ~198
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| limit | – | – | – |
| user_id | – | – | – |
| user_name | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
| includes | – | – | – |
| next_cursor | – | – | – |
| result_count | – | – | – |
No examples provided.
x-twitter.reply_to_post ~478
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| auto_populate_reply_metadata | – | – | – |
| card_uri | – | – | – |
| community_id | – | – | – |
| direct_message_deep_link | – | – | – |
| exclude_reply_user_ids | – | – | – |
| for_super_followers_only | – | – | – |
| made_with_ai | – | – | – |
| media | array | – | – |
| nullcast | – | – | – |
| paid_partnership | – | – | – |
| poll | – | – | – |
| reply_settings | – | – | – |
| reply_to_post_id | string | yes | – |
| share_with_followers | – | – | – |
| text | – | – | – |
| user_id | – | – | – |
| user_name | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| post_id | – | – | – |
| text | – | – | – |
| user_id | – | – | – |
| user_name | – | – | – |
No examples provided.
x-twitter.repost_post ~164
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| post_id | string | yes | – |
| user_id | – | – | – |
| user_name | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| post_id | – | – | – |
| retweeted | – | – | – |
| user_id | – | – | – |
| user_name | – | – | – |
No examples provided.
x-twitter.search ~115
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| query | string | yes | – |
| search_type | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| next_cursor | – | – | – |
| prev_cursor | – | – | – |
| status | – | – | – |
| timeline | – | – | – |
No examples provided.
x-twitter.tweet_info ~77
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| author | – | – | – |
| bookmarks | – | – | – |
| conversation_id | – | – | – |
| created_at | – | – | – |
| id | – | – | – |
| lang | – | – | – |
| likes | – | – | – |
| media | – | – | – |
| quotes | – | – | – |
| replies | – | – | – |
| retweets | – | – | – |
| text | – | – | – |
No examples provided.
x-twitter.tweet_replies ~95
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| next_cursor | – | – | – |
| prev_cursor | – | – | – |
| status | – | – | – |
| timeline | – | – | – |
No examples provided.
x-twitter.unrepost_post ~155
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| post_id | string | yes | – |
| user_id | – | – | – |
| user_name | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| retweeted | – | – | – |
| user_id | – | – | – |
| user_name | – | – | – |
No examples provided.
x-twitter.user_info ~130
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| rest_id | – | – | – |
| user_name | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliates | – | – | – |
| avatar | – | – | – |
| blue_verified | – | – | – |
| business_account | – | – | – |
| created_at | – | – | – |
| desc | – | – | – |
| friends | – | – | – |
| header_image | – | – | – |
| id | – | – | – |
| location | – | – | – |
| media_count | – | – | – |
| name | – | – | – |
| pinned_tweet_ids_str | – | – | – |
| profile | – | – | – |
| protected | – | – | – |
| rest_id | – | – | – |
| status | – | – | – |
| statuses_count | – | – | – |
| sub_count | – | – | – |
| verification_type | – | – | – |
No examples provided.
x-twitter.user_timeline ~160
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| rest_id | – | – | – |
| user_name | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| next_cursor | – | – | – |
| pinned | – | – | – |
| prev_cursor | – | – | – |
| status | – | – | – |
| timeline | – | – | – |
| user | – | – | – |
No examples provided.
youtube.channel_details ~143
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| artistBio | – | – | – |
| avatar | – | – | – |
| badges | – | – | – |
| banner | – | – | – |
| canonicalBaseUrl | – | – | – |
| channelId | – | – | – |
| country | – | – | – |
| description | – | – | – |
| hasBusinessEmail | – | – | – |
| isFamilySafe | – | – | – |
| isVerified | – | – | – |
| isVerifiedArtist | – | – | – |
| joinedDate | – | – | – |
| joinedDateText | – | – | – |
| keywords | – | – | – |
| links | – | – | – |
| stats | – | – | – |
| title | – | – | – |
| username | – | – | – |
No examples provided.
youtube.channel_search ~141
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | – |
| cursor | – | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| contents | – | – | – |
| cursorNext | – | – | – |
No examples provided.
youtube.channel_videos ~147
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | – |
| cursor | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| videos | – | – | – |
No examples provided.
youtube.playlist_details ~87
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| playlist_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| author | – | – | – |
| badges | – | – | – |
| description | – | – | – |
| playlistId | – | – | – |
| stats | – | – | – |
| thumbnails | – | – | – |
| title | – | – | – |
| updatedTime | – | – | – |
| updatedTimeText | – | – | – |
No examples provided.
youtube.search ~441
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| content_type | – | – | – |
| cursor | – | – | – |
| duration | – | – | – |
| features | – | – | – |
| language | string | – | – |
| location | string | – | – |
| query | string | yes | – |
| sort_by | – | – | – |
| upload_date | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| contents | – | – | – |
| cursorNext | – | – | – |
| didYouMean | – | – | – |
| estimatedResults | – | – | – |
| unappliedFilters | – | – | – |
No examples provided.
youtube.search_autocomplete ~98
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | – |
| location | string | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| query | – | – | – |
| results | – | – | – |
No examples provided.
youtube.video_comments ~167
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| sort_by | – | – | – |
| video_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| comments | – | – | – |
| cursorNext | – | – | – |
| totalCommentsCount | – | – | – |
No examples provided.
youtube.video_details ~146
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| video_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| author | – | – | – |
| category | – | – | – |
| channel_id | – | – | – |
| description | – | – | – |
| is_live_content | – | – | – |
| keywords | – | – | – |
| number_of_views | – | – | – |
| published_time | – | – | – |
| thumbnails | – | – | – |
| title | – | – | – |
| type | – | – | – |
| video_id | – | – | – |
| video_length | – | – | – |
No examples provided.
What is the Vee3 MCP server?
Vee3 is an MCP server listed in the public MCP registry as io.github.Vee3io/vee3. Hosted MCP with 91 agent tools: X, domains, SEO, Maps, Trends, Search, YouTube, TikTok, and more. This page covers its hosted endpoint (https://mcp.vee3.io/mcp).
Is the Vee3 MCP server safe to use?
Vee3 scores 76 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.
Does the Vee3 MCP server require authentication?
No. We connected to Vee3 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Vee3 MCP server still maintained?
Vee3 is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.