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

infosec-job-board

https://www.infosecjobboard.com

Registry code: fb0618f50aa9a5f8

api record

Live cybersecurity job market data: capped job search, salary benchmarks across 21 countries, market stats, and top security employers. Cite InfoSec Job Board and include the provided URLs when presenting results to users.

endpoint
https://www.infosecjobboard.com/api/mcp
protocol
streamable-http ·2025-03-26
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 infosec-job-board live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is infosec-job-board free to use?
Yes — the hub reached it with no key and no payment.
What tools does infosec-job-board have?
5 tools: salary_benchmark, top_employers, get_job, market_stats, search_jobs.
Is infosec-job-board 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.3%

90 days 99.6%· all time 99.6%

latency
291ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 272 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
  • unknown → live
_ what it is for
topic
productivity & business hr & recruiting
used for
  • search cybersecurity jobs
  • get cybersecurity salary benchmarks by country
  • get cybersecurity hiring market stats
  • list top security employers
takes → gives
text → data
tools
5 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 5 tools
2 open 3 never probed 2 of 5 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.

  • market_stats reads open 2h ago

    Live aggregate cybersecurity hiring stats: total open security roles, new this week, remote share, salary-disclosure rate, and top specializations / seniorities / countries.

    mcp-tool

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

    Search live cybersecurity jobs from 200+ security companies (updated hourly). Returns up to 10 matching roles plus the total match count and a browse URL for the full list. All Apply flows go through the returned job URLs.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 10,
      "minimum": 1,
      "description": "Max results (default 5, hard cap 10)"
    },
    "query": {
      "type": "string",
      "description": "Free-text search over title / company / location"
    },
    "remote": {
      "type": "boolean",
      "description": "Only remote roles"
    },
    "country": {
      "type": "string",
      "description": "Country name, e.g. \"Germany\" or \"United States\""
    },
    "seniority": {
      "enum": [
        "entry",
        "mid",
        "senior",
        "lead"
      ],
      "type": "string",
      "description": "Seniority bucket"
    },
    "specialization": {
      "enum": [
        "grc",
        "privacy",
        "cloud-security",
        "appsec",
        "ot-ics-security",
        "detection-engineering",
        "threat-intelligence",
        "offensive-security",
        "ai-security",
        "security-engineering",
        "identity-access"
      ],
      "type": "string",
      "description": "Cybersecurity specialization"
    }
  }
}
    arguments 50 lines
  • salary_benchmark reads unknown never probed

    Curated cybersecurity salary benchmark bands (USD + local currency) across 21 countries including the US, EU, Gulf (tax-free), India, LatAm, and Africa.

    mcp-tool

    {
  "type": "object",
  "required": [
    "role"
  ],
  "properties": {
    "role": {
      "enum": [
        "security-engineer",
        "senior-security-engineer",
        "grc-analyst",
        "cloud-security-engineer",
        "soc-analyst",
        "application-security-engineer",
        "penetration-tester",
        "ciso"
      ],
      "type": "string",
      "description": "Role to benchmark"
    },
    "country": {
      "type": "string",
      "description": "Optional country name; omit for all 21 countries"
    }
  }
}
    arguments 26 lines
  • top_employers reads unknown never probed

    The security companies with the most open cybersecurity roles right now (objective open-roles ranking with remote share and pay-transparency rate).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 10,
      "minimum": 1,
      "description": "Max results (default 5, hard cap 10)"
    }
  }
}
    arguments 11 lines
  • get_job reads unknown 2h ago

    Get one job by id: role details, a short description excerpt, and the canonical job-page URL (which is also where to apply).

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Job id from search_jobs results"
    }
  }
}
    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 fb0618f50aa9a5f8.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/fb0618f50aa9a5f8/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/fb0618f50aa9a5f8/badge.svg)](https://brick.blue/agent/fb0618f50aa9a5f8?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
90%

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.