qrcode-pub-mcp
Related Servers
Alternatives to qrcode-pub-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP-capable agents to call 40 paid API tools—including OCR, PDF, image, tabular, and web utilities—by paying per request via x402 micropayments on Base, with no API key, subscription, or signup required.MIT

com.corenexis/apiofficial
AlicenseNot gradedqualityCmaintenanceA remote MCP server that lets AI agents generate PDFs from Markdown or HTML, extract text from images and PDFs, validate and screen email addresses, convert or host images, and create QR codes and barcodes. It also exposes account, subscription, and API-discovery tools, with every call running against the same REST quotas tied to the caller's own API key.MIT- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to read public web pages as clean markdown, verify whether a quote appears on a page, check the health of up to 25 links, and audit any origin's x402 and agent-readiness setup. Tools are pay-per-call in USDC on Base via x402 with free previews, requiring no signup or API key.MIT
- AlicenseBqualityFmaintenanceAn MCP server providing 22 pay-per-call utility tools for AI agents (scrape, validate, embed, store, moderate, notify, convert, prevent loops) without accounts or API keys, using USDC payments via the x402 protocol.1738 npm1MIT
- AlicenseNot gradedqualityFmaintenanceMulti-tool API for AI agents with MCP support: image generation (Flux), web scraping, TTS, OCR, QR codes, weather, crypto, PDF, screenshots, and more. Pay-per-use with x402 protocol.7 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to call pay-per-use tools for search, PDF processing, web reading, extraction, summarization, fact-checking, translation, jobs, and discovery, with each call paid in USDC on Base via x402 and no API key or account required.AGPL 3.0
TDQS
Scored across 4 tools
qr_code and host_file are clearly distinct, and page_to_markdown vs page_metadata differ by output (clean Markdown vs structured metadata/OG tags). The two page-fetching tools overlap in the fetch step and could be momentarily confused, but their return contracts are different enough to guide selection.
All names use snake_case (qr_code, page_to_markdown, page_metadata, host_file), which is consistent. The verb/noun style varies a bit (noun-only qr_code, noun_to_noun page_to_markdown, verb_noun host_file), but each name is readable and predictable.
Four tools is a compact, well-scoped set for a QR generation plus file-hosting/page-fetching utility. Slightly thin, but each tool earns its place and nothing looks redundant.
Generation (qr_code), fetching (page_to_markdown, page_metadata) and upload (host_file) are covered, but host_file returns a delete token with no corresponding delete tool, leaving a dead end for cleanup. No QR decoding or content-size/format management operations either.