deep_article_audit — Japanese Article Deep Audit MCP Tool
deep_article_audit
(deep article audit) is one of 1 tool on the
Japanese Article Deep Audit
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call deep_article_audit from your client
- Claude Code Japanese Article Deep Audit deep_article_audit run in your project directory
- Claude Desktop Japanese Article Deep Audit deep_article_audit ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Japanese Article Deep Audit deep_article_audit ~/.cursor/mcp.json
- VS Code Japanese Article Deep Audit deep_article_audit .vscode/mcp.json
- Zed Japanese Article Deep Audit deep_article_audit ~/.config/zed/settings.json
- Windsurf Japanese Article Deep Audit deep_article_audit ~/.codeium/windsurf/mcp_config.json
- Cline Japanese Article Deep Audit deep_article_audit ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Japanese Article Deep Audit deep_article_audit ~/.gemini/settings.json
- Grok Japanese Article Deep Audit deep_article_audit .mcp.json (in your project root)
- ChatGPT Japanese Article Deep Audit deep_article_audit Settings → Connectors → Advanced → Developer mode
- Claude.ai Japanese Article Deep Audit deep_article_audit Settings → Connectors → Add custom connector
- LangChain Japanese Article Deep Audit deep_article_audit pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http jp-article-check-paid https://jp-article-check-paid.9gbnk9sztm.workers.dev/mcp
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.