get_content_standards — VASTlint MCP Tool Read-only
get_content_standards
(get content standards) is one of 15 tools on the
VASTlint
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_content_standards from your client
- Claude Code VASTlint get_content_standards run in your project directory
- Claude Desktop VASTlint get_content_standards ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor VASTlint get_content_standards ~/.cursor/mcp.json
- VS Code VASTlint get_content_standards .vscode/mcp.json
- Zed VASTlint get_content_standards ~/.config/zed/settings.json
- Windsurf VASTlint get_content_standards ~/.codeium/windsurf/mcp_config.json
- Cline VASTlint get_content_standards ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI VASTlint get_content_standards ~/.gemini/settings.json
- Grok VASTlint get_content_standards .mcp.json (in your project root)
- ChatGPT VASTlint get_content_standards Settings → Connectors → Advanced → Developer mode
- Claude.ai VASTlint get_content_standards Settings → Connectors → Add custom connector
- LangChain VASTlint get_content_standards pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport sse vastlint https://vastlint.org/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.