qURL
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QURL_API_KEY | Yes | API key with appropriate scopes (qurl:read, qurl:write, qurl:resolve) | |
| QURL_API_URL | No | qURL API base URL | https://api.layerv.ai |
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": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_qurlB | Create a qURL - a secure, policy-bound link to a protected resource. The returned qurl_link is ephemeral (shown once) and should be shared immediately. |
| resolve_qurlA | Resolve a qURL access token to get the target URL and open firewall access. After resolution, the target URL is accessible from your IP for the duration specified in access_grant.expires_in seconds. |
| list_qurlsC | List qURLs with optional filtering by status, date ranges, and search query. |
| get_qurlA | Get details of a qURL resource and its access tokens. Accepts either a resource ID (r_ prefix) or a qURL display ID (q_ prefix). |
| delete_qurlA | Revoke/delete a qURL. This immediately invalidates the link. |
| extend_qurlA | Extend the expiration of an active qURL. Accepts a resource ID (r_) or qURL display ID (q_). Shorthand for update_qurl with only extend_by — use update_qurl for richer updates (tags, description, expiration). |
| update_qurlA | Update a qURL - extend expiration, set an absolute expiry, update tags, or change the description. Accepts either a resource ID (r_ prefix) or qURL display ID (q_ prefix). Do not provide both extend_by and expires_at. At least one update field is required. |
| mint_linkA | Mint a new access link for an existing qURL resource. Accepts either a resource ID (r_ prefix) or qURL display ID (q_ prefix). Use this to generate additional access links without creating a new resource. Do not provide both expires_in and expires_at. |
| batch_create_qurlsA | Create multiple qURLs in a single request. Returns per-item results including any errors for partial failures. The response sets isError=true when one or more items fail so agents can branch on partial failure without parsing the JSON. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| secure-a-service | Guide through creating a qURL to protect a service with appropriate security policies (expiration, session limits, IP/geo allowlists, AI-agent blocking). |
| audit-links | Review all active qURLs and identify expiring links, token counts, missing metadata, or potential issues. |
| rotate-access | Rotate a qURL by revoking the existing link and creating a fresh one with the same target. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Active qURL Links | |
| qURL Usage & Quota |
TDQS
Scored across 9 tools
Most tools have distinct purposes, but extend_qurl and update_qurl overlap in functionality. Extend_qurl is a subset of update_qurl, which could cause confusion, though the descriptions guide the agent to use update_qurl for richer updates.
Most tools follow a verb_qurl pattern (create_qurl, delete_qurl, get_qurl, list_qurls, update_qurl, extend_qurl), but mint_link uses a different noun ('link') and batch_create_qurls uses plural 'qurls', breaking consistency.
Nine tools cover the full lifecycle of qURL resources without being excessive. Each tool serves a clear purpose, from creation to resolution, including batch operations and specific updates.
The tool set covers CRUD plus batch creation, link minting, and resolution. Missing are tools for individually managing access tokens or disabling a qURL temporarily, but core workflows are well-supported.