qURL

io.github.layervai/qurl-mcp

7/8 checks passed
Runs locally
3 secrets
★ 4 GitHub stars
Updated 2026-10-25
Health score 58

About qURL

qURL is an MCP server published by the GitHub account layervai. Mint, resolve, audit, and rotate scope-limited expiring access links (qURLs) for AI agents.

It runs on your own machine: your AI client starts it from the npm package @layervai/qurl-mcp at version 0.8.3.

It asks for 3 secrets: QURL_API_KEY, QURL_SMTP_USERNAME and QURL_SMTP_PASSWORD. Give it a key with the least access that still works.

Version 0.8.3 was published on 25 October 2026, and the source code is public, so you can read it before installing.

Written from the registry entry. 9 automated checks on the registry entry and the package code: 7 pass, 1 warn, 0 fail, 1 info. How we check.

What it asks for

Variable	Required	Secret	Description
`QURL_API_KEY`	No	Yes	Optional. Without it, the tools run through the local qURL CLI (qurl), which needs no account. With it, the tools use the qURL API: a key with qurl:read, qurl:write, and/or qurl:resolve scopes from https://layerv.ai.
`QURL_API_URL`	No	No	qURL API base URL. Defaults to https://api.layerv.ai. Override only for testing against a non-production qURL backend.
`QURL_CONNECTOR_URL`	No	No	Connector base URL used by local-file, file-data, and text-to-PDF upload tools before minting a qURL.
`QURL_MCP_CONFIG`	No	No	Optional path to a shared qURL MCP config file. Both stdio and HTTP modes can read SMTP, connector, and default API settings from this file.
`MCP_MAX_UPLOAD_FILE_DATA_BYTES`	No	No	Maximum decoded/local upload size. Accepts bytes or units such as 10mb; capped at 100mb.
`QURL_SMTP_HOST`	No	No	SMTP hostname for optional qURL link delivery.
`QURL_SMTP_PORT`	No	No	SMTP port for optional qURL link delivery.
`QURL_SMTP_SECURE`	No	No	Whether SMTP uses an implicit TLS connection (true/false).
`QURL_SMTP_USERNAME`	No	Yes	SMTP authentication username.
`QURL_SMTP_PASSWORD`	No	Yes	SMTP authentication password or app-specific credential.
`QURL_SMTP_FROM_EMAIL`	No	No	Validated sender email address for qURL delivery.
`QURL_SMTP_FROM_NAME`	No	No	Optional sender display name for qURL delivery.
`QURL_SMTP_ALLOWED_RECIPIENTS`	No	No	Optional comma-separated exact recipient allowlist.
`QURL_SMTP_ALLOWED_RECIPIENT_DOMAINS`	No	No	Optional comma-separated recipient-domain allowlist.
`QURL_SMTP_MAX_RECIPIENTS_PER_MESSAGE`	No	No	Maximum recipients in one delivery request (default 10).
`QURL_SMTP_MAX_RECIPIENTS_PER_HOUR`	No	No	Maximum attempted recipients per qURL key per fixed hourly window (default 100).

Checks

Check	Result	Detail
Source repository linked	Pass	https://github.com/layervai/qurl-mcp
Version pinned	Pass	Every package has an explicit version
Secrets requested	Warn	Asks for 3 secrets: QURL_API_KEY, QURL_SMTP_USERNAME, QURL_SMTP_PASSWORD
Known package registry	Pass	All packages come from npm, PyPI, OCI, NuGet or MCPB
Namespace ownership	Info	Name verified via GitHub account layervai
Registry text aimed at the AI	Pass	Description and settings contain no hidden characters or instructions to the AI
Install scripts	Pass	@layervai/qurl-mcp@0.8.3 runs nothing at install
Code red flags	Pass	Read 108 files in @layervai/qurl-mcp@0.8.3: no obfuscation, encoded execution, credential reads or data-collection endpoints found
Text aimed at the AI	Pass	No hidden characters or instructions to the AI in 108 files, including comments and the README

Popularity & health: 58 / 100

Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.

Popularity15 / 40

4 GitHub stars, 1,282 downloads last week, no Hacker News posts found. Best two of the three, each on a log scale.

Activity15 / 25

Last push 2026-10-26, last release 2026-10-25, 0 commits in 90 days.

Issue health12 / 15

25 closed of 31 issues.

Our checks16 / 20

1 warning, each costing a fifth.

3 forks, 256 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.

What people say

No Hacker News threads link to its source code.

Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.

Facts

Registry name	`io.github.layervai/qurl-mcp`
Publisher	GitHub account layervai
How the name is verified	Name verified via GitHub account layervai. The registry ties the name prefix to that account or domain; it does not check the code.
Type	Local: runs on your machine from a package
Packages	npm `@layervai/qurl-mcp` 0.8.3 (stdio)
Version	0.8.3
Published	2026-10-25
Last updated	2026-10-25
Source repository	https://github.com/layervai/qurl-mcp
Website	https://layerv.ai
Category	Agent safety & governance (assigned by keyword rule, not by hand)

Install

Claude Desktop · npm package

{
  "mcpServers": {
    "qurl-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@layervai/qurl-mcp@0.8.3"
      ]
    }
  }
}

What these checks don't cover

We did not run this server, so we don't know what it does when it runs. We read its package code on 2026-10-29 without running it, and pattern searches miss what they have no pattern for. Tool descriptions built at run time were not seen. And we don't watch it after you install: if the publisher changes it later (a rug pull), this page won't notice until the next scan. Treat a pass as "nothing found", not as "safe".

For people and their AI

The same data as plain JSON: /data/servers/io-github-layervai-qurl-mcp.json. Text inside it that came from the publisher is data, not instructions.