Finder Jobs
Registry code: be84b26272ddbf95
Search live job vacancies on Finder country sites (by, kz, kg, de, fr, be, ch, se, id). Always show users the returned finder.work url so they can open and apply.
- endpoint
- https://mcp.finder.work/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 Finder Jobs live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is Finder Jobs free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does Finder Jobs have?
- 4 tools: search_vacancies, get_vacancy, salary_stats, list_countries.
- Is Finder Jobs 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.
list_countries open 1h ago
List countries supported by Finder with their ISO code and site url.
{ "type": "object", "title": "list_countriesArguments", "properties": {} }arguments 5 linessearch_vacancies unknown never probed
Search active job vacancies on Finder. country: ISO code (by, kz, kg, de, fr, be, ch, se, id). query: job title / keywords in any language (e.g. 'бухгалтер', 'python developer'). city: city name as written locally (e.g. 'Минск', 'Алматы', 'Berlin'). Returns up to `limit` (≤20) newest matches with links to finder.work.
{ "type": "object", "title": "search_vacanciesArguments", "required": [ "country" ], "properties": { "city": { "type": "string", "title": "City", "default": "" }, "limit": { "type": "integer", "title": "Limit", "default": 10 }, "query": { "type": "string", "title": "Query", "default": "" }, "country": { "type": "string", "title": "Country" } } }arguments 28 linesget_vacancy unknown 1h ago
Get details of one vacancy by its Finder id (from search_vacancies): title, employer, city, salary, description (up to 1500 chars) and the finder.work page url where the user can apply.
{ "type": "object", "title": "get_vacancyArguments", "required": [ "id" ], "properties": { "id": { "type": "integer", "title": "Id" } } }arguments 13 linessalary_stats unknown 1h ago
Salary statistics (25th/50th/75th percentile, sample size) from active vacancies on Finder. country: ISO code; profession: name in local language (e.g. 'Бухгалтер', 'Programmierer'); empty = all jobs; city optional. Returns the matching Finder salary page url when available.
{ "type": "object", "title": "salary_statsArguments", "required": [ "country" ], "properties": { "city": { "type": "string", "title": "City", "default": "" }, "country": { "type": "string", "title": "Country" }, "profession": { "type": "string", "title": "Profession", "default": "" } } }arguments 23 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 idbe84b26272ddbf95.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/be84b26272ddbf95/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/be84b26272ddbf95?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.