jobs-brief
Registry code: 1f54c18c450f243c
Jobs Brief is a free newsletter, sent every other Friday, of hand-picked senior cloud, platform, DevOps, SRE and AI-infrastructure roles that are remote across the EU or based in Poland, taken straight from company career pages. These tools show a past edition, as sent, and the hiring signals it carried; some roles may have closed. The current edition goes to subscribers: https://jobsbrief.eu/?utm_source=mcp. Each role links to the company's own posting; applications go to the company directly.
- endpoint
- https://jobsbrief.eu/api/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 jobs-brief live?
- Yes — it answered the hub's last check (checked 14h ago). It answered 100% of checks over the last 30 days.
- Is jobs-brief free to use?
- Not measured yet.
- What tools does jobs-brief have?
- 2 tools: sample_edition, signals.
- Is jobs-brief 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 2 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.
sample_edition unknown never probed
A hand-picked selection, a few dozen roles, not an exhaustive job search: senior cloud, platform, DevOps, SRE and AI-infrastructure roles from a past Jobs Brief edition, each read by an editor and kept only if it can be taken remotely from anywhere in the EU ('remote-eu') or from Poland ('poland'), at mid, senior or manager level. Each role has its location, contract form where stated, core stack, a one-line summary of the work, the published salary when there is one, and a link to the company's own posting. All filters are optional and combine.
{ "type": "object", "properties": { "level": { "enum": [ "mid", "senior", "manager" ], "type": "string", "description": "mid: evidenced mid-level IC roles. senior: senior, staff and principal IC roles. manager: engineering managers and heads of engineering." }, "query": { "type": "string", "description": "Free text matched against title, company and summary, e.g. 'observability' or 'GPU'." }, "stack": { "type": "string", "description": "A technology to match in the role's stack, e.g. kubernetes, terraform, aws, gcp." }, "section": { "enum": [ "remote-eu", "poland" ], "type": "string", "description": "remote-eu: remote roles open across the EU. poland: roles based in Poland." } }, "additionalProperties": false }arguments 31 linessignals unknown never probed
Which cloud, platform and AI-infrastructure teams in Europe and Poland are growing, and why: dated news items (funding rounds, acquisitions, new engineering hubs, new cloud regions), each with its source link, picked for a past Jobs Brief edition. News and context, not job postings or posting counts.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 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 id1f54c18c450f243c.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/1f54c18c450f243c/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/1f54c18c450f243c?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.