scout
Registry code: 28d82ced1e78dbe7
Scout lists newly noticed early-stage startups on X, refreshed daily. Use it for questions about brand-new companies (what appeared this week, new AI or robotics startups, who is gaining followers fastest), not for established companies, market data or investment advice.
Start with search_companies: it lists and filters companies (by search text, sector, when they were found, newest or fastest growing), 100 per page with a cursor. Use get_company when you already have a company's X handle and want its full details. Use get_discovery_stats for how many companies were found per day. Sector slugs…
- endpoint
- https://scout.emre.computer/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 scout live?
- Yes — it answered the hub's last check (checked 13h ago). It answered 100% of checks over the last 30 days.
- Is scout free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does scout have?
- 4 tools: get_company, get_discovery_stats, list_sectors, search_companies.
- Is scout 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.
90 days 100%· all time 100%
last good check
of 4 tools
- unknown → live
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.
through this hub
successful
what callers paid
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.
get_discovery_stats open 13h ago
Count how many companies Scout found on each of the last 7 days, and the total listed, optionally within one sector. Use for trend questions such as "how many new AI startups this week"; it returns numbers, not companies.
{ "type": "object", "properties": { "sector": { "enum": [ "ai", "quantum", "hardware", "robotics", "biotech_health", "space_defense", "climate_energy", "crypto", "fintech", "dev_tools_infra", "consumer", "other" ], "type": "string", "description": "Only companies in this sector." } }, "additionalProperties": false }arguments 24 lineslist_sectors open 13h ago
Return the sector slugs and display names that the sector filter of search_companies and get_discovery_stats accepts. Call it only when you need to map a user's wording to a slug.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linessearch_companies open 13h ago
List or search newly noticed startups. Filter by name/website text, sector, and when Scout found them (today, 3 days, 7 days, all); sort by newest or by 7-day follower growth. Returns up to 100 companies per call plus nextCursor for the next page. Use this first for any "find/list new startups" question.
{ "type": "object", "properties": { "sort": { "enum": [ "newest", "growth" ], "type": "string", "description": "newest (default) or growth (most X followers gained over 7 days)." }, "query": { "type": "string", "maxLength": 60, "description": "Search company names and websites (e.g. \"robot\"). Omit to list all." }, "range": { "enum": [ "24h", "3d", "7d", "all" ], "type": "string", "description": "When Scout found them: 24h (today), 3d, 7d, or all (default)." }, "cursor": { "type": "string", "description": "nextCursor from a previous page; omit for the first page." }, "sector": { "enum": [ "ai", "quantum", "hardware", "robotics", "biotech_health", "space_defense", "climate_energy", "crypto", "fintech", "dev_tools_infra", "consumer", "other" ], "type": "string", "description": "Only companies in this sector." } }, "additionalProperties": false }arguments 51 linesget_company unknown never probed
Get one company's full Scout profile by its X handle: bio, website and its description, followers and 7-day growth, latest X post, and latest funding round. Use when you already know the handle; returns an error result if Scout has not listed it.
{ "type": "object", "required": [ "handle" ], "properties": { "handle": { "type": "string", "pattern": "^@?[A-Za-z0-9_]{1,15}$", "description": "The company's X handle, with or without @ (e.g. \"openai\")." } }, "additionalProperties": false }arguments 14 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id28d82ced1e78dbe7.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/28d82ced1e78dbe7/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/28d82ced1e78dbe7?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.