OnlineCyberTools MCP (280+ filterable tools)

osint_qr_code_generator

Read-onlyIdempotent

Build QR code payloads for plain text, URLs, WiFi, vCard, SMS, or email. Returns a ready-to-render image URL.

Instructions

QR Code Payload Builder. Build the encoded text payload for a QR code from one of six input types — plain text, a URL, WiFi credentials (WIFI:…), a vCard contact, an SMS draft, or a mailto email — and return a ready-to-render image URL. Use this to prepare QR content; use osint_qr_code_scanner to decode an existing QR image, osint_barcode_generator for UPC/EAN/Code128 barcodes, and security_totp_qr_generator for 2FA otpauth:// codes. The API call runs locally and is read-only, non-destructive, deterministic, and rate-limited (20 req/min anonymous); the returned serviceUrl points at the third-party api.qrserver.com renderer, which a client fetches separately to obtain the PNG. Returns the encoded content, its length, the normalized settings, and that render URL.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`type`	Yes	Payload type to encode. Unknown values fall back to text. (qrType is accepted as an alias.)	text
`qrType`	No	Alias for type; used when type is absent.
`inputs`	No	Per-type fields; only the object matching type is read.
`settings`	No	Rendering options applied to the serviceUrl.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`success`	No	True when the payload was built.
`result`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed36 schema fields changedv0.5.1Jun 3, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / inputs / additionalProperties
```
Added value: +false
```

addedInput schema / properties / inputs / description

Added value: +"Per-type fields; only the object matching type is read."

addedInput schema / properties / inputs / properties / contact

Added value: +{
+  "additionalProperties": false,
+  "description": "vCard 3.0 fields (type=contact).",
+  "properties": {
+    "email": {
+      "type": "string"
+    },
+    "firstName": {
+      "type": "string"
+    },
+    "lastName": {
+      "type": "string"
+    },
+    "organization": {
+      "type": "string"
+    },
+    "phone": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / inputs / properties / email

Added value: +{
+  "additionalProperties": false,
+  "description": "Email draft (type=email), encoded as mailto:<address>?subject=&body=.",
+  "properties": {
+    "address": {
+      "type": "string"
+    },
+    "body": {
+      "type": "string"
+    },
+    "subject": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / inputs / properties / sms

Added value: +{
+  "additionalProperties": false,
+  "description": "SMS draft (type=sms), encoded as sms:<phone>?body=<message>.",
+  "properties": {
+    "message": {
+      "type": "string"
+    },
+    "phone": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / inputs / properties / text

Added value: +{
+  "description": "Raw text, used when type=text.",
+  "type": "string"
+}

addedInput schema / properties / inputs / properties / url

Added value: +{
+  "description": "URL, used when type=url.",
+  "type": "string"
+}

addedInput schema / properties / inputs / properties / wifi / additionalProperties
```
Added value: +false
```

addedInput schema / properties / inputs / properties / wifi / description

Added value: +"WiFi join data (type=wifi), encoded as WIFI:T:<security>;S:<ssid>;P:<password>;;."

addedInput schema / properties / inputs / properties / wifi / properties / password / description
```
Added value: +"Network password."
```
addedInput schema / properties / inputs / properties / wifi / properties / security / description
```
Added value: +"Auth type, e.g. WPA, WEP, or nopass."
```
addedInput schema / properties / inputs / properties / wifi / properties / ssid / description
```
Added value: +"Network name."
```
removedInput schema / properties / inputs / properties / wifi / required
```
Removed value: -[
-  "ssid",
-  "password",
-  "security"
-]
```
removedInput schema / properties / inputs / required
```
Removed value: -[
-  "wifi"
-]
```

addedInput schema / properties / qrType

Added value: +{
+  "description": "Alias for type; used when type is absent.",
+  "enum": [
+    "text",
+    "url",
+    "wifi",
+    "contact",
+    "sms",
+    "email"
+  ],
+  "type": "string"
+}

addedInput schema / properties / settings / additionalProperties
```
Added value: +false
```

addedInput schema / properties / settings / description

Added value: +"Rendering options applied to the serviceUrl."

addedInput schema / properties / settings / properties / backgroundColor / default
```
Added value: +"#ffffff"
```
addedInput schema / properties / settings / properties / backgroundColor / description
```
Added value: +"Background color as #rrggbb; invalid input falls back to #ffffff."
```
addedInput schema / properties / settings / properties / backgroundColor / pattern
```
Added value: +"^#[0-9a-fA-F]{6}$"
```
addedInput schema / properties / settings / properties / errorCorrection / default
```
Added value: +"M"
```

addedInput schema / properties / settings / properties / errorCorrection / description

Added value: +"Error-correction level: L 7%, M 15%, Q 25%, H 30% damage tolerance."

addedInput schema / properties / settings / properties / errorCorrection / enum
```
Added value: +[
+  "L",
+  "M",
+  "Q",
+  "H"
+]
```
addedInput schema / properties / settings / properties / foregroundColor / default
```
Added value: +"#000000"
```
addedInput schema / properties / settings / properties / foregroundColor / description
```
Added value: +"Module color as #rrggbb; invalid input falls back to #000000."
```
addedInput schema / properties / settings / properties / foregroundColor / pattern
```
Added value: +"^#[0-9a-fA-F]{6}$"
```
addedInput schema / properties / settings / properties / size / default
```
Added value: +300
```
addedInput schema / properties / settings / properties / size / description
```
Added value: +"Square pixel size; other values fall back to 300."
```
addedInput schema / properties / settings / properties / size / enum
```
Added value: +[
+  200,
+  300,
+  400,
+  500
+]
```

removedInput schema / properties / settings / required

Removed value: -[
-  "size",
-  "errorCorrection",
-  "foregroundColor",
-  "backgroundColor"
-]

addedInput schema / properties / type / default
```
Added value: +"text"
```

addedInput schema / properties / type / description

Added value: +"Payload type to encode. Unknown values fall back to text. (qrType is accepted as an alias.)"

addedInput schema / properties / type / enum

Added value: +[
+  "text",
+  "url",
+  "wifi",
+  "contact",
+  "sms",
+  "email"
+]

changedInput schema / required

Previous value: -[
-  "type",
-  "inputs",
-  "settings"
-]New value: +[
+  "type"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "properties": {
+        "content": {
+          "description": "The encoded string that the QR will contain.",
+          "type": "string"
+        },
+        "contentLength": {
+          "description": "Character length of content.",
+          "type": "integer"
+        },
+        "errorCorrectionDisplay": {
+          "description": "Verbose error-correction label with damage tolerance.",
+          "type": "string"
+        },
+        "inputLabel": {
+          "description": "UI label for the input, e.g. \"Website URL\".",
+          "type": "string"
+        },
+        "serviceUrl": {
+          "description": "api.qrserver.com URL that renders the QR PNG; empty string when content is blank.",
+          "type": "string"
+        },
+        "settings": {
+          "description": "Normalized settings actually applied.",
+          "properties": {
+            "backgroundColor": {
+              "description": "Applied background color (#rrggbb).",
+              "type": "string"
+            },
+            "errorCorrection": {
+              "description": "Applied level (L, M, Q, H).",
+              "type": "string"
+            },
+            "foregroundColor": {
+              "description": "Applied module color (#rrggbb).",
+              "type": "string"
+            },
+            "size": {
+              "description": "Square pixel size.",
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        },
+        "sizeDisplay": {
+          "description": "Size as \"<n>x<n> pixels\".",
+          "type": "string"
+        },
+        "type": {
+          "description": "Resolved payload type (text, url, wifi, contact, sms, email).",
+          "type": "string"
+        },
+        "typeDisplay": {
+          "description": "Human label for the type, e.g. \"Contact Card (vCard)\".",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "success": {
+      "description": "True when the payload was built.",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0May 31, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds context beyond annotations: non-destructive, deterministic, rate-limited (20 req/min anonymous), and explains the serviceUrl is a third-party renderer fetched separately. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and front-loaded with purpose, but is somewhat verbose. Every sentence adds value; could be slightly more concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given complexity (nested objects, 4 parameters, output schema exists), the description covers the API flow, rate limits, third-party dependency, and return fields. Fully adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with detailed descriptions for all properties. The description summarizes but adds little beyond the schema, e.g., mentioning encoding formats like 'WIFI:T:...'. Meets baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it builds QR code payloads from six input types and returns a render URL. It distinguishes itself from siblings by naming them explicitly (osint_qr_code_scanner, osint_barcode_generator, security_totp_qr_generator).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use this tool ('prepare QR content') and when to use alternatives (decode, barcode, TOTP). Provides clear context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server