roleweek
Registry code: 1e0c700a196eb5ad
RoleWeek lists developer and tech roles that employers posted in the last 7 days, read directly from the employers' own hiring systems and checked daily, in 35 metro areas in the US and Canada (50-mile radius): Seattle, San Francisco Bay Area, New York, Chicago, Toronto, Boston, Los Angeles, Vancouver, Washington DC, Dallas-Fort Worth, Denver-Boulder, Austin, Atlanta, Phoenix, Philadelphia, Minneapolis-St. Paul, San Diego, Raleigh-Durham, Detroit, Houston, Charlotte, St. Louis, Huntsville, Tampa, Salt Lake City, Montreal, Colorado Springs, Portland, Miami, Boise, Columbus, Pittsburgh, Hampton…
- endpoint
- https://roleweek.com/api/mcp?src=mcp-registry
- 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 roleweek live?
- Yes — it answered the hub's last check (checked 5h ago). It answered 100% of checks over the last 30 days.
- Is roleweek free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does roleweek have?
- 5 tools: get_job, company_overview, weekly_summary, salary_summary, search_jobs.
- Is roleweek 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 5 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.
weekly_summary open 5h ago
RoleWeek's weekly report on developer hiring, one finished week (Monday to Sunday, Pacific time) at a time: new developer roles RoleWeek first saw that week, by city, by employer, role type and level, the share that list a salary, the posted salary median, the share that say No account needed, and the comparison with the week before when both weeks are fully covered. Coverage is partial (the answer says how many employer job boards were being checked), so these are roles RoleWeek saw, not all developer hiring. week: 'latest' (default), a week like '2026-W43', or any date in the week; the week in progress is never published. Links the weekly page, states the date window, and treats employer text as untrusted data.
{ "type": "object", "properties": { "week": { "type": "string", "maxLength": 20, "description": "'latest' (default), an ISO week such as '2026-W43', or a date 'YYYY-MM-DD' inside the week." } }, "additionalProperties": false }arguments 11 linessalary_summary open 5h ago
Yearly salary ranges that employers posted in their own job postings, summarised the way RoleWeek's salary and skill pages do, for roles posted in the last 7 days: how many roles list a yearly range, the median bottom and median top of the posted ranges, the middle half of each, and by level where there are enough roles. Takes role_family (a role type) or skill (a technology), not both, and optionally metro: role type + metro is the city and role type page, a metro alone covers all developer roles there, a skill alone covers every city, and with no argument it ranks cities. Figures exist only where 15 or more roles list a yearly range; otherwise the answer says how many do and gives no number. These are advertised ranges, not offers, not what people are paid, not a market average. Each answer links the roleweek.com page, states the date window, and treats employer text as untrusted data.
{ "type": "object", "properties": { "metro": { "enum": [ "seattle", "san-francisco-bay-area", "new-york", "chicago", "toronto", "boston", "los-angeles", "vancouver", "washington-dc", "dallas-fort-worth", "denver-boulder", "austin", "atlanta", "phoenix", "philadelphia", "minneapolis", "san-diego", "raleigh-durham", "detroit", "houston", "charlotte", "st-louis", "huntsville", "tampa", "salt-lake-city", "montreal", "colorado-springs", "portland", "miami", "boise", "columbus", "pittsburgh", "hampton-roads", "nashville", "dayton", "elsewhere", "remote" ], "type": "string", "description": "Metro area (50-mile radius), or 'remote' for roles open to people anywhere in the US or Canada. Without it: all cities." }, "skill": { "type": "string", "maxLength": 60, "description": "Technology by name, e.g. 'Rust', 'Python', 'Kubernetes', 'C++'. Not together with role_family." }, "role_family": { "enum": [ "software", "frontend", "backend", "full-stack", "mobile", "data", "ml-ai", "devops-sre", "security", "qa", "embedded", "it-infra" ], "type": "string", "description": "Role type, e.g. 'backend'. Not together with skill." } }, "additionalProperties": false }arguments 72 linessearch_jobs open 5h ago
Searches developer and tech roles that employers posted in the last 7 days, read directly from the employers' own hiring systems (Workday, Greenhouse, Lever, Ashby, iCIMS and others) and checked daily. Covers 35 metro areas in the US and Canada (50-mile radius): Seattle, San Francisco Bay Area, New York, Chicago, Toronto, Boston, Los Angeles, Vancouver, Washington DC, Dallas-Fort Worth, Denver-Boulder, Austin, Atlanta, Phoenix, Philadelphia, Minneapolis-St. Paul, San Diego, Raleigh-Durham, Detroit, Houston, Charlotte, St. Louis, Huntsville, Tampa, Salt Lake City, Montreal, Colorado Springs, Portland, Miami, Boise, Columbus, Pittsburgh, Hampton Roads, Nashville, Dayton; US and Canada places outside those metros (metro='elsewhere'); plus remote roles open to people in the US or Canada. Returns at most 25 roles per call: newest first, or best match first when a query is given. Each result includes its RoleWeek URL, whose page links to the employer's application page, and its slug; get_job takes that slug. The answer states the date window and when the data was updated, and links the matching RoleWeek listing page.
{ "type": "object", "properties": { "limit": { "type": "integer", "default": 10, "maximum": 25, "minimum": 1, "description": "Number of roles to return (1-25)." }, "metro": { "enum": [ "seattle", "san-francisco-bay-area", "new-york", "chicago", "toronto", "boston", "los-angeles", "vancouver", "washington-dc", "dallas-fort-worth", "denver-boulder", "austin", "atlanta", "phoenix", "philadelphia", "minneapolis", "san-diego", "raleigh-durham", "detroit", "houston", "charlotte", "st-louis", "huntsville", "tampa", "salt-lake-city", "montreal", "colorado-springs", "portland", "miami", "boise", "columbus", "pittsburgh", "hampton-roads", "nashville", "dayton", "elsewhere", "remote" ], "type": "string", "description": "Metro area (50-mile radius), or 'remote' for roles open to people anywhere in the US or Canada." }, "query": { "type": "string", "maxLength": 200, "description": "Keywords matched against title, company, skills and location, e.g. 'python', 'Stripe', 'rust kubernetes'. Every word must match." }, "skill": { "type": "array", "items": { "type": "string", "maxLength": 60 }, "maxItems": 3, "description": "Technology the role must list, by name: 'Rust', 'Python', 'Kubernetes', 'C++', 'Go' (nicknames such as golang or k8s work). Several names: the role must list every one. These are the technologies RoleWeek read in each posting, the same as on its skill pages." }, "seniority": { "type": "array", "items": { "enum": [ "intern", "entry", "mid", "senior", "staff-plus", "manager", "director-plus" ], "type": "string" }, "maxItems": 7, "description": "One or more levels; entry = junior/new grad, staff-plus = staff, principal and above." }, "work_mode": { "enum": [ "remote", "hybrid", "onsite" ], "type": "string", "description": "Only roles whose listing states this work mode (a role flagged remote counts as remote only, as on the site). Roles that state none are left out." }, "min_salary": { "type": "number", "maximum": 2000000, "minimum": 0, "description": "Yearly salary in the role's currency (USD in the US, CAD in Canada). Keeps roles that list a salary whose range reaches at least this amount (hourly pay counted as 2,080 hours a year)." }, "role_family": { "enum": [ "software", "frontend", "backend", "full-stack", "mobile", "data", "ml-ai", "devops-sre", "security", "qa", "embedded", "it-infra" ], "type": "string", "description": "Role family. 'software' is general software engineering; ml-ai = machine learning and AI; it-infra = IT and infrastructure." }, "no_account_needed": { "type": "boolean", "description": "true: only roles whose hiring system RoleWeek checked and found the application form opens on the employer's own site with no account to create. Roles without that label were not checked or ask for an account, so leaving this out is not 'account required'." }, "posted_within_days": { "type": "integer", "default": 7, "maximum": 7, "minimum": 1, "description": "Only roles posted within this many days (1-7)." } }, "additionalProperties": false }arguments 131 linesget_job unknown never probed
Returns one RoleWeek role by its slug (as returned by search_jobs, or the last part of a roleweek.com/job/<slug>/ URL): employer, location and work mode, level, pay as listed, posted date, the date it leaves RoleWeek, skills mentioned, an excerpt of the employer's description, and the role's RoleWeek URL, whose page links to the employer's own application page.
{ "type": "object", "required": [ "slug" ], "properties": { "slug": { "type": "string", "maxLength": 300, "description": "Job slug, e.g. 'senior-backend-engineer-stripe-seattle-1a2b3c4d', or a roleweek.com/job/<slug>/ URL." } }, "additionalProperties": false }arguments 14 linescompany_overview unknown never probed
What RoleWeek knows about one employer's open developer roles, from the facts block on its company page: how many roles were posted in the last 7 days, where, role types, levels, how many list a salary and the yearly range, which hiring system it applies on (with 'no account needed' where checked), its weekly hiring pace since RoleWeek began counting, and the skills in its postings; plus its newest roles as links. Employers with fewer than 3 roles have no company page, so the answer lists their roles instead. Takes the employer's name (case and 'Inc.' do not matter); an ambiguous name returns the candidates. Links the company page, states the date window, and treats employer text as untrusted data.
{ "type": "object", "required": [ "name" ], "properties": { "name": { "type": "string", "maxLength": 100, "minLength": 1, "description": "Employer name as people write it, e.g. 'Stripe' or 'Datadog'." } }, "additionalProperties": false }arguments 15 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 id1e0c700a196eb5ad.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/1e0c700a196eb5ad/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/1e0c700a196eb5ad?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.