Security & Testing
vetmytoken.com
VetMyToken is a security analytics MCP server that scans tokens for risk, reports deployer history and past incidents, and provides accuracy metrics for its verdicts.
ENDPOINT 1
https://vetmytoken.com/mcp
MCP server metadata
- Name
- vetmytoken
- Version
- 1
VetMyToken scans crypto tokens and publishes one verdict per token, with every claim traced to the source that established it. Use scan_token for a specific token, get_deployer_history for the wallet behind it, get_incidents for what has collapsed recently and what was said about it beforehand, and get_accuracy for how the verdicts have performed. Quote the sentences as they come back and link the web_url so a reader can see the evidence behind them.
Known tools 4
scan_tokenReturn VetMyToken's verdict for one token: a risk band, a score out of 100, and the plain-language findings behind them.
Inferred read-onlyget_deployer_historyReturn what this site has recorded about the wallet that deployed a token: how many tokens it launched that we scanned, how many of those later lost their liquidity, and how long they lasted.
Inferred read-onlyget_incidentsReturn recent token collapses this site recorded, each with the verdict it carried BEFORE the collapse.
Inferred read-onlyget_accuracyReturn how this site's verdicts have actually performed: for each of the 7, 30 and 90-day windows, how many predictions were made before their outcomes were known and how those outcomes fell.
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.vetmytoken]
url = "https://vetmytoken.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"vetmytoken": {
"type": "http",
"url": "https://vetmytoken.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: vetmytoken
Remote MCP URL: https://vetmytoken.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": {
"vetmytoken": {
"url": "https://vetmytoken.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"vetmytoken": {
"type": "http",
"url": "https://vetmytoken.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "vetmytoken",
"transport": "streamable-http",
"url": "https://vetmytoken.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.