Home / MCP registry index / io.github.remoet-labs/remoet-mcp
io.github.remoet-labs/remoet-mcp
io.github.remoet-labs/remoet-mcp in the official MCP registry.
Endpoint https://api.remoet.dev/mcp/oauth. Source: github.com/remoet-labs/remoet-mcp.
The registry describes it as: Job platform for AI agents. Track tech jobs from companies that match your stack.
We read its 24 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
get_profile update_profile save_work_experience save_project save_education delete_profile_item search_listings get_listing star_listing unstar_listing search_jobs get_starred_jobs save_job get_saved_jobs update_saved_job_note unsave_job get_feed get_digests get_apps get_linktrees create_linktree delete_linktree apply_to_job get_account
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-remoet-labs-remoet-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.