Skip to content

H1R3: Australian job board for bots MCP server

dev.workers.h1r3.h1r3/h1r3h1r3.h1r3.workers.devstreamable-httpv0.9.0Scanned

Bot-first AU job board: live jobs, verified candidates apply via bots. First 100 employers free.

31 tools: 1 can delete or cancel things, 16 change things and 14 only read.

Tools: 1 delete, 0 irreversible, 16 write, 14 read.
  • Reads private data · 2
  • Reads text others write · 2
  • Can send data out · 2
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the H1R3: Australian job board for bots MCP server can do

The H1R3: Australian job board for bots MCP server is published by h1r3.h1r3.workers.dev, a domain the MCP Registry verified. It has 31 tools. It can delete or cancel things (1 tool: delete_job_alert) and create or change data (16 tools: create_job_alert, claim_listing, join_waitlist, post_job and 12 more). 14 tools only read.

2 tools read private data (search_jobs and get_verification_status); 2 tools bring in text other people can write (search_jobs and get_verification_status); 2 tools can send data out of your system (post_job and add_referee). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 15, 2026, version 0.9.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

31 tools

Deletes or cancels 1Claude Code: deny
  • delete_job_alertDelete one of your job alerts by id (seeker key).No findings

    Why it is in this group

    • The name "delete_job_alert" says "delete": a word for removing or ending something.
    Description, as the server wrote it
    Delete one of your job alerts by id (seeker key).
Changes things 16Claude Code: ask
  • add_certAdd a cert/licence (metadata + optional document SHA-256; no file upload).No findings

    Why it is in this group

    • The name "add_cert" says "add": a word for a change.
    Description, as the server wrote it
    Add a cert/licence (metadata + optional document SHA-256; no file upload).
  • add_refereeNominate a referee for a role; returns a unique single-use 30-day referee link to share.Can send data outNo findings

    Why it is in this group

    • The name "add_referee" says "add": a word for a change.

    What it can reach

    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    Nominate a referee for a role; returns a unique single-use 30-day referee link to share.
  • add_roleAdd an employment-history role with claimed tasks (taxonomy codes or {custom}).No findings

    Why it is in this group

    • The name "add_role" says "add": a word for a change.
    Description, as the server wrote it
    Add an employment-history role with claimed tasks (taxonomy codes or {custom}). Roles current or ended within 24 months are reference-eligible.
  • applyApply to a job (seeker key).No findings

    Why it is in this group

    • The name "apply" says "apply": a word for a change.
    Description, as the server wrote it
    Apply to a job (seeker key). Needs Basic verified (free: email + selfie check) or higher; jobs with min_verification=id ("ID verified only") need ID verified (A$3/yr).
  • claim_listingVerified (ABN) employer claims a sourced listing for their company; converts to an H1R3 job using 1 credit.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Verified (ABN) employer claims a sourced listing for their company; converts to an H1R3 job using 1 credit.
  • confirm_emailEmail a single-use 24h confirmation link to the account email (identity score +15).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Email a single-use 24h confirmation link to the account email (identity score +15).
  • create_job_alertSave a job search as an email alert (seeker key, Basic verified).No findings

    Why it is in this group

    • The name "create_job_alert" says "create": a word for a change.
    Description, as the server wrote it
    Save a job search as an email alert (seeker key, Basic verified). Sends NEW matching jobs daily or weekly to the account email, with an unsubscribe link. Filters as search_jobs: q, location, near, occupation, industry, work_type, min_pay (A$/yr, advertised pay), include_estimates. Max 5 alerts. sending_enabled in the reply says whether H1R3 email sending is switched on yet.
  • join_waitlistJoin the pre-launch waitlist.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Join the pre-launch waitlist.
  • post_jobPost a job (employer key, ABN-verified, 1 credit).Can send data outNo findings

    Why it is in this group

    • The name "post_job" says "post": a word for a change.

    What it can reach

    • outboundThe name "post_job" says "post": it sends or publishes something to other people.
    Description, as the server wrote it
    Post a job (employer key, ABN-verified, 1 credit). Returns Fair Work/moderation warnings. Set id_verified_only=true to accept ID verified applicants only (default: Basic verified or higher).
  • request_issuer_confirmationGet a single-use 30-day link for the cert issuer to confirm yes/no.No findings

    Why it is in this group

    • The name "request_issuer_confirmation" says "request": a word for a change.
    Description, as the server wrote it
    Get a single-use 30-day link for the cert issuer to confirm yes/no. Share it yourself (no email is sent).
  • set_privacySeeker privacy consent + visibility (private | applied | searchable).No findings

    Why it is in this group

    • The name "set_privacy" says "set": a word for a change.
    Description, as the server wrote it
    Seeker privacy consent + visibility (private | applied | searchable). Consent is required before adding certs/roles.
  • share_passportCreate a read-only passport link for any employer or bot (revokes previous).No findings

    Why it is in this group

    • The description's first verb is "create": a word for a change.
    Description, as the server wrote it
    Create a read-only passport link for any employer or bot (revokes previous).
  • start_testStart a timed skills test (seeker key).No findings

    Why it is in this group

    • The name "start_test" says "start": a word for a change.
    Description, as the server wrote it
    Start a timed skills test (seeker key). The human account owner must take it.
  • submit_testSubmit answers (0-based option indexes, in order).No findings

    Why it is in this group

    • The name "submit_test" says "submit": a word for a change.
    Description, as the server wrote it
    Submit answers (0-based option indexes, in order).
  • update_applicationShortlist or reject an application (employer key).No findings

    Why it is in this group

    • The name "update_application" says "update": a word for a change.
    Description, as the server wrote it
    Shortlist or reject an application (employer key).
  • update_profileCreate/update seeker profile.No findings

    Why it is in this group

    • The name "update_profile" says "update": a word for a change.
    Description, as the server wrote it
    Create/update seeker profile.
Only reads 14Show 14 read-only tools
  • find_adjacent_rolesH1R3 Cloud: given a role title or ANZSCO code (and optionally the candidate's verified tasks, free text or H1R3 task codes like admin.payroll), return the most adjacent occupations…No findings

    Why it is in this group

    • The name "find_adjacent_roles" says "find": a word for reading.
    Description, as the server wrote it
    H1R3 Cloud: given a role title or ANZSCO code (and optionally the candidate's verified tasks, free text or H1R3 task codes like admin.payroll), return the most adjacent occupations by shared skills (JSA Australian Skills Classification), with score, shared tasks (why), tasks the candidate has vs is missing, and live H1R3 job counts + sample jobs.
  • get_passportRead a shared passport by its token.No findings

    Why it is in this group

    • The name "get_passport" says "get": a word for reading.
    Description, as the server wrote it
    Read a shared passport by its token.
  • get_verificationYour portable verified passport: three 0-100 scores (identity, skills_certs, references) with level + breakdown, certs, roles, per-task matrix, learning & attitude.No findings

    Why it is in this group

    • The name "get_verification" says "get": a word for reading.
    Description, as the server wrote it
    Your portable verified passport: three 0-100 scores (identity, skills_certs, references) with level + breakdown, certs, roles, per-task matrix, learning & attitude.
  • get_verification_statusSeeker verification level and steps: Not verified, Basic verified (FREE: email confirmed + selfie check; a real person was at the camera, not an ID check), ID verified (A$3/yr: ID …Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_verification_status" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Seeker verification level and steps: Not verified, Basic verified (FREE: email confirmed + selfie check; a real person was at the camera, not an ID check), ID verified (A$3/yr: ID document check). Shows what is missing to apply.
  • list_applicationsList applicants for a job you own (employer key), with skill badges and verification_level (Basic verified | ID verified).No findings

    Why it is in this group

    • The name "list_applications" says "list": a word for reading.
    Description, as the server wrote it
    List applicants for a job you own (employer key), with skill badges and verification_level (Basic verified | ID verified).
  • list_bot_applicable_jobsThe canonical index of jobs a bot can apply to end-to-end (no human form/captcha).No findings

    Why it is in this group

    • The name "list_bot_applicable_jobs" says "list": a word for reading.
    Description, as the server wrote it
    The canonical index of jobs a bot can apply to end-to-end (no human form/captcha). Each job has an apply block {method, endpoint, required_fields, auth}.
  • list_cert_typesCert/licence types and how each is verified (register link, issuer confirmation, admin).No findings

    Why it is in this group

    • The name "list_cert_types" says "list": a word for reading.
    Description, as the server wrote it
    Cert/licence types and how each is verified (register link, issuer confirmation, admin).
  • list_job_alertsList your active job alerts (seeker key).No findings

    Why it is in this group

    • The name "list_job_alerts" says "list": a word for reading.
    Description, as the server wrote it
    List your active job alerts (seeker key).
  • list_skill_testsList available skills tests.No findings

    Why it is in this group

    • The name "list_skill_tests" says "list": a word for reading.
    Description, as the server wrote it
    List available skills tests.
  • list_task_taxonomyTask taxonomy (codes) for roles, with which certs/badges corroborate each task.No findings

    Why it is in this group

    • The name "list_task_taxonomy" says "list": a word for reading.
    Description, as the server wrote it
    Task taxonomy (codes) for roles, with which certs/badges corroborate each task.
  • match_profileFind live Australian jobs that match a resume or LinkedIn profile.No findings

    Why it is in this group

    • The description's first verb is "find": a word for reading.
    Description, as the server wrote it
    Find live Australian jobs that match a resume or LinkedIn profile. Send the resume text (text) OR derived signals (titles, occupations, skills). H1R3 extracts job titles, skills, location, seniority, likely pay band and work type with the ANZSCO dictionary (no AI), then ranks jobs by title/skill/occupation overlap, best first, broadening to related occupations when exact matches are few. Nothing is stored. Never send LinkedIn URLs: paste text or a Save-to-PDF export.
  • search_jobsSearch live Australian jobs; every result has pay_type verified (ABN-verified employer on H1R3) | advertised (stated in source ad) | unclear (a figure in the ad that looks wrong or…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "search_jobs" says "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "search" and "note": it reads notes.
    • untrusted-inputThe description's first sentence says "search" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Search live Australian jobs; every result has pay_type verified (ABN-verified employer on H1R3) | advertised (stated in source ad) | unclear (a figure in the ad that looks wrong or partial; not counted as advertised) | estimate (H1R3 estimate from ABS/JSA medians, not from the employer, with estimate_basis) | none, plus one normalised pay object {type,min,max,unit,text}; estimates are included by default (include_estimates=false for stated pay only); filter with pay=verified|advertised|estimate|any; sourced results carry job_url, posted_ago, and (for everyone, no key or verification) direct_to {apply_url, go_url, method, login_required, anti_bot_seen, notes} to send the candidate straight to the employer page, plus apply_mode (candidate_bot_ok / candidate_bot_grey / human_only). source=verified (paid, verified H1R3 employers) | sourced (public ATS listings; apply at original) | all (default; verified ranked first). Seek-style filters: industry (ANZSIC division), category/occupation (ANZSCO), location (state/region/remote), q (keywords), min_pay (annual A$) + include_estimates, page/per_page. Options: GET /api/v1/jobs/filters.
  • search_seekersSearch searchable seekers (ABN-verified employer key).No findings

    Why it is in this group

    • The name "search_seekers" says "search": a word for reading.
    Description, as the server wrote it
    Search searchable seekers (ABN-verified employer key). Each result has verification_level (Basic verified | ID verified). Filters: id_verified_only, min_level (basic|phone|id), verified_task (code), verified_cert (type), verified_skill (badge), min_score, min_identity, min_skills, min_references (0-100).

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

8 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 outbound tools breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__h1r3__add_referee",
      "mcp__h1r3__post_job"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:53 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
17
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 17 tools that change things (1 destructive, 16 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://h1r3.h1r3.workers.dev/mcp: tools/list returned 31 tools to an anonymous client, including delete_job_alert (destructive), create_job_alert (write), claim_listing (write), join_waitlist (write), post_job (write) and 12 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
  2. Tools4 added, 1 changed.+4 added~1 changedView diff

Install

Pinned to version 0.9.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http h1r3 https://h1r3.h1r3.workers.dev/mcp
claude mcp add --transport http h1r3 https://h1r3.h1r3.workers.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__h1r3__match_profile",
      "mcp__h1r3__list_job_alerts",
      "mcp__h1r3__search_jobs",
      "mcp__h1r3__list_bot_applicable_jobs",
      "mcp__h1r3__list_skill_tests",
      "mcp__h1r3__list_applications",
      "mcp__h1r3__search_seekers",
      "mcp__h1r3__list_task_taxonomy",
      "mcp__h1r3__list_cert_types",
      "mcp__h1r3__get_verification",
      "mcp__h1r3__get_verification_status",
      "mcp__h1r3__get_selfie_link",
      "mcp__h1r3__get_passport",
      "mcp__h1r3__find_adjacent_roles"
    ],
    "ask": [
      "mcp__h1r3__create_job_alert",
      "mcp__h1r3__claim_listing",
      "mcp__h1r3__join_waitlist",
      "mcp__h1r3__post_job",
      "mcp__h1r3__apply",
      "mcp__h1r3__update_application",
      "mcp__h1r3__update_profile",
      "mcp__h1r3__start_test",
      "mcp__h1r3__set_privacy",
      "mcp__h1r3__add_cert",
      "mcp__h1r3__request_issuer_confirmation",
      "mcp__h1r3__add_role",
      "mcp__h1r3__add_referee",
      "mcp__h1r3__share_passport",
      "mcp__h1r3__confirm_email",
      "mcp__h1r3__submit_test"
    ],
    "deny": [
      "mcp__h1r3__delete_job_alert"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as h1r3. Review it before you use it.

Capability tags behind 4 rules
  • mcp__h1r3__search_jobs private-data, untrusted-input
  • mcp__h1r3__post_job outbound
  • mcp__h1r3__add_referee outbound
  • mcp__h1r3__get_verification_status private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.workers.h1r3.h1r3/h1r3/verify?hash=f696c117f018eaca3281dd5c8a1920361aa380f7b1913dc6261658698b92d459" | jq -e '.changed == false'

Pinned hash f696c117f018, from Nov 15, 2026, 04:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.workers.h1r3.h1r3/h1r3/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.workers.h1r3.h1r3/h1r3
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.workers.h1r3.h1r3/h1r3.svg)](https://radar.anlyon.com/servers/dev.workers.h1r3.h1r3/h1r3)

Source: MCP Registry. Synced Oct 21, 2026, 18:12 UTC.

H1R3: Australian job board for bots MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the H1R3: Australian job board for bots MCP server safe?

No scan can promise that. What its definitions show: 31 tools, 17 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the H1R3: Australian job board for bots MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: delete_job_alert.

Can the H1R3: Australian job board for bots MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the H1R3: Australian job board for bots MCP server have?

31 tools: 1 destructive, 16 write, 14 read. delete_job_alert, create_job_alert, claim_listing, join_waitlist, post_job, apply, update_application, update_profile and 23 more.

Does the H1R3: Australian job board for bots MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the H1R3: Australian job board for bots MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): post_job and add_referee.

Has the H1R3: Australian job board for bots MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.