check_eeat — Pa1m SEO MCP Tool Read-only
check_eeat
(check eeat) is one of 36 tools on the
Pa1m SEO
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_eeat from your client
- Claude Code Pa1m SEO check_eeat run in your project directory
- Claude Desktop Pa1m SEO check_eeat ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Pa1m SEO check_eeat ~/.cursor/mcp.json
- VS Code Pa1m SEO check_eeat .vscode/mcp.json
- Zed Pa1m SEO check_eeat ~/.config/zed/settings.json
- Windsurf Pa1m SEO check_eeat ~/.codeium/windsurf/mcp_config.json
- Cline Pa1m SEO check_eeat ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Pa1m SEO check_eeat ~/.gemini/settings.json
- Grok Pa1m SEO check_eeat .mcp.json (in your project root)
- ChatGPT Pa1m SEO check_eeat Settings → Connectors → Advanced → Developer mode
- Claude.ai Pa1m SEO check_eeat Settings → Connectors → Add custom connector
- LangChain Pa1m SEO check_eeat pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport sse pa1m-seo https://seo.hypa1m.xyz/mcp
Other tools on this server
- get_status
- scan_quick
- scan_full
- check_core_seo
- check_performance
- check_links
- check_images
- check_security
- check_technical
- check_crawlability
- check_structured_data
- check_js_rendering
- check_accessibility
- check_content
- check_social
- check_url_structure
- check_redirects
- check_mobile
- check_i18n
- check_html
- check_ai_geo
- check_legal
- brief
- analyze_endpoint
- google_index_submit
- google_index_submit_bulk
- google_index_check
- google_index_check_bulk
- backlinks_check
- backlinks_check_bulk
- google_index_status
- google_index_report
- google_check_status
- google_check_report
- backlinks_status
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.