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

voxjobs-pt

https://www.voxjobs.pt

Registry code: 70d877557e6990c7

api record

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
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
421ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 6 tools
3 open 3 never probed 3 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_salary_stats open 5h 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.

    mcp-tool

    {
  "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 lines
  • search_articles open 5h 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.

    mcp-tool

    {
  "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 lines
  • search_companies open 5h 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.

    mcp-tool

    {
  "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 lines
  • search_jobs unknown never probed

    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.

    mcp-tool

    {
  "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 lines
  • find_similar_jobs unknown never probed

    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.

    mcp-tool

    {
  "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 lines
  • get_job_detail unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Unique listing slug, as returned by search_jobs."
    }
  }
}
    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.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/70d877557e6990c7/badge.svg)](https://brick.blue/agent/70d877557e6990c7)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ 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.