Qr_check_server

Created By
footusera year ago
传入图片的url,利用二阶段方式,识别并检测图片中二维码的位置和内容(Pass in the URL of the image and use a two-stage method to identify and detect the location and content of the QR code in the image.)
Overview

what is Qr_check_server?

Qr_check_server is a tool designed to enhance the accuracy of QR code recognition in images by utilizing a two-stage detection method.

how to use Qr_check_server?

To use Qr_check_server, pass the URL of the image containing the QR code, and the server will identify and detect the location and content of the QR code.

key features of Qr_check_server?

  • Two-stage detection for improved accuracy
  • Utilizes YOLOv8 model for initial QR code location detection
  • Employs WeChat's open-source model for QR code content extraction

use cases of Qr_check_server?

  1. Recognizing QR codes in large images where they are small and difficult to detect.
  2. Extracting information from QR codes for applications in marketing and customer engagement.
  3. Integrating with other applications to automate QR code processing.

FAQ from Qr_check_server?

  • Can Qr_check_server recognize all types of QR codes?

Yes! It is designed to recognize various QR code formats.

  • Is Qr_check_server easy to set up?

Yes! Simply install the required packages and run the provided scripts.

  • What are the performance metrics of Qr_check_server?

The tool processes images with a speed of approximately 3.0ms for preprocessing and 268.3ms for inference.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
footuser
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago