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

usedby

https://www.usedby.ai

Registry code: c479881ef30923bf

api record

usedby tracks which companies publicly use which AI and software tools, each line backed by a public source (vendor customer page, case study, press release, job post).

Proof levels, strongest first: CONFIRMED (case study, named testimonial, press release), OBSERVED (the vendor shows the customer: logo wall, customers page), SIGNAL (a job post shows the company's employees use the tool: the weakest proof).

endpoint
https://www.usedby.ai/mcp
protocol
http-sse ·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 usedby live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is usedby free to use?
Yes — the hub reached it with no key and no payment.
What tools does usedby have?
5 tools: search_tools, who_uses, company_stack, compare, recent_changes.
Is usedby 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
332ms

last good check

priced tools
0

of 5 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 5 tools
1 open 4 never probed 1 of 5 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.

  • recent_changes open 1h ago

    Companies newly listed as customers by tool vendors in the last N days, optionally for one tool. Departures are not published.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "days": {
          "type": "integer",
          "maximum": 365,
          "minimum": 1,
          "description": "Window in days (default 30, max 365)."
        },
        "tool": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Only this tool (slug or name)."
        },
        "limit": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1,
          "description": "Rows to list (default 25, max 100). The usedby page has the full list."
        }
      }
    }
    arguments 24 lines
  • search_tools unknown never probed

    Find AI and software tools tracked on usedby by name or category, with how many companies publicly use each.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1,
          "description": "Rows to list (default 25, max 100). The usedby page has the full list."
        },
        "query": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "Tool name or category, e.g. 'cursor', 'coding', 'customer support'."
        }
      }
    }
    arguments 21 lines
  • who_uses unknown never probed

    Companies that publicly use a tool, strongest proof first, each with its proof level (CONFIRMED, OBSERVED, or SIGNAL: a job post, the weakest proof), source page and first public proof date.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "tool"
      ],
      "properties": {
        "tool": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Tool slug or name, e.g. 'cursor', 'GitHub Copilot', 'harvey'."
        },
        "limit": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1,
          "description": "Rows to list (default 25, max 100). The usedby page has the full list."
        }
      }
    }
    arguments 21 lines
  • company_stack unknown 1h ago

    Tools a company publicly uses according to usedby, strongest proof first, each with its proof level (job-post signals last) and source page.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "company"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1,
          "description": "Rows to list (default 25, max 100). The usedby page has the full list."
        },
        "company": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Company slug, name or website, e.g. 'stripe', 'Klarna', 'notion.so'."
        }
      }
    }
    arguments 21 lines
  • compare unknown 1h ago

    Two tools side by side: public customers with their proof mix, top industries, companies confirmed or observed on both, and vendor facts with their sources.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "a",
        "b"
      ],
      "properties": {
        "a": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "First tool slug or name."
        },
        "b": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Second tool slug or name."
        },
        "limit": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1,
          "description": "Rows to list (default 25, max 100). The usedby page has the full list."
        }
      }
    }
    arguments 28 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 c479881ef30923bf.

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

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.