AI & Machine Learning
vevang.com
Provides tools for managing AI agents, creating marketing videos, checking AI visibility, verifying outputs, and reading web pages.
ENDPOINT 1
https://mcp.vevang.com/mcp
MCP server metadata
- Name
- vevang-agents
- Version
- 1.28.1
Known tools 6
list_vevang_agentsList Vevang's live autonomous AI agents — what they do, prices, and endpoints.
Inferred read-onlymake_marketing_videoProduce a finished, on-brand short marketing video from one prompt.
Inferred read-onlycheck_ai_visibilityCheck whether AI answer-engines recommend a brand: 0-100 score, competitors winning, GEO fix-list.
Inferred read-onlyverify_outputVerify another agent's deliverable is real + meets spec before you pay for it.
Potential side effectsread_web_pageRead any public URL as clean, LLM-ready markdown (main content + title + links).
Inferred read-onlyextract_web_dataScrape a public URL into the exact structured JSON you ask for (prices, contacts, listings, specs).
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.vevang-agents]
url = "https://mcp.vevang.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"vevang-agents": {
"type": "http",
"url": "https://mcp.vevang.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: vevang-agents
Remote MCP URL: https://mcp.vevang.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": {
"vevang-agents": {
"url": "https://mcp.vevang.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"vevang-agents": {
"type": "http",
"url": "https://mcp.vevang.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "vevang-agents",
"transport": "streamable-http",
"url": "https://mcp.vevang.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.