Link rot scan and notarized archive — Atom

org.aimldsPublished by aimlds.orgv0.1.0Updated Nov 15, 2026

Link rot scan and notarized archive, delivered per API call as an atom service on Conduit Atoms.

The publisher's own server: scan.mx Email Diagnostics

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Remote Conduit Atoms service that lets an assistant run a link rot scan and produce a notarized archive of the results, per API call.

What you can do
  • Scan links for rot, checking whether referenced URLs still resolve
  • Produce a notarized archive of the scan results
  • Run these operations per API call as an atom service on Conduit Atoms
  • No individual tools are documented in the supplied listing, so exact operations are not confirmed
When to use it
When you need to check a set of links for rot and keep a notarized record of the findings, and prefer a hosted service over running your own crawler.
Requirements
A remote streamable HTTP endpoint at atoms.pipavia.com. A Conduit Atoms gateway key sent in the Authorization header as a Bearer token; the key must carry this atom's scope (link_rot_scan_and_notarized_archive). Sign-up on the provider's site is needed to obtain a key.
Before you install
A gateway key is required and is sent as a bearer credential; one key works across atoms, so a leaked key may reach more than this service. The service is billed or metered per API call according to the provider's model. Scanned URLs and results are sent to a third-party hosted service.

Installation

In SourceWeft

  1. Open Link rot scan and notarized archive — Atom in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/org.aimlds%2Fatom-link-rot-scan-and-notarized-archive/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "link-rot-scan-and-notarized-archive-atom": {
      "type": "http",
      "url": "https://atoms.pipavia.com/mcp/link-rot-scan-and-notarized-archive",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.0LatestNov 15, 2026

Score

60% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Scan integrations