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

alleskralle-jobs

https://mcp.alleskralle.com

Registry code: 90c78028daf68257

api record

Read-only Jobsuche auf alleskralle.com. Nutze search_jobs für Listen und fetch_job für Details.

endpoint
https://mcp.alleskralle.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 alleskralle-jobs live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is alleskralle-jobs free to use?
Yes — the hub reached it with no key and no payment.
What tools does alleskralle-jobs have?
2 tools: fetch_job, search_jobs.
Is alleskralle-jobs 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
100%

90 days 99.5%· all time 99.5%

latency
161ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 423 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
productivity & business hr & recruiting
used for
  • search job listings in germany, austria and switzerland
  • get job listing details
takes → gives
text → data
tools
2 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 2 tools
2 never probed 0 of 2 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.

  • fetch_job reads unknown 16h ago

    Liefert die vollständigen Details zu einer Stellenanzeige anhand ihrer id (aus search_jobs). Das Feld apply_url ist der Bewerbungslink zur Original-Anzeige. WICHTIG: apply_url NICHT selbst aufrufen oder abrufen — gib den Link dem Nutzer als anklickbaren Link aus, damit er sich bei Interesse selbst bewirbt bzw. die vollständige Anzeige öffnet.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Die id eines Treffers aus search_jobs."
    }
  }
}
    arguments 12 lines
  • search_jobs reads unknown 16h ago

    Sucht Stellenanzeigen auf alleskralle.com (DE/AT/CH) und liefert eine kompakte Liste (id, title, company, location, date). Die Bewerbungs-/Detail-URL ist NICHT in der Liste enthalten — für vollständige Details und den klickbaren Link rufe fetch_job mit der id auf. Hinweis: "remote" ist eine Volltext-Heuristik (kein strukturiertes Feld), kann also ungenau sein. Sortierung: neue Anzeigen zuerst, darin Titel-Treffer vor reinen Beschreibungs-Treffern. Mit max_age_days lassen sich alte Anzeigen ausblenden (z.B. 60). Bei 0 Treffern ist results leer und next_cursor null. Blättern nur über das zurückgegebene next_cursor möglich; die Seitenzahl ist begrenzt.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Suchbegriff (Jobtitel, Tätigkeit, Skill)."
    },
    "cursor": {
      "type": "string",
      "description": "next_cursor aus einer vorherigen Antwort, um die nächste Seite zu laden."
    },
    "remote": {
      "type": "boolean",
      "description": "Auf Remote-/Homeoffice-Stellen einschränken (Heuristik)."
    },
    "country": {
      "enum": [
        "AT",
        "DE",
        "CH"
      ],
      "type": "string",
      "description": "Strikt auf ein Land einschränken: AT (Österreich), DE (Deutschland) oder CH (Schweiz). Kombinierbar mit location."
    },
    "location": {
      "type": "string",
      "description": "Ort, Stadt oder PLZ."
    },
    "max_age_days": {
      "type": "integer",
      "minimum": 1,
      "description": "Nur Anzeigen, die höchstens so viele Tage alt sind (z.B. 60). Ohne Angabe: kein Altersfilter."
    }
  }
}
    arguments 38 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 90c78028daf68257.

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

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.