media_content_verification — Cybercentry Verification MCP Tool
media_content_verification
(media content verification) is one of 12 tools on the
Cybercentry Verification
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call media_content_verification from your client
- Claude Code Cybercentry Verification media_content_verification run in your project directory
- Claude Desktop Cybercentry Verification media_content_verification ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Cybercentry Verification media_content_verification ~/.cursor/mcp.json
- VS Code Cybercentry Verification media_content_verification .vscode/mcp.json
- Zed Cybercentry Verification media_content_verification ~/.config/zed/settings.json
- Windsurf Cybercentry Verification media_content_verification ~/.codeium/windsurf/mcp_config.json
- Cline Cybercentry Verification media_content_verification ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Cybercentry Verification media_content_verification ~/.gemini/settings.json
- Grok Cybercentry Verification media_content_verification .mcp.json (in your project root)
- ChatGPT Cybercentry Verification media_content_verification Settings → Connectors → Advanced → Developer mode
- Claude.ai Cybercentry Verification media_content_verification Settings → Connectors → Add custom connector
- LangChain Cybercentry Verification media_content_verification pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http verification https://centry.cybercentry.co.uk/api/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.