Linkguard

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026

Forward URL safety scans to the hosted PreClick remote MCP endpoint.

VerifiedSTDIODesktop only

Overview

Linkguard's local MCP server; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

  1. Open Linkguard in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

linkguard

linkguard is a local stdio front end for a hosted URL safety scanner. Before an agent follows a link, linkguard can ask the hosted service to examine the URL — synchronously for an immediate verdict, or asynchronously when a scan may take a while — and, when you say why you are visiting, whether the page actually matches that intent.

linkguard does not scan anything itself. Each tool call is forwarded as a JSON-RPC tools/call POST to the hosted PreClick remote MCP endpoint at https://preclick.ai/mcp, and the upstream answer is returned as-is in substance. Both plain JSON answers and text/event-stream (SSE) answers are understood. Scanning quality, availability, and rate limits are the hosted service's.

PRECLICK_API_KEY is optional. When it is set, it is sent as the X-API-Key header documented for the hosted endpoint; when it is absent, no such header is sent and the keyless trial tier applies. LINKGUARD_ENDPOINT overrides the endpoint URL when set.

Intent text is capped at 248 characters by the upstream service; linkguard enforces that limit locally before sending anything.

Install

bash
npx @reneturcios/linkguard scan https://example.comdocker run -i ghcr.io/cloudcorprecords/linkguard

CLI

bash
linkguard scan https://example.comlinkguard scan-intent https://example.com --intent "pay an invoice"linkguard async-scan https://example.comlinkguard async-scan-intent https://example.com --intent "read the docs"linkguard status <task_id>linkguard result <task_id>linkguard --version

The async commands return a task_id immediately. Poll it with status, then fetch the finished scan with result.

Exit codes: 0 success, 1 upstream or validation error, 2 usage error.

MCP server

bash
npx -y @reneturcios/linkguard mcp
json
{  "mcpServers": {    "linkguard": {      "command": "npx",      "args": ["-y", "@reneturcios/linkguard", "mcp"],      "env": { "PRECLICK_API_KEY": "your-key-if-you-have-one" }    }  }}

The env block is optional.

Tools

ToolInputWhat it returns
url_scanner_scanurl (string, required)The upstream scan verdict for the URL, synchronously.
url_scanner_scan_with_intenturl (string, required), intent (string, optional, max 248 chars)The upstream verdict judged against the stated intent.
url_scanner_async_scanurl (string, required)A task_id for the submitted scan, immediately.
url_scanner_async_scan_with_intenturl (string, required), intent (string, optional, max 248 chars)A task_id for the submitted intent-aware scan.
url_scanner_async_task_statustask_id (string, required)The current status of the asynchronous task.
url_scanner_async_task_resulttask_id (string, required)The finished scan result, or the task status while it runs.

Upstream failures — HTTP errors, JSON-RPC errors, unreachable hosts — are reported as tool errors with the underlying message.

Development

bash
npm installnpm run buildnpm testnpm run dev

Tests run entirely on fake-fetch fixtures, including plain-JSON and SSE upstream bodies; no network is used and no live call to the hosted endpoint is made.

License

MIT — see LICENSE.

Source: README.md at commit 1d50fc4

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestNov 3, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts