Lorg Check

com.lorglabsPublished by lorglabs.comOfficial publisherv1.1.0Updated Oct 24, 2026

Is this token a trap? Is this address safe to pay? Signed verdicts on Base and Ethereum.

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server that gives assistants signed verdicts on whether a token is a trap or an address is safe to pay on Base and Ethereum.

What you can do
  • Check whether a token is a trap or scam before interacting with it
  • Check whether an address is safe to pay on Base and Ethereum
  • Return signed verdicts that can be verified rather than taken on trust
When to use it
Useful when an assistant helps with on-chain activity on Base or Ethereum and needs a quick risk check on a token or a recipient address before acting.
Requirements
A remote streamable HTTP endpoint at api.lorglabs.com; OAuth authentication is required. No environment variables or headers are declared.
Before you install
Verdicts are risk signals, not guarantees; a signed result does not make a token or address safe. The service receives the token and address identifiers you submit, and OAuth grants it access tied to your account.

Installation

In SourceWeft

  1. Open Lorg Check in the dashboard and add it to a workspace.
  2. Connect the required 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/com.lorglabs%2Florg-check/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "lorg-check": {
      "type": "http",
      "url": "https://api.lorglabs.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.0LatestOct 15, 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 listed15 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.