Server data from the Official MCP Registry
Mint, resolve, audit, and rotate scope-limited expiring access links (qURLs) for AI agents.
Mint, resolve, audit, and rotate scope-limited expiring access links (qURLs) for AI agents.
The qURL MCP server is well-structured with proper authentication, secure credential handling, and appropriate permission scoping. The code demonstrates strong security practices including lazy SDK initialization to defer credential validation, comprehensive input validation via Zod schemas, and clean separation of concerns. Minor code quality observations around broad error handling do not materially affect security. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.
5 files analyzed · 7 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: QURL_API_KEY
Environment variable: QURL_API_URL
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-layervai-qurl-mcp": {
"env": {
"QURL_API_KEY": "your-qurl-api-key-here",
"QURL_API_URL": "your-qurl-api-url-here"
},
"args": [
"-y",
"@layervai/qurl-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
⚠️ Renamed from
@layerv/qurl-mcpin v0.4.0. The old package is deprecated and will not receive further updates. If you're using@layerv/qurl-mcp@0.3.x, swap the scope in your MCP client config — same binary, same API key, no other changes.
MCP server for qURL™ secure link management.
Quantum URL (qURL) · The internet has a hidden layer. This is how you enter.
qURL MCP Server is a Model Context Protocol server that lets AI agents (Claude, GPT, Cursor, etc.) create, resolve, list, and manage qURL secure links natively. It connects to the qURL API over stdio transport, so any MCP-compatible client can use it without custom integration code.
Add the server to your MCP client configuration (Claude Desktop, Claude Code, etc.):
{
"mcpServers": {
"qurl": {
"command": "npx",
"args": ["@layervai/qurl-mcp"],
"env": { "QURL_API_KEY": "lv_live_xxx" }
}
}
}
Replace lv_live_xxx with your actual API key. The key must have the appropriate scopes for the tools you intend to use (see below).
| Tool | Description | Required Scope |
|---|---|---|
create_qurl | Create a secure, policy-bound link to a protected resource | qurl:write |
resolve_qurl | Resolve an access token to get the target URL and grant network access | qurl:resolve |
list_qurls | List active qURLs with optional pagination | qurl:read |
get_qurl | Get details of a specific qURL by resource ID | qurl:read |
delete_qurl | Revoke a qURL, immediately invalidating the link | qurl:write |
extend_qurl | Extend the expiration of an active qURL (alias for update_qurl) | qurl:write |
update_qurl | Update expiration, tags, or description on an active qURL | qurl:write |
mint_link | Mint a new access link for an existing protected resource | qurl:write |
batch_create_qurls | Create multiple qURLs in a single call | qurl:write |
revoke_qurl_token | Revoke one qURL token without revoking sibling tokens on the resource | qurl:write |
update_qurl_token | Update expiry, label, policy, or session limits on one qURL token | qurl:write |
list_qurl_sessions | List active access sessions for a qURL resource | qurl:read |
terminate_qurl_sessions | Terminate one or all active sessions for a qURL resource | qurl:write |
| URI | Name | Description |
|---|---|---|
qurl://links | Active qURL Links | List of all active qURL links |
qurl://usage | qURL Usage & Quota | Current quota and usage information |
| Environment Variable | Required | Description | Default |
|---|---|---|---|
QURL_API_KEY | Conditional (see description) | API key with appropriate scopes (qurl:read, qurl:write, qurl:resolve). The server boots without it so MCP introspection (tools/list, resources/list, prompts/list) works for directory probes — required only on the first tool call or resource read, where invocations surface a typed missing_api_key error until the key is set. | -- |
QURL_API_URL | No | qURL API base URL | https://api.layerv.ai |
A multi-stage Dockerfile is included for container-based deployment:
docker build -t qurl-mcp .
docker run -i -e QURL_API_KEY=lv_live_xxx qurl-mcp
The image runs as the non-root node user, ships only production dependencies, and uses tini as PID 1 for clean signal handling.
If a tool call returns missing_api_key despite QURL_API_KEY looking set, check stderr for the boot-time warning — some MCP hosts hide stderr, and the warning is the fastest way to spot a whitespace-only or unset value:
docker logs <container> # if running detached
docker run -i -e QURL_API_KEY=lv_live_xxx qurl-mcp 2>&1 # interactive
npm install
npm run build
npm test
npm run lint
Additional commands:
npm run dev # Watch mode (rebuild on changes)
npm run format # Format source with Prettier
npm run format:check # Check formatting without modifying files
MIT -- LayerV AI
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.