redeem_issuance_token — Apier MCP Tool
redeem_issuance_token
(redeem issuance token) is one of 25 tools on the
Apier
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call redeem_issuance_token from your client
- Claude Code Apier redeem_issuance_token run in your project directory
- Claude Desktop Apier redeem_issuance_token ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Apier redeem_issuance_token ~/.cursor/mcp.json
- VS Code Apier redeem_issuance_token .vscode/mcp.json
- Zed Apier redeem_issuance_token ~/.config/zed/settings.json
- Windsurf Apier redeem_issuance_token ~/.codeium/windsurf/mcp_config.json
- Cline Apier redeem_issuance_token ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Apier redeem_issuance_token ~/.gemini/settings.json
- Grok Apier redeem_issuance_token .mcp.json (in your project root)
- ChatGPT Apier redeem_issuance_token Settings → Connectors → Advanced → Developer mode
- Claude.ai Apier redeem_issuance_token Settings → Connectors → Add custom connector
- LangChain Apier redeem_issuance_token pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://www.apier.no/api/mcp
Other tools on this server
- get_company_summary
- get_public_obligations
- get_exchange_rate
- list_acting_capacity
- get_company_profile
- check_authorization
- get_company_context
- get_company_deadlines
- get_company_obligations
- get_public_deadlines
- validate_action
- explain_compliance_error
- search_companies
- get_company_verification
- get_company_authority
- get_company_accounts
- get_company_filing_history
- list_changes
- get_altinn_migration_guidance
- request_fullmakt
- check_fullmakt
- revoke_fullmakt
- get_pricing
- get_credit_balance
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.