_ registry / mcp streamable-http · checked 1h ago

lorg-check

https://api.lorglabs.com

Registry code: c52f4bd0d2db94e3

api record

Lorg Check answers one question before money moves: is this token a trap, or is this address one you shouldn't pay? Call check_token before buying or swapping into a token. Call check_address before sending funds to a wallet or contract. Read `action` in the result: proceed, limit_exposure (go in small, or ask the user first) or do_not_proceed. `summary` is one sentence you can show the user. A result marked as an error is not a verdict: treat the address as not verified and do not trade on it. An allow is not a guarantee: it means nothing that should stop the trade was found at the moment of…

endpoint
https://api.lorglabs.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is lorg-check live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is lorg-check free to use?
No — it asks for a key or a login before it will serve.
What tools does lorg-check have?
2 tools: check_address, check_token.
Is lorg-check safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
355ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 2 tools
1 auth-required 1 never probed 1 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • check_token auth-required 1h ago

    Is this token safe to buy? Runs a simulated buy and sell-back through the token's real pool, and reads what its owner can still do, who can withdraw the pool's liquidity, its holders, its deployer and whether it imitates a known token. Returns a signed verdict (allow, caution or block), an action (proceed, limit_exposure, do_not_proceed), a one-sentence summary and the reasons, most serious first. Use it before every swap into a token on Base or Ethereum. Takes about a second.

    mcp-tool

    {
      "type": "object",
      "required": [
        "chain",
        "address"
      ],
      "properties": {
        "chain": {
          "enum": [
            "base",
            "ethereum"
          ],
          "type": "string",
          "description": "The chain the address is on."
        },
        "address": {
          "type": "string",
          "pattern": "^0x[0-9a-fA-F]{40}$",
          "description": "The token's contract address: 0x followed by 40 hex characters."
        },
        "amount_usd": {
          "type": "number",
          "maximum": 1000000000,
          "minimum": 0.01,
          "description": "Optional: the size of the trade you intend, in US dollars. The check then also buys and sells that amount in simulation, and says so (EXIT_LIQUIDITY_INSUFFICIENT, action limit_exposure) when the pool is too small for it or the token limits the size of a sale. Give it whenever you know the size."
        }
      },
      "additionalProperties": false
    }
    arguments 29 lines
  • check_address unknown never probed

    Is this address safe to send funds to? Checks sanctions lists, known scam labels, wallets that forward everything they receive to a thief (EIP-7702 sweepers), look-alike addresses made for address poisoning, and where the wallet's first funds came from. Returns a signed verdict (allow, caution or block), an action, a one-sentence summary and the reasons. Use it before a payment or transfer on Base or Ethereum. For a token you intend to buy, use check_token instead. Takes about a fifth of a second.

    mcp-tool

    {
      "type": "object",
      "required": [
        "chain",
        "address"
      ],
      "properties": {
        "chain": {
          "enum": [
            "base",
            "ethereum"
          ],
          "type": "string",
          "description": "The chain the address is on."
        },
        "address": {
          "type": "string",
          "pattern": "^0x[0-9a-fA-F]{40}$",
          "description": "The wallet or contract address: 0x followed by 40 hex characters."
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c52f4bd0d2db94e3.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c52f4bd0d2db94e3/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c52f4bd0d2db94e3/badge.svg)](https://brick.blue/agent/c52f4bd0d2db94e3?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.