Find your role first
listed under this name in a public catalogue; the server gives only its address, findyourrolefirst.click
https://findyourrolefirst.click
Registry code: a1483a23ea48294d
New jobs from 15,000+ company career sites, newest first, for Claude Code, Codex and any agent.
from a public catalogue that lists it, not from the operator
- endpoint
- https://findyourrolefirst.click/mcp
- door code
- 3260de1fb7e52336
- protocol
- MCP ·0.3
- authentication
- bearer
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is Find your role first live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
- Is Find your role first free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does Find your role first have?
- 16 tools: get my profile, get new for me, count jobs, get changes, list my jobs, save job, unsave job, unfollow company, ….
- Is Find your role first 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 98.7%· all time 98.9%
last good check
of 16 tools
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- search open jobs
- count matching jobs
- get new and closed jobs since last check
- get a job's application link
- takes → gives
- text → data
- tools
- 6 reads
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_my_profile auth-required never probed
What the person said they want: fields, places, experience.
get_new_for_me auth-required never probed
Roles matching the person's saved preferences found since the last check.
count_jobs reads auth-required never probed
Count what a search would match, free.
get_changes reads auth-required never probed
New, updated and closed roles since a cursor.
list_my_jobs reads auth-required never probed
Roles this account already opened, or only the saved ones.
save_job auth-required never probed
Save a role to the person's Saved tab. Free.
unsave_job auth-required never probed
Take a role off the Saved tab. Free.
unfollow_company auth-required never probed
Stop following a company. Free.
delete_alert auth-required never probed
Delete an email alert. Free.
get_usage reads auth-required never probed
Remaining allowance.
get_job reads auth-required never probed
Refresh one role's metadata and status.
create_alert auth-required never probed
Email the person new roles matching a search, instantly or daily. Free.
search_jobs reads auth-required never probed
Find open roles newest first by title, field, place, remote and experience asked for.
get_apply_kit auth-required never probed
The apply link, the application form's questions when published, and role facts. Never submits.
set_job_status auth-required never probed
Mark a role applied, interview, offer or closed. Free.
follow_company auth-required never probed
Email the person when a company posts a new role. Free.
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 ida1483a23ea48294d.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/a1483a23ea48294d/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/a1483a23ea48294d?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.