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

echoloc

https://api.echoloc.ai

Registry code: 011eb654bcab30e0

api record

echoloc company intelligence: technographics with direction of change (adopting / replacing / evaluating), hiring signals, and firmographics for 760,000+ companies, built from public job posts. Without an API key you get an anonymous preview (5 tool calls/day, trimmed results). For full data send an echoloc API key in the 'X-API-Key' header. Free beta key (100 requests/month, instant): sign up at https://echoloc.ai/auth?mode=signup&returnTo=%2Fapp%2Fapi and copy the key from https://echoloc.ai/app/api. Production keys: [email protected]. Details: https://echoloc.ai/for-agents/

endpoint
https://api.echoloc.ai/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 echoloc live?
Yes — it answered the hub's last check (checked 12m ago). It answered 100% of checks over the last 30 days.
Is echoloc free to use?
Yes — the hub reached it with no key and no payment.
What tools does echoloc have?
3 tools: search_companies_by_technologies, get_company_by_domain, list_technologies.
Is echoloc 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
99.6%

90 days 99.3%· all time 99.3%

latency
102ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 570 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
productivity & business crm & sales
used for
  • find companies using given technologies
  • get a company profile by domain
  • list tracked technologies
takes → gives
text → data
tools
3 reads
_ 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 3 tools
1 open 2 never probed 1 of 3 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_technologies reads open 20h ago

    Catalog of all technologies in the dataset with per-technology company counts. sort='count' (most used first) or 'name'.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "page": {
      "type": "integer",
      "default": 1,
      "minimum": 1
    },
    "sort": {
      "enum": [
        "count",
        "name"
      ],
      "type": "string",
      "default": "count"
    },
    "page_size": {
      "type": "integer",
      "default": 50,
      "maximum": 500,
      "minimum": 1
    }
  }
}
    arguments 24 lines
  • search_companies_by_technologies reads unknown 20h ago

    Find companies using the given technologies, ranked by usage. Names are case-insensitive ('snowflake' == 'Snowflake'); 10,000+ technologies are tracked (use list_technologies to explore). match='any' needs at least one technology, 'all' needs every one.

    mcp-tool

    {
  "type": "object",
  "required": [
    "technologies"
  ],
  "properties": {
    "page": {
      "type": "integer",
      "default": 1,
      "minimum": 1
    },
    "match": {
      "enum": [
        "any",
        "all"
      ],
      "type": "string",
      "default": "any"
    },
    "page_size": {
      "type": "integer",
      "default": 20,
      "maximum": 100,
      "minimum": 1
    },
    "technologies": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 1,
      "description": "Technology names, e.g. [\"Snowflake\", \"dbt\"]"
    }
  }
}
    arguments 35 lines
  • get_company_by_domain reads unknown 20h ago

    Resolve a company domain (e.g. 'walgreens.com') to its full profile: firmographics, hiring stats, and the technology stack with adoption context (using / adopting / replacing / evaluating). Matches the primary domain first, then known aliases (regional TLDs, legacy brands, subdomains).

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "Company domain — primary or any known alias"
    }
  }
}
    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 011eb654bcab30e0.

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

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.