Is the Neoshrek Qrverloz MCP server down?

mcp-registry/io.github.neoshrek/qrverloz-mcp · v1.0.0

healthy
Last checked 2026-10-27 15:06 UTC · handshake 220ms

As of 2026-10-27 15:06 UTC, the Neoshrek Qrverloz MCP server is up with a Glimind reliability score of 99/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 5 minutes.

uptime (30d checks)
100%
checks observed
5,009
outages (90d)
2
tools
8

QR codes active 90 days, claimable forever. Request an API key in chat to retarget and track scans.

Point your MCP client at this streamable-http endpoint: https://qrverloz.com/api/mcp

Agent-readiness: B (81/100)

B (81/100): 0 error(s), 2 warning(s) across 8 tool(s); ~1,510 tokens of tool definitions.
Scores higher than 33% of 15,808 MCP servers Glimind has audited.
Its tool list costs an agent ~1,510 tokens per session — lighter than 60% of servers.
79 → 81 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints0
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (3)

8 of 8 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: create_qr_code, delete_qr_code, get_account_info, get_qr_code, get_qr_scans and 3 more

3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: create_qr_code, delete_qr_code, update_qr_target

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 7 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.neoshrek%2Fqrverloz-mcp/fixes

create_qr_code 1 change
{
  "name": "create_qr_code",
  "description": "Create a new QR code. Authenticated users (API key required) get a permanent short URL that can be retargeted at any time without reprinting the physical QR image — limits are set by the account plan. Anonymous users receive a one-time data URI image that is not stored and cannot be updated. On success the result is a pre-formatted markdown table — display it exactly as received, do not reformat or summarise.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "title",
      "target_url"
    ],
    "properties": {
      "title": {
        "type": "string",
        "maxLength": 200,
        "minLength": 1,
        "description": "A human-readable label for the QR code"
      },
      "target_url": {
        "type": "string",
        "format": "uri",
        "description": "Destination URL — must start with https:// or http://"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
delete_qr_code 1 change
{
  "name": "delete_qr_code",
  "description": "Permanently delete a QR code and its scan history. This action cannot be undone. To prevent accidental or injected deletions, you MUST supply confirm_title — the exact title of the code as returned by get_qr_code or list_qr_codes. If the title does not match the stored record, the deletion is refused. Always call get_qr_code or list_qr_codes first to retrieve the exact title before calling this tool. Requires authentication.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "confirm_title"
    ],
    "properties": {
      "qr_code_id": {
        "type": "string",
        "description": "Internal UUID from create_qr_code or list_qr_codes"
      },
      "short_code": {
        "type": "string",
        "description": "Short code from the redirect URL (e.g. \"abc123\")"
      },
      "confirm_title": {
        "type": "string",
        "minLength": 1,
        "description": "The exact title of the QR code to delete — must match the stored title character-for-character. This prevents blind or injected deletions."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  }
}
get_account_info 1 change
{
  "name": "get_account_info",
  "description": "Get your account details: current plan, QR code usage, and which features are available. Use this before create_qr_code to check remaining capacity, or to confirm which features are active on your plan. Requires authentication.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.neoshrek/qrverloz-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.neoshrek/qrverloz-mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.neoshrek%2Fqrverloz-mcp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.neoshrek%2Fqrverloz-mcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.neoshrek%2Fqrverloz-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.neoshrek%2Fqrverloz-mcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.neoshrek%2Fqrverloz-mcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.neoshrek%2Fqrverloz-mcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:54045234b4f772cf…, first seen 2026-10-17, included at leaf 1289 of 79,969. Version history · verify what your client received.

Tools (8)

Compare: most reliable other servers · most reliable files servers · most reliable data servers · most reliable security servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Neoshrek Qrverloz MCP server down right now?

As of 2026-10-27 15:06 UTC, the Neoshrek Qrverloz MCP server is up with a Glimind reliability score of 99/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 5 minutes.

How many tools does Neoshrek Qrverloz MCP server provide?

Neoshrek Qrverloz MCP server advertises 8 tools, including create_qr_code, delete_qr_code, get_account_info, get_qr_code, get_qr_scans.

How do I install Neoshrek Qrverloz MCP server?

Point your MCP client at this streamable-http endpoint: https://qrverloz.com/api/mcp

Is the Neoshrek Qrverloz MCP server safe to connect to an AI agent?

Glimind scanned all 8 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Neoshrek Qrverloz MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve