_ registry / mcp streamable-http · checked 49m ago

hiring-change-intelligence

https://s-hiring.pixharvest.com

Registry code: 48e440885467a910

api record

Track public job boards: free snapshot, paid hiring-growth intel via x402 USDC.

from a public catalogue that lists it, not from the operator

endpoint
https://s-hiring.pixharvest.com/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 hiring-change-intelligence live?
Partly — its last checks failed now and then (checked 49m ago). It answered 0% of checks over the last 30 days.
Is hiring-change-intelligence free to use?
Not measured yet.
What tools does hiring-change-intelligence have?
5 tools: hiring_intel_report, hiring_batch_scan, hiring_changes, hiring_landscape, hiring_snapshot.
Is hiring-change-intelligence 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
degraded
uptime, 30 days
0%

90 days 0%· all time 0%

latency
—

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → degraded· fetch failed
_ 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
5 never probed 0 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.

  • hiring_intel_report unknown never probed

    PAID ($0.50 USDC on Base via x402). Highest-value workforce-intelligence report: hiring growth rate, which teams are scaling, geographic footprint, headcount estimate and executive takeaways for investors/recruiters/sales. Use to gauge if a company is expanding, for account research, competitive talent analysis, sourcing priorities.

    mcp-tool

    {
  "type": "object",
  "required": [
    "company"
  ],
  "properties": {
    "company": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • hiring_batch_scan unknown never probed

    PAID ($0.03 USDC per company via x402, max 50). Track hiring across a whole portfolio or target-account list in one call; per-company counts of new openings and closures. Use for recruitment agency monitoring, VC portfolio talent tracking, sales prospecting signals, sector hiring trends.

    mcp-tool

    {
  "type": "object",
  "required": [
    "companies"
  ],
  "properties": {
    "companies": {
      "type": "array",
      "items": {
        "type": "string"
      }
    }
  }
}
    arguments 14 lines
  • hiring_changes unknown never probed

    PAID ($0.05 USDC on Base via x402). Hiring change detection vs history: newly opened roles, roles removed/closed (layoff or hiring freeze signal), team and location changes. Use for "did X just start/stop hiring", new job postings, recruiting trends, expansion or downsizing alerts.

    mcp-tool

    {
  "type": "object",
  "required": [
    "company"
  ],
  "properties": {
    "company": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • hiring_landscape unknown never probed

    PAID ($5 USDC on Base via x402, up to 10 companies). Strategic hiring landscape: ranks an anchor company against peers by hiring volume and growth, shows which competitor is scaling fastest, team/geography shifts and talent-war signals. Use for competitive intelligence, market mapping, employer benchmarking.

    mcp-tool

    {
  "type": "object",
  "required": [
    "companies"
  ],
  "properties": {
    "anchor": {
      "type": "string"
    },
    "companies": {
      "type": "array",
      "items": {
        "type": "string"
      }
    }
  }
}
    arguments 17 lines
  • hiring_snapshot unknown never probed

    FREE. Current job openings / who is hiring at one company right now, with teams (departments), locations, remote and employment type. Use for "what jobs is X hiring for", open roles, talent demand, headcount signals. Sources Greenhouse/Lever/Ashby. Target: gh:<h>, lever:<h>, ashby:<h> or bare company handle.

    mcp-tool

    {
  "type": "object",
  "required": [
    "company"
  ],
  "properties": {
    "company": {
      "type": "string"
    }
  }
}
    arguments 11 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 48e440885467a910.

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

_ also on pixharvest.com 3 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.