mcp-pulse

com.korture/hiring

com.korture/hiring

com.korture/hiring did not answer the probe on 2026-10-03. Result: needs auth (HTTP 401).

Who is wired for this role, in four plain facets, and what one change would widen it.

needs auth probed 2026-10-03 · HTTP 401 · Bearer

Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token","error_description":"Korture Hiring needs a Korture account. Sign in to continue."}
Endpoint
https://mcp.korture.com/api/mcp (streamable-http)
Host
mcp.korture.com
Repository
https://github.com/skprasad-korture/korture-mcp
Website
https://www.korture.com
Registry
active, updated 2026-08-20 · registry entry
Reachable
2 of the last 2 probes

History

We add a row when the result changes. A server with no change keeps its last row.

ProbedResultInitToolsTokens
2026-10-03 20:30needs auth
2026-10-03 17:48needs auth

Badge

mcp-pulse: needs auth

[![mcp-pulse](https://mcp-pulse.ulehla.dev/badge/com.korture/hiring.svg)](https://mcp-pulse.ulehla.dev/s/com.korture/hiring)