voxjobs-pt
Registry code: 70d877557e6990c7
Job listings in Portugal: search, salary statistics, comparables and companies.
from a public catalogue that lists it, not from the operator
- endpoint
- https://www.voxjobs.pt/api/mcp
- protocol
- streamable-http ·2024-11-05
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is voxjobs-pt live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
- Is voxjobs-pt free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does voxjobs-pt have?
- 6 tools: find_similar_jobs, get_job_detail, search_articles, search_jobs, search_companies, get_salary_stats.
- Is voxjobs-pt 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 99.2%· all time 99.2%
last good check
of 6 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- search jobs in portugal
- get salary statistics
- find similar jobs
- search employers
- takes → gives
- text → data
- tools
- 6 reads
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.
search_articles reads open 14h ago
Search editorial articles about the Portugal job market: job-hunting guides, salary analysis, career advice. Use this when the user asks how something works — the interview process, an ATS, a specific market or benefit — rather than asking for jobs.
{ "type": "object", "properties": { "limit": { "type": "number", "description": "Maximum number of results (default 5, max 10)." }, "query": { "type": "string", "description": "Free-text topic (optional). Empty → the most recent articles." } } }arguments 13 linessearch_jobs reads open 14h ago
Search active job listings in Portugal. Use this whenever the user wants to find a job — by title, skills, location, salary or schedule. Combines semantic ranking on the `query` (title/skills) with structural filters. Returns company, city, region, remote mode, seniority, salary and a citable URL, plus `total`: the exact number of listings matching the filters, which makes this useful for market-size questions. Listings are aggregated from ATSs, boards and public-sector portals and refreshed daily; each result carries `postedAt` and `lastSeenAt`. Salaries are published in EUR.
{ "type": "object", "properties": { "limit": { "type": "number", "description": "Maximum number of results (default 10, max 20)." }, "query": { "type": "string", "description": "Free-text semantic hint: job title, skills or field (e.g. 'data engineer', 'react developer', 'marketing manager'). Ranks results by meaning; combine with structural filters." }, "company": { "type": "string", "description": "Restrict to jobs from this employer (free-text name)." }, "escoCode": { "type": "string", "description": "ESCO occupation code (see europa.eu/esco). Optional and precise: when the caller has one, it filters much more sharply than free text." }, "location": { "type": "string", "description": "City or region within the market (e.g. Lisbon, Porto, Berlin). Do not include the country — it is set by the host." }, "schedule": { "enum": [ "FULL_TIME", "PART_TIME", "SHIFTS", "FLEXIBLE" ], "type": "string", "description": "Hours: FULL_TIME, PART_TIME, SHIFTS or FLEXIBLE." }, "seniority": { "enum": [ "INTERNSHIP", "JUNIOR", "MID", "SENIOR", "LEAD", "EXECUTIVE" ], "type": "string", "description": "Level of the role." }, "remoteMode": { "enum": [ "REMOTE", "HYBRID", "ONSITE" ], "type": "string", "description": "Work arrangement. REMOTE, HYBRID or ONSITE." }, "contractType": { "type": "string", "description": "Contract type in market-local vocabulary (e.g. permanent, CDI, B2B, umowa o pracę)." }, "salaryMinYearly": { "type": "number", "description": "Minimum gross yearly salary, in the market currency (EUR, GBP or PLN). Non-yearly periods are normalised." } } }arguments 64 linessearch_companies reads open 8h ago
Search employers with active listings in Portugal. Returns sector, headquarters, size band and the number of active jobs in this market. Use this when the user wants to explore who is hiring, or to restrict a subsequent search_jobs by employer.
{ "type": "object", "properties": { "name": { "type": "string", "description": "Full or partial employer name." }, "limit": { "type": "number", "description": "Maximum number of results (default 8, max 20)." }, "sector": { "type": "string", "description": "Sector (e.g. technology, healthcare, retail)." } } }arguments 17 linesget_salary_stats reads open 14h ago
Get salary statistics for a slice of the Portugal job market: how many listings match, how many publish a salary, the median annual salary, the p25–p75 range and a breakdown by seniority. Use this when the user asks what a role pays, or how two locations/seniorities compare — instead of listing individual jobs. Takes the same filters as search_jobs and describes exactly the set that tool would return. Reports percentiles rather than averages, because job salaries have a long right tail and a single executive listing moves an average. All figures normalised to the yearly period.
{ "type": "object", "properties": { "escoCode": { "type": "string", "description": "ESCO occupation code (see europa.eu/esco). Optional and precise: when the caller has one, it filters much more sharply than free text." }, "location": { "type": "string", "description": "City or region within the market (e.g. Lisbon, Porto, Berlin). Do not include the country — it is set by the host." }, "schedule": { "enum": [ "FULL_TIME", "PART_TIME", "SHIFTS", "FLEXIBLE" ], "type": "string", "description": "Hours: FULL_TIME, PART_TIME, SHIFTS or FLEXIBLE." }, "seniority": { "enum": [ "INTERNSHIP", "JUNIOR", "MID", "SENIOR", "LEAD", "EXECUTIVE" ], "type": "string", "description": "Level of the role." }, "remoteMode": { "enum": [ "REMOTE", "HYBRID", "ONSITE" ], "type": "string", "description": "Work arrangement. REMOTE, HYBRID or ONSITE." }, "contractType": { "type": "string", "description": "Contract type in market-local vocabulary (e.g. permanent, CDI, B2B, umowa o pracę)." } } }arguments 48 linesfind_similar_jobs reads unknown 8h ago
Given one job listing, find comparable ones: same occupation family and area, close seniority. Use this when the user likes a role but wants alternatives — 'find me similar jobs', 'the same but remote', 'what else is around'. Comparability is by role (ESCO code) and geography, not by text similarity: it answers 'is there anything else out there for someone with this profile', which a keyword search misses.
{ "type": "object", "required": [ "slug" ], "properties": { "slug": { "type": "string", "description": "Slug of the reference listing, as returned by search_jobs or get_job_detail." }, "limit": { "type": "number", "description": "Maximum number of comparables (default 6, max 20)." } } }arguments 16 linesget_job_detail reads unknown 8h ago
Get the complete record of one job listing in Portugal by its slug. Use this after search_jobs when the user asks about a specific role: full description, requirements, salary (gross/net/estimated), employer, contract type and the outbound URL to apply.
{ "type": "object", "required": [ "slug" ], "properties": { "slug": { "type": "string", "description": "Unique listing slug, as returned by search_jobs." } } }arguments 12 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 id70d877557e6990c7.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/70d877557e6990c7/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/70d877557e6990c7?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.