_ registry / mcp http-sse · checked 1h ago

nue_people_Homepage

https://www.nuepeople.com

Registry code: d12fbe49aef401a9

api record

Public MCP server for discovering open jobs. Search, filter, and get application links.

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

endpoint
https://www.nuepeople.com/mcp
protocol
http-sse ·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 nue_people_Homepage live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is nue_people_Homepage free to use?
Yes — the hub reached it with no key and no payment.
What tools does nue_people_Homepage have?
5 tools: search_jobs, list_contract_types, get_skill_clusters, get_application_link, get_job_details.
Is nue_people_Homepage 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
98.7%

90 days 98.6%· all time 98.6%

latency
186ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 359 checks · signed record
  • degraded → live
  • live → degraded· fetch failed
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • search open jobs
  • get job details
  • get a job application link
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
4 open 1 never probed 4 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.

  • list_contract_types reads open 15h ago

    Lists the available contract types, including IDs and names. Use this tool when the user wants to filter search_jobs by contract type.

    mcp-tool

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

    Returns the current skill cluster data for public jobs on the nü people website. Use this tool when the user wants an overview of which skills or technologies are currently in demand.

    mcp-tool

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

    Returns the direct application link for a public open job. Use this tool when the user wants to apply for a specific job after identifying it via search_jobs or get_job_details.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "jobId": {
          "default": null,
          "description": "Job ID from a previous search_jobs result. Accepts an integer or an integer represented as a string."
        }
      }
    }
    arguments 9 lines
  • get_job_details reads open 8h ago

    Returns public details for a single open job by ID. Use this tool after search_jobs when the user wants more information about one specific job.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "id": {
          "default": null,
          "description": "Job ID from a previous search_jobs result. Accepts an integer or an integer represented as a string."
        }
      }
    }
    arguments 9 lines
  • search_jobs reads unknown 15h ago

    Searches currently open jobs on the nü people website. Use this tool when the user wants to find matching jobs by keyword, role, skill, location, or contract type. Returns a list of public job summaries.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "Search query, such as a role, skill, technology, or job title, for example 'Senior C# Developer' or 'Kubernetes'."
        },
        "location": {
          "type": [
            "string",
            "null"
          ],
          "default": null,
          "description": "Optional city filter, for example 'Munich'."
        },
        "maxResults": {
          "type": "integer",
          "default": 10,
          "description": "Maximum number of results to return. Allowed range: 1 to 25. Default: 10."
        },
        "contractTypeId": {
          "type": [
            "integer",
            "null"
          ],
          "default": null,
          "description": "Optional contract type ID. Use list_contract_types first if the user wants to filter by contract type."
        }
      }
    }
    arguments 33 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 d12fbe49aef401a9.

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