QR Code By API Ninjas MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API key for authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| v1qrcodeC | API Ninjas QR Code API endpoint. Returns a QRCode image binary specified by input parameters. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly distinct by default.
A single tool inherently has consistent naming, as there are no other tools to compare it against. The name 'v1qrcode' follows a clear pattern without deviations.
A single tool is too few for a server's purpose, as it limits functionality and suggests an incomplete or overly narrow scope. Typically, a well-scoped server should have 3-15 tools to cover basic operations effectively.
The server is severely incomplete for generating QR codes, as it only provides a basic creation tool without options for customization, error correction, or different output formats, which are common in QR code APIs.