Receipt signing public key — qeaas mcp MCP Resource
Receipt signing public key
is one of 3 resources on the
qeaas mcp
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Receipt signing public key from your client
- Claude Code qeaas mcp Resource/Receipt signing public key run in your project directory
- Claude Desktop qeaas mcp Resource/Receipt signing public key ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor qeaas mcp Resource/Receipt signing public key ~/.cursor/mcp.json
- VS Code qeaas mcp Resource/Receipt signing public key .vscode/mcp.json
- Zed qeaas mcp Resource/Receipt signing public key ~/.config/zed/settings.json
- Windsurf qeaas mcp Resource/Receipt signing public key ~/.codeium/windsurf/mcp_config.json
- Cline qeaas mcp Resource/Receipt signing public key ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI qeaas mcp Resource/Receipt signing public key ~/.gemini/settings.json
- Grok qeaas mcp Resource/Receipt signing public key .mcp.json (in your project root)
- ChatGPT qeaas mcp Resource/Receipt signing public key Settings → Connectors → Advanced → Developer mode
- Claude.ai qeaas mcp Resource/Receipt signing public key Settings → Connectors → Add custom connector
- LangChain qeaas mcp Resource/Receipt signing public key pip install langchain-mcp-adapters
Other resources on this server
qeaas mcp also offers 1 prompt — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 24 September 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.