tokenos-audit.html — TokenOS Smart Contract Audit MCP Resource
tokenos-audit.html
is one of 1 resource on the
TokenOS Smart Contract Audit
MCP server. Connect the server and your client can attach it as context.
by client
How to attach tokenos-audit.html from your client
- Claude Code TokenOS Smart Contract Audit Resource/tokenos-audit.html run in your project directory
- Claude Desktop TokenOS Smart Contract Audit Resource/tokenos-audit.html ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TokenOS Smart Contract Audit Resource/tokenos-audit.html ~/.cursor/mcp.json
- VS Code TokenOS Smart Contract Audit Resource/tokenos-audit.html .vscode/mcp.json
- Zed TokenOS Smart Contract Audit Resource/tokenos-audit.html ~/.config/zed/settings.json
- Windsurf TokenOS Smart Contract Audit Resource/tokenos-audit.html ~/.codeium/windsurf/mcp_config.json
- Cline TokenOS Smart Contract Audit Resource/tokenos-audit.html ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TokenOS Smart Contract Audit Resource/tokenos-audit.html ~/.gemini/settings.json
- Grok TokenOS Smart Contract Audit Resource/tokenos-audit.html .mcp.json (in your project root)
- ChatGPT TokenOS Smart Contract Audit Resource/tokenos-audit.html Settings → Connectors → Advanced → Developer mode
- Claude.ai TokenOS Smart Contract Audit Resource/tokenos-audit.html Settings → Connectors → Add custom connector
- LangChain TokenOS Smart Contract Audit Resource/tokenos-audit.html pip install langchain-mcp-adapters
TokenOS Smart Contract Audit also offers 4 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 14 November 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.