SkanQRCode

What SkanQRCode MCP server does

The SkanQRCode MCP server connects an MCP-compatible agent to the SkanQRCode real-time URL and QR-code safety API. It provides agent-callable checks for URLs and IP addresses, allowing an agent workflow to evaluate a target before fetching or opening it.

The repository identifies the official package as @skanqrcode/mcp-server. The MCP implementation exposes two tools: check_url for target analysis and get_usage for account usage information. The broader SDK repository also contains TypeScript and Python examples for invoking the MCP server from custom agent applications.

How it works

The server communicates over stdio. An agent calls check_url with a URL or IP address, and the MCP server sends the request to SkanQRCode's check endpoint. The API returns a safety result based on statuses such as malicious, suspicious, or not_malicious. The underlying API also supplies a recommended action—allow, warn, or block—along with reasons and execution details.

Authentication uses a SkanQRCode API key. Paid plans use keys beginning with sk_live_, while the free sandbox plan uses sk_test_ keys. Sandbox results are intended for integration testing rather than production decisions.

Setup and configuration

Install the official @skanqrcode/mcp-server package and configure it as a stdio MCP server in the client you use. The repository includes a Claude Desktop configuration example, along with client examples in TypeScript and Python.

Set the SKANQRCODE_API_KEY environment variable for the process running the server. Use a live key for production traffic and a test key when validating an integration. The supplied material does not specify additional required environment variables or client configuration fields.

Tools and capabilities

The SkanQRCode MCP server exposes:

• check_url: submits a URL or IP address for a safety verdict before an agent opens or retrieves it.
• get_usage: retrieves usage information for the associated account.

The underlying SkanQRCode API also supports monthly and hourly usage endpoints, allow and block lists, billing-session URLs, and a health endpoint, but the MCP listing specifically identifies only check_url and get_usage as MCP tools.

Limitations and notes

The MCP server is intended for link-safety checks; it is not described as a general web-fetching or QR-code-scanning tool. QR decoding is handled locally in the repository's mobile examples, not by the MCP server itself.

API behavior, including response statuses and usage data, depends on the SkanQRCode account and key. Allow-list and block-list writes require an admin-scope key in the underlying API, and the allow list is limited to Pro and Business plans; these operations are not listed as MCP tools. The repository also notes that billing webhooks are not exposed for API clients.