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

northline-chainkit

https://northline-chainkit.northline-c86.workers.dev

Registry code: ddfc96a1a51a7108

api record

Onchain facts for Base and Arc: address preflight/risk profile, USDC payment verification, transaction explainer, gas/fees, USDC balances. Paid tools cost $0.001-$0.005 USDC on Base via x402; call chainkit_catalog (free) for prices.

endpoint
https://northline-chainkit.northline-c86.workers.dev/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 northline-chainkit live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is northline-chainkit free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does northline-chainkit have?
6 tools: address_profile, verify_usdc_payment, usdc_balances, chainkit_catalog, network_status, explain_transaction.
Is northline-chainkit 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
117ms

last good check

priced tools
2

of 6 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, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 2 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
4

distinct

settlements
14

last 2026-10-30

received on chain
0.523 USDC

concentrated, shared-payto

_ what it can do 6 tools
2 paid1 open 3 never probed 3 of 6 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.

  • network_status 0.001 USDC paid 1h ago

    Live block height, gas price and fee estimates (transfer, ERC-20 transfer, contract call) for Base or Arc. On Arc fees are quoted directly in USDC. Costs $0.001 USDC on Base per call via x402 (unpaid calls return the x402 PaymentRequired; any x402 MCP client pays automatically).

    mcp-tool

    {
      "type": "object",
      "properties": {
        "chain": {
          "enum": [
            "base",
            "arc"
          ],
          "type": "string",
          "default": "base"
        }
      }
    }
    arguments 13 lines
  • explain_transaction 0.004 USDC paid 1h ago

    Explain a Base or Arc transaction in plain JSON: status, confirmations, fee, method selector, created contract, and every ERC-20 transfer decoded with symbol and decimals. Costs $0.004 USDC on Base per call via x402 (unpaid calls return the x402 PaymentRequired; any x402 MCP client pays automatically).

    mcp-tool

    {
      "type": "object",
      "required": [
        "tx"
      ],
      "properties": {
        "tx": {
          "type": "string",
          "pattern": "^0x[0-9a-fA-F]{64}$"
        },
        "chain": {
          "enum": [
            "base",
            "arc"
          ],
          "type": "string",
          "default": "base"
        }
      }
    }
    arguments 20 lines
  • chainkit_catalog open 1h ago

    Free. Lists every ChainKit tool with its price, required inputs and an example, plus how x402 payment works. Call this first.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • address_profile unknown never probed

    Preflight any address on Base or Arc before paying or approving it: EOA vs contract vs EIP-7702-delegated wallet, EIP-1967 proxy implementation/admin, owner(), Safe multisig threshold, ERC-20 metadata, USDC + native balance, Sourcify verification, and risk flags. Costs $0.005 USDC on Base per call via x402 (unpaid calls return the x402 PaymentRequired; any x402 MCP client pays automatically).

    mcp-tool

    {
      "type": "object",
      "required": [
        "address"
      ],
      "properties": {
        "chain": {
          "enum": [
            "base",
            "arc"
          ],
          "type": "string",
          "default": "base"
        },
        "address": {
          "type": "string",
          "pattern": "^0x[0-9a-fA-F]{40}$"
        }
      }
    }
    arguments 20 lines
  • verify_usdc_payment unknown never probed

    Verify that a transaction paid at least N USDC to an address on Base or Arc (handles Arc native-USDC logs). Returns verified true/false, confirmations, matching transfers and reasons. Use it to confirm a customer paid before delivering. Costs $0.003 USDC on Base per call via x402 (unpaid calls return the x402 PaymentRequired; any x402 MCP client pays automatically).

    mcp-tool

    {
      "type": "object",
      "required": [
        "tx",
        "to"
      ],
      "properties": {
        "to": {
          "type": "string",
          "pattern": "^0x[0-9a-fA-F]{40}$"
        },
        "tx": {
          "type": "string",
          "pattern": "^0x[0-9a-fA-F]{64}$"
        },
        "from": {
          "type": "string",
          "pattern": "^0x[0-9a-fA-F]{40}$"
        },
        "chain": {
          "enum": [
            "base",
            "arc"
          ],
          "type": "string",
          "default": "base"
        },
        "minAmount": {
          "type": "string"
        },
        "minConfirmations": {
          "type": "string"
        }
      }
    }
    arguments 35 lines
  • usdc_balances unknown never probed

    USDC and native balance of one address on both Base and Arc in a single call. Costs $0.002 USDC on Base per call via x402 (unpaid calls return the x402 PaymentRequired; any x402 MCP client pays automatically).

    mcp-tool

    {
      "type": "object",
      "required": [
        "address"
      ],
      "properties": {
        "address": {
          "type": "string",
          "pattern": "^0x[0-9a-fA-F]{40}$"
        }
      }
    }
    arguments 12 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 ddfc96a1a51a7108.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ddfc96a1a51a7108/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/ddfc96a1a51a7108/badge.svg)](https://brick.blue/agent/ddfc96a1a51a7108?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
100%

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.