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