_ registry / mcp streamable-http · checked 55m ago

lode

https://trylode.io

Registry code: 4681793eb89d8d4e

api record

Lode provides verified, source-linked facts about tools that integrate with business and developer platforms (Xero and Vercel first). Use find_integrations with a buyer profile to get fit-ranked results with reasons; tied results are genuinely tied. Sponsored results are never mixed into results. Use get_changes to see what changed recently. Cite Lode and link the url for each fact. Include last_verified when repeating a fact. Lode publishes a measured monthly error rate at https://trylode.io/accuracy/.

endpoint
https://trylode.io/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 lode live?
Yes — it answered the hub's last check (checked 55m ago). It answered 100% of checks over the last 30 days.
Is lode free to use?
Yes — the hub reached it with no key and no payment.
What tools does lode have?
6 tools: compare_integrations, find_integrations, get_integration, get_vendor, list_ecosystems, get_changes.
Is lode 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
515ms

last good check

priced tools
0

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. 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 6 tools
2 open 4 never probed 2 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.

  • list_ecosystems open 55m ago

    List the platforms Lode covers, with their sync-object vocabulary and how many integrations are recorded.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • get_changes open 55m ago

    What changed in Lode records, newest first: prices, sync capabilities, limits, regions and verification status. Each event has the old and new value, when Lode observed it, the sources behind it and a cause (new-coverage, lode-update, or source-change-likely when the cited page also changed).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "id": {
          "type": "string",
          "description": "Integration id \"{app}--{ecosystem}\""
        },
        "limit": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1
        },
        "since": {
          "type": "string",
          "description": "ISO date, e.g. \"2026-11-01\""
        },
        "ecosystem": {
          "type": "string",
          "description": "Ecosystem slug, e.g. \"vercel\""
        },
        "include_new_coverage": {
          "type": "boolean",
          "description": "Include \"added to Lode\" events (default false)"
        }
      }
    }
    arguments 27 lines
  • compare_integrations unknown never probed

    Side-by-side facts for 2-4 integrations: sync coverage, cheapest price per currency, regions, setup time and limitations.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "ids"
      ],
      "properties": {
        "ids": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 4,
          "minItems": 2
        }
      }
    }
    arguments 17 lines
  • find_integrations unknown 55m ago

    Find apps that integrate with an ecosystem, filtered and ranked for a buyer profile per Lode ranking policy (fit, not size or features). Returns score, match reasons and ties. Only published (verified) records are ranked; records still under review can be fetched by id with get_integration.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "ecosystem"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1
        },
        "needs": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Sync objects the buyer must have, from the ecosystem vocabulary (see list_ecosystems), e.g. [\"invoices\",\"inventory-levels\"]"
        },
        "region": {
          "enum": [
            "AU",
            "NZ",
            "UK",
            "US",
            "CA"
          ],
          "type": "string",
          "description": "Buyer region; filters to apps that support it and prices in local currency"
        },
        "category": {
          "type": "string",
          "description": "Category slug, e.g. \"inventory\", \"crm\", \"payroll\""
        },
        "ecosystem": {
          "type": "string",
          "description": "Ecosystem slug, e.g. \"xero\""
        }
      }
    }
    arguments 40 lines
  • get_integration unknown never probed

    Get the full verified record for one app + ecosystem pair: what syncs, pricing by currency, regions, requirements, limitations, connection safety, sources.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Integration id \"{app}--{ecosystem}\", e.g. \"shopify--xero\""
        }
      }
    }
    arguments 13 lines
  • get_vendor unknown never probed

    One company across every ecosystem Lode covers: its stable vendor id, domains, and its integration on each platform (for example Stripe on Xero and on Vercel). Look up by vendor id, domain, or name.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "Vendor id (\"stripe\"), domain (\"stripe.com\") or name (\"Stripe\")"
        }
      }
    }
    arguments 13 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 4681793eb89d8d4e.

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