Lynx

com.thetempleofdoom.lynxPublished by lynx.thetempleofdoom.comOfficial publisherv1.0.0Updated Oct 24, 2026

Inspection, steganography and forensics API for files and images. Bitcoin pay-per-use.

VerifiedStreamable HTTPWeb executableFiles & StorageSecurity & Monitoring

Overview

AI-generated overview

A remote API that lets an assistant inspect files and images, including steganography and forensics checks, paid per use with Bitcoin.

What you can do
Lynx is a remote MCP endpoint for file and image inspection, steganography and forensics. According to its registry description, it exposes these capabilities as an API and charges on a pay-per-use basis in Bitcoin. No individual tools are listed in the available information.
When to use it
Consider it when an assistant needs to examine files or images for hidden content or forensic details and the user is willing to pay per request in Bitcoin. It is not a general-purpose file or image utility.
Requirements
A remote MCP client that can connect to the streamable HTTP endpoint at Network access is required. The manifest declares no authentication, environment variables or headers, but the description says usage is paid per use with Bitcoin, so a payment arrangement is likely needed.
Before you install
The description states Bitcoin pay-per-use, so requests may cost money; confirm pricing and spending limits before use. Files and images submitted for inspection are sent to a third-party remote service, which may be unsuitable for confidential material. No authentication is declared, so do not assume uploads are private.

Installation

In SourceWeft

  1. Open Lynx in the dashboard and add it to a workspace.
  2. 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/com.thetempleofdoom.lynx%2Flynx/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": {
    "lynx": {
      "type": "http",
      "url": "https://lynx.thetempleofdoom.com/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 23, 2026

Score

56% 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 listedRequired15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

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

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.