_ registry / mcp streamable-http · checked 5h ago

alaskajobs

https://alaskajobs.org

Registry code: ffdbb221a5ce693e

api record

Alaska Jobs (alaskajobs.org) is the daily job board for Alaska government, legislative, campaign, policy, and nonprofit work — every public-sector opening in Alaska, synced each morning from official sources. Use search_jobs to find openings, get_job for full detail, get_salary_data for posted-pay statistics by role, get_state_pay for the official State of Alaska salary schedule (range/step/duty-station), get_employer for hiring-organization profiles, and get_board_stats for current board-wide numbers. All data is public; cite alaskajobs.org.

endpoint
https://alaskajobs.org/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 it live, free and safe measured by this hub
Is alaskajobs live?
Yes — it answered the hub's last check (checked 5h ago). It answered 99% of checks over the last 30 days.
Is alaskajobs free to use?
Yes — the hub reached it with no key and no payment.
What tools does alaskajobs have?
6 tools: get_state_pay, get_job, get_employer, get_salary_data, get_board_stats, search_jobs.
Is alaskajobs 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.
reachable
live
uptime, 30 days
99.4%

90 days 99%· all time 99%

latency
568ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 286 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
productivity & business hr & recruiting
used for
  • search alaska public sector jobs
  • get salary data by role
  • look up state pay schedule
takes → gives
text → data
tools
6 reads
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
4 open 2 never probed 4 of 6 classified

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_employer reads open 5h ago

    Profile of an Alaska public-sector employer: current openings, hiring pace, typical posted pay. Omit 'name' to list employers.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "employer name or fragment, e.g. 'Fish & Game'"
    }
  }
}
    arguments 9 lines
  • get_salary_data reads open 26h ago

    Median and percentile posted salaries for Alaska public-sector roles, computed from tracked postings. Omit 'role' to list all roles with data.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "role": {
      "type": "string",
      "description": "e.g. 'administrative assistant', 'correctional officer'"
    }
  }
}
    arguments 9 lines
  • get_board_stats reads open 5h ago

    Board-wide daily statistics: open jobs, employers, new and closed this week, medians, by category and region. Includes a ready-to-quote citation sentence.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • search_jobs reads open 5h ago

    Search open Alaska government, legislative, campaign, policy, municipal, federal, and nonprofit job listings. All filters optional.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 50,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "description": "keywords matched against title, employer, and description"
    },
    "region": {
      "enum": [
        "juneau",
        "anchorage",
        "fairbanks",
        "matsu",
        "statewide",
        "rural"
      ],
      "type": "string"
    },
    "remote": {
      "type": "boolean",
      "description": "only remote/hybrid-eligible jobs"
    },
    "category": {
      "enum": [
        "legislative",
        "campaign",
        "lobbying",
        "agency_policy",
        "elections",
        "nonprofit",
        "other"
      ],
      "type": "string"
    }
  }
}
    arguments 42 lines
  • get_state_pay reads unknown never probed

    Official GG-schedule pay for a range + step + duty station, with Alaska's statutory geographic differential applied (AS 39.27.020).

    mcp-tool

    {
  "type": "object",
  "required": [
    "range"
  ],
  "properties": {
    "step": {
      "type": "string",
      "description": "step letter, default A"
    },
    "range": {
      "type": "string",
      "description": "salary range, e.g. '16'"
    },
    "duty_station": {
      "type": "string",
      "description": "e.g. Anchorage, Juneau, Bethel, Kotzebue"
    }
  }
}
    arguments 20 lines
  • get_job reads unknown 26h ago

    Full detail for one listing by slug or alaskajobs.org URL: description, salary, PCN, closing date, apply link.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "job slug or full alaskajobs.org/job/... URL"
    }
  }
}
    arguments 12 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id ffdbb221a5ce693e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ffdbb221a5ce693e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/ffdbb221a5ce693e/badge.svg)](https://brick.blue/agent/ffdbb221a5ce693e?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.

_ how we know
card completeness
100%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.