remoet-mcp server
io.github.remoet-labs/remoet-mcpremoet-labsstreamable-httpv1.0.0Scanned
Job platform for AI agents. Track tech jobs from companies that match your stack.
24 tools: 4 can delete or cancel things, 9 change things and 11 only read.
- Reads private data · 2
- Reads text others write · 2
- Can send data out · 1
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the remoet-mcp server can do
The remoet-mcp server is published by the GitHub account remoet-labs. It has 24 tools. It can delete or cancel things (4 tools: delete_profile_item, unstar_listing, unsave_job and delete_linktree) and create or change data (9 tools: update_profile, save_work_experience, save_project, save_education and 5 more). 11 tools only read.
2 tools read private data (get_digests and get_linktrees); 2 tools bring in text other people can write (get_digests and get_linktrees); 1 tool can send data out of your system (update_profile). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 2 findings (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
24 tools
Deletes or cancels 4Claude Code: deny
delete_linktreeDelete a link tree page.No findings
Why it is in this group
- The name "delete_linktree" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Delete a link tree page. Link tree ids come from get_linktrees. Confirm with the user before deleting.
Annotations the server declares
- title: Delete Link Tree
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
delete_profile_itemDelete a profile item: a work experience entry, a project, or an education entry (set type accordingly).No findings
Why it is in this group
- The name "delete_profile_item" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Delete a profile item: a work experience entry, a project, or an education entry (set type accordingly). Use this to clean up duplicates, placeholder/test entries, or clearly wrong data. Ids come from get_profile. Always confirm with the user before deleting anything that could be real.
Annotations the server declares
- title: Delete Profile Item
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
unsave_jobRemove a job from the user's saved list.No findings
Why it is in this group
- The description's first verb is "remove": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Remove a job from the user's saved list. Saved job ids come from get_saved_jobs. Confirm with the user before removing.
Annotations the server declares
- title: Remove Saved Job
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
unstar_listingRemove a star from a company listing.No findings
Why it is in this group
- The name "unstar_listing" says "unstar": a word for a change.
- The description's first verb is "remove": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Remove a star from a company listing. WARNING: Unstarring consumes from your unstar budget (per 30-day period), EXCEPT when the user is over their star cap (then trimming back to the limit is free). This prevents unlimited cycling of stars. The remaining unstar budget is reported by get_account. Only unstar if the company is truly not relevant. Do NOT mass-unstar to get a user under their cap unless they explicitly ask. If they are over cap, surface the choice and let them decide which to keep.
Annotations the server declares
- title: Unstar Company
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
Changes things 9Claude Code: ask
apply_to_jobApply to a job on behalf of the user, or get its application link.No findings
Why it is in this group
- The name "apply_to_job" says "apply": a word for a change.
Description, as the server wrote it Apply to a job on behalf of the user, or get its application link. Two outcomes by job type: internal jobs (posted directly through Remoet's partner system) are applied to end-to-end and return the created application; scraped jobs (most of the platform) return applicationType "external" with the applicationUrl where the user applies on the company's site. Share that link with the user; Remoet cannot submit external applications for them. Applying to an internal job submits a real application in the user's name, so it needs the user's explicit consent. Internal jobs must be published and not expired, and the user can only apply once per job: duplicate applications are rejected.
Annotations the server declares
- title: Apply to Job
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
create_linktreeCreate a link tree page: a shareable page with the user's links (social media, portfolio, GitHub, etc.).No findings
Why it is in this group
- The name "create_linktree" says "create": a word for a change.
Description, as the server wrote it Create a link tree page: a shareable page with the user's links (social media, portfolio, GitHub, etc.). Each account can create up to 10. The slug becomes the public URL. Slug rules: 5-20 characters, lowercase letters, numbers, and hyphens only, cannot start/end with a hyphen. Must be unique. Use the user's name or handle as a base for the slug. The usual links are the ones on the user's profile (githubUrl, linkedinUrl, twitterUrl, url), which get_profile returns. Remoet tracks views and link clicks on each link tree, so a link tree URL on a CV or application shows whether a recruiter opened it.
Annotations the server declares
- title: Create Link Tree
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
save_educationAdd or update an education entry (upsert).No findings
Why it is in this group
- The name "save_education" says "save": a word for a change.
Description, as the server wrote it Add or update an education entry (upsert). Omit id to create (institution is required); pass an id (from get_profile) to update, changing only the fields you send. Ask about degrees, bootcamps, and notable certifications. Confirm approximate dates with the user rather than guessing; don't fabricate. Saving without an id always creates a new entry.
Annotations the server declares
- title: Save Education
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
save_jobSave a job to the user's list for later.No findings
Why it is in this group
- The name "save_job" says "save": a word for a change.
Description, as the server wrote it Save a job to the user's list for later. Supports both AI-extracted jobs (from search_jobs or get_starred_jobs) and internal partner jobs. This gives the agent memory across sessions. Saved jobs persist so the user doesn't lose track of interesting roles. Optionally attach a note (e.g. "Great fit for React skills", "Follow up next week"). Each job can only be saved once.
Annotations the server declares
- title: Save Job
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
save_projectAdd or update a portfolio project (upsert).No findings
Why it is in this group
- The name "save_project" says "save": a word for a change.
Description, as the server wrote it Add or update a portfolio project (upsert). Omit id to create (title and shortDescription are required); pass an id (from get_profile) to update, changing only the fields you send. Projects are the #1 differentiator for junior/mid developers. Help the user recognize work they might not think of: side projects, open-source contributions, hackathon entries, internal tools, time-saving scripts, blogs, personal apps. Saving without an id always creates a new entry. Saved entries appear on the user's public profile, so they should describe real work.
Annotations the server declares
- title: Save Project
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
save_work_experienceAdd or update a work experience entry (upsert).No findings
Why it is in this group
- The name "save_work_experience" says "save": a word for a change.
Description, as the server wrote it Add or update a work experience entry (upsert). Omit id to create a new entry (title and startDate are required); pass an id (from get_profile) to update an existing one, changing only the fields you send. Every description should cover WHAT was built, HOW (technologies), IMPACT (users served, performance gains, revenue, uptime), and SCOPE (team size, scale). Push for measurable outcomes ("Built React frontend" -> "...serving 50K users, 40% faster"). The technologies array feeds job matching. Saving without an id always creates a new entry. Saved entries appear on the user's public profile, so they should describe real experience. Ask the user to confirm vague dates or fill real gaps.
Annotations the server declares
- title: Save Work Experience
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
star_listingStar/save a company listing.No findings
Why it is in this group
- The name "star_listing" says "star": a word for a change.
Description, as the server wrote it Star/save a company listing. Starring subscribes you to their job postings. Starred company jobs appear in get_starred_jobs. Starring also unlocks the company's FULL tech stack (unstarred listings only show a small preview). Starring is FREE. It does not consume budget. However, there is a limit on how many active stars you can have at once. Remaining star slots are reported by get_account. CRITICAL: Only star companies where the user's tech stack genuinely overlaps with the company's tech stack. A React/Node developer should NOT star a company that only uses Go or Java. Irrelevant stars pollute the job feed with noise. Every star must be a deliberate, high-quality match. A company returned by a techStack-filtered search_listings call confirms the technologies in its matchedTechStack field (the filter checks the full stack, including the part hidden from the preview), so judge overlap by matchedTechStack, not the visible preview.
Annotations the server declares
- title: Star Company
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
update_profileUpdate the user's Remoet profile core and/or their visibility.Can send data outNo findings
Why it is in this group
- The name "update_profile" says "update": a word for a change.
What it can reach
- outboundThe input takes a destination (input.phone): what the tool writes goes there.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Update the user's Remoet profile core and/or their visibility. Only provide the fields you want to change. Omitted fields are left as-is; pass null to clear a field. If the source data (CV, website, etc.) is missing a field, ask the user rather than guessing. Never copy placeholder text like "lorem ipsum". The account email cannot be changed through this tool. VISIBILITY: pass visibility to control who can see the profile in company candidate lists: NONE (hidden), STARRED (only companies the user has starred, the recommended two-way match), or ALL (every company). Explain the trade-off before changing it. SUMMARY WRITING GUIDE: the summary is the most important field, the first thing companies read. Pattern: [Role] with [X years] experience in [core tech stack]. [One differentiator or achievement]. Example: "Senior Full-Stack Developer with 8 years of experience in React, Node.js, and AWS. Built and scaled a SaaS platform serving 200K users." Under 500 characters. Avoid generic fluff like "passionate developer". Be specific and quantifiable.
Annotations the server declares
- title: Update Profile
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
update_saved_job_noteUpdate the note on a saved job.No findings
Why it is in this group
- The name "update_saved_job_note" says "update": a word for a change.
Description, as the server wrote it Update the note on a saved job. Use this to add context, track application status, or record follow-up reminders. Pass null to clear the note.
Annotations the server declares
- title: Update Saved Job Note
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 11Show 11 read-only tools
get_accountThe user's account status in one call: every budget the platform enforces (active stars vs cap, unstars used vs the 30-day unstar budget, MCP requests today vs daily cap, REST API …No findings
Why it is in this group
- The name "get_account" says "get": a word for reading.
Description, as the server wrote it The user's account status in one call: every budget the platform enforces (active stars vs cap, unstars used vs the 30-day unstar budget, MCP requests today vs daily cap, REST API requests today vs daily cap, each with a resetsAt), the remaining limits (link-tree cap), and any over-cap/grace state. Calling it is free and never counts against a cap. Every limit is a plain number. Remoet is free. There is nothing to upgrade to and nothing to sell: if the user is at a limit, help them work within it.
Annotations the server declares
- title: View Account
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_appsList approved apps built on the Remoet platform.No findings
Why it is in this group
- The name "get_apps" says "get": a word for reading.
Description, as the server wrote it List approved apps built on the Remoet platform. These are community and official apps that extend Remoet's functionality. Each app has a repo URL for deployment and a demo URL to try it out. Use this to help users discover tools that complement their Remoet workflow, e.g. portfolio sites, CV generators, job trackers, etc. You can filter by category or tag.
Annotations the server declares
- title: Browse Apps
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_digestsHISTORICAL ONLY: the user's archived job digests, the email summaries Remoet used to send about new jobs from their starred companies.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_digests" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "email": it reads mail.
- untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
Description, as the server wrote it HISTORICAL ONLY: the user's archived job digests, the email summaries Remoet used to send about new jobs from their starred companies. No new digest has been generated since 2026-07-06, when the feed roundup replaced that pipeline, so this returns nothing at all for an account created since then. What carries new roles now is get_feed (the composed dashboard stream, and what the roundup emails are built from); for searching, use get_starred_jobs or search_jobs. Reach for this tool only when the user asks about their old email summaries by name. Without an id: the 20 most recent as lightweight summaries (id, title, frequency, jobCount, createdAt). With an id: that digest's full markdown body (each job's title, application URL, salary, remote policy, experience level, tech stack).
Annotations the server declares
- title: View Digests
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_feedThe user's dashboard feed as ONE composed stream, chronological newest first.No findings
Why it is in this group
- The name "get_feed" says "get": a word for reading.
Description, as the server wrote it The user's dashboard feed as ONE composed stream, chronological newest first. Each entry has a kind: 'item' (per-company job items from their starred companies - the company, when it landed, role snapshots with job id/title/application URL/salary/remote policy/experience level/tech stack, and per-role flags isActive, savedJobId, matchesFilters, plus per-item isStarred: false means the user unstarred that company since), 'job_of_the_day' (one daily editorial pick from anywhere on the platform - a discovery candidate worth surfacing), 'blog' and 'broadcast' (platform content; usually skim). Pass nextCursor back to page deeper; omit it for the newest page.
Annotations the server declares
- title: View Feed
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_linktreesThe user's link tree pages: shareable single-page URLs for a CV, email signature, or job application, with per-link view/click tracking so recruiter engagement is measurable.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_linktrees" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "email": it reads mail.
- untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
Description, as the server wrote it The user's link tree pages: shareable single-page URLs for a CV, email signature, or job application, with per-link view/click tracking so recruiter engagement is measurable. Without a slug: all of the user's link trees (each with its id and slug). With a slug: that page's content plus its engagement data (views, clicks per link), which answers "has anyone looked at my link tree?".
Annotations the server declares
- title: View Link Trees
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_listingWorks without a Remoet account.1 finding
Why it is in this group
- The name "get_listing" says "get": a word for reading.
Findings
- Info
The description is 2,246 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ew, same contract as search_listings. The star budget is reported by get_account."
Description, as the server wrote it Works without a Remoet account. Get detailed information about a specific company listing by its slug. Use this to review a company before deciding whether to star it. Returns the company's full description, perks, job count, and URLs. hiringStats shows how often the company opens roles and how long roles stay listed, counted in distinct roles: newRoles30d/newRoles90d (roles posted in the window, by the board's own publish date where it gives one, else when Remoet first saw the role), closedRoles90d (roles taken down), and medianDaysListed (median days from posting to takedown, over medianSampleSize roles closed in the last 180 days). A takedown is not a confirmed hire, so report how long roles stay listed, never a time to hire. A null count means Remoet cannot answer it honestly: tracking began inside the window (see trackedSince), or most of the board came down at once (a dead board or broken source) so the closed count is unknown. A null median means fewer than 5 closed roles or under 180 days of tracking. monthly[] has newRoles and closedRoles per UTC calendar month, oldest first, up to 12; the last month is the current, partial one, and months before tracking began are left out (closedRoles is null in a month with a board event). salaryStats gives pay bands over the company's live roles on the public board that state a salary (rolesWithSalary; it can be lower than jobCount, which also counts roles Remoet does not publish): bands[] has label 'all' plus 'junior'/'mid'/'senior' where at least 5 roles back it, each with medianFrom, medianTo, p25From, p75To and sampleSize. medianTo and p75To are null when fewer than 5 of those roles state an upper figure: there is no honest top to quote, not missing data. Figures are stated salaries converted to USD a year, not salaries posted in USD; say so when quoting them. NOTE: the tech stack is a small preview unless the company is starred. Starring unlocks the full stack (techStackCount shows the true total, e.g. a 3-tag preview of 147). Pass checkTechStack with the user's technologies to verify overlap against the FULL stack. Matched ones come back in matchedTechStack and lead the preview, same contract as search_listings. The star budget is reported by get_account.
Annotations the server declares
- title: View Company Details
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_profileThe user's complete Remoet profile in one call: profile core (summary, links, location, avatar), workExperience, projects, and education (each section entry carries an id for updat…No findings
Why it is in this group
- The name "get_profile" says "get": a word for reading.
Description, as the server wrote it The user's complete Remoet profile in one call: profile core (summary, links, location, avatar), workExperience, projects, and education (each section entry carries an id for update/delete) plus the current visibility setting. The ids it returns are the ones the save_* and delete_profile_item tools take. What the fields affect: the summary is the first thing companies read; the technologies arrays on work entries and projects feed job matching, so an empty array drops that entry out of matching; visibility NONE hides the user from every company's candidate list, STARRED shows them to the companies they have starred, ALL to every company.
Annotations the server declares
- title: View Profile
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_saved_jobsGet the user's saved jobs list.No findings
Why it is in this group
- The name "get_saved_jobs" says "get": a word for reading.
Description, as the server wrote it Get the user's saved jobs list. This is the user's job search memory: shows all jobs they've bookmarked across sessions, with notes and job details. Includes both AI-extracted jobs and internal partner jobs (see jobType field). It shows the user's existing pipeline, so jobs they have already saved can be told apart from new ones. Paginated, newest saves first. Each saved job includes isActive and deactivatedAt fields. If isActive is false, the job is no longer appearing on the company's careers page. This usually means it was filled or expired, but could also be a temporary scraper issue (there is a grace period before deactivation). A saved job the user can no longer see (its company is no longer starred, or a partner role was unpublished) keeps its entry but comes back with job: null, locked: true and a lockedReason to pass on. If job is null without locked, the listing was deleted entirely. A deactivated job may still be open on the company's careers page.
Annotations the server declares
- title: View Saved Jobs
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_starred_jobsGet job postings from the user's starred companies.No findings
Why it is in this group
- The name "get_starred_jobs" says "get": a word for reading.
Description, as the server wrote it Get job postings from the user's starred companies. This is the user's own curated feed. If the user has no stars, this returns nothing. In that case, use search_jobs instead: it reads the public catalogue. Supports filtering by search query, location, tech stack, remote policy, experience level, and minimum salary. Results are paginated. Same-title postings from one company are grouped into a single row: postingCount and postingLocations show how many raw postings it represents and where (boards often post one role per location). Results can be bookmarked with save_job. A single filtered query can miss good roles; an unfiltered call returns the whole feed, paginated. The techStack filter uses OR logic: specifying ["React", "TypeScript", "Node.js"] returns jobs matching AT LEAST ONE of them (technologies are auto-normalized and matched across spelling variants), so filter by the technologies that genuinely matter and judge each job's fit from its own techStack field. Use searchQuery for role-based searches ("senior engineer", "frontend", "platform") and techStack for technology-based filtering. OVER-CAP WARNING: if the response includes a "starsOverCap" field, the user has more starred companies than the limit allows and the surplus is scheduled for PERMANENT deletion on the given date. Proactively tell the user (count + date) and let them choose which companies to unstar down to the limit. NEVER unstar companies on the user's behalf just to get under the limit unless they explicitly ask you to.
Annotations the server declares
- title: View Job Feed
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
search_jobsWorks without a Remoet account.1 finding
Why it is in this group
- The name "search_jobs" says "search": a word for reading.
Findings
- Info
The description is 2,429 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...chStack: ["Go", "Kubernetes"], location: ["Berlin"], remotePolicy: ["remote"] })."
Description, as the server wrote it Works without a Remoet account. Search Remoet's PUBLIC job catalogue: every role on the open board at remoet.dev/jobs, across all companies, not just the ones the user has starred. No star is needed and none is consumed. Use this to answer "what is out there" for any technology, title or company; use get_starred_jobs instead for the user's own curated feed. Each result carries the role's public Remoet URL, which is a real page anyone can open, plus applyUrl (the employer's own posting, where an application actually happens) and companySlug (the same slug get_listing takes, for company detail). Roles that Remoet is not permitted to publish never appear here. Duplicate postings of one role at a company are collapsed into a single result, so totalCount is the number of distinct roles, not raw postings. duplicateCount is how many postings collapsed into it; boards usually duplicate a role per location, but nothing guarantees that, so do NOT report it as a number of locations. firstSeenAt is when Remoet first saw the role, not when the employer posted it, and lastVerifiedAt is the last time Remoet confirmed it was still open. Filters are searchQuery (title, Remoet summary and tech stack), techStack (ANY of the given technologies, or EVERY one under techStackMatch: "all", which is how you express a must-have stack), companySlug, location, remotePolicy, experienceLevel and salaryMin. A salaryMin floor drops every role Remoet holds no numeric salary for, which is roughly 45% of the board, so use it when salary is a hard requirement and leave it off otherwise. location matches the canonical places Remoet stores per role rather than the free-text location string, so a country also finds roles that name only one of its cities; searchQuery does NOT read location, so filter by place with location and not by typing the place into searchQuery. When a search returns nothing, the hint says which filter emptied it and how many roles dropping that one filter would return, so act on the hint rather than guessing at which filter to relax. Results are newest-first unless you ask otherwise: sortBy takes "newest" or "salary", with sortOrder asc or desc. Start broad and narrow: a single heavily filtered query misses good roles. Results can be bookmarked with save_job. Example: search_jobs({ searchQuery: "platform engineer", techStack: ["Go", "Kubernetes"], location: ["Berlin"], remotePolicy: ["remote"] }).
Annotations the server declares
- title: Search Public Jobs
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
search_listingsWorks without a Remoet account, except starred: true.No findings
Why it is in this group
- The name "search_listings" says "search": a word for reading.
Description, as the server wrote it Works without a Remoet account, except starred: true. Search companies on Remoet, or list the user's starred companies (starred: true). Returns a summary per result. Full detail (description, perks, URLs) is on get_listing, by slug. Job boards and aggregators are excluded; talent networks that post direct roles (e.g. Toptal) appear as companies. CRITICAL, star quality: only star companies whose tech stack OVERLAPS the user's skills (a JavaScript dev should not star a Go/Rust-only shop). Stars are the user's job-feed noise filter, so an irrelevant star pollutes their feed with jobs they can't use. Judge overlap by each result's matchedTechStack: the technologies from your techStack filter that the company actually uses, checked against its FULL stack (not the capped preview), so do NOT skip a company just because the visible preview omits the user's skills. An empty matchedTechStack means the result matched on text, not tags. techStackCount is the company's true tag total; the full stack unlocks on starring. techStack matches AT LEAST ONE filtered technology by default; set techStackMatch:"all" to require every one. starred: true limits results to the user's starred companies; combined with techStack it returns matchedTechStack per starred company, which shows any star with zero overlap. Example: search_listings({ searchQuery: "payments", techStack: ["TypeScript", "React"], experienceLevel: ["mid"] }).
Annotations the server declares
- title: Search Companies
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
4 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__remoet__update_profile"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:10 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 13
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://api.remoet.dev/.well-known/oauth-protected-resource/mcp/oauth
- Authorization servers
- https://api.remoet.dev/mcp/oauth
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 13 tools that change things (4 destructive, 9 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.remoet.dev/mcp/oauth: tools/list returned 24 tools to an anonymous client, including delete_profile_item (destructive), unstar_listing (destructive), unsave_job (destructive), delete_linktree (destructive), update_profile (write) and 8 more
Findings
Matches of fixed checks, with the text they matched.
- Infoget_listing
The description is 2,246 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ew, same contract as search_listings. The star budget is reported by get_account."
- Infosearch_jobs
The description is 2,429 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...chStack: ["Go", "Kubernetes"], location: ["Berlin"], remotePolicy: ["remote"] })."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:get_listingOnly readsdescription
Tools2 changed.~2 changedView diff
- Changed:get_listingOnly readsdescription
- Changed:update_profileChanges thingsdescriptioninputSchema
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http remoet https://api.remoet.dev/mcp/oauthclaude mcp add --transport http remoet https://api.remoet.dev/mcp/oauthRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__remoet__get_profile",
"mcp__remoet__search_listings",
"mcp__remoet__get_listing",
"mcp__remoet__search_jobs",
"mcp__remoet__get_starred_jobs",
"mcp__remoet__get_saved_jobs",
"mcp__remoet__get_feed",
"mcp__remoet__get_digests",
"mcp__remoet__get_apps",
"mcp__remoet__get_linktrees",
"mcp__remoet__get_account"
],
"ask": [
"mcp__remoet__update_profile",
"mcp__remoet__save_work_experience",
"mcp__remoet__save_project",
"mcp__remoet__save_education",
"mcp__remoet__star_listing",
"mcp__remoet__save_job",
"mcp__remoet__update_saved_job_note",
"mcp__remoet__create_linktree",
"mcp__remoet__apply_to_job"
],
"deny": [
"mcp__remoet__delete_profile_item",
"mcp__remoet__unstar_listing",
"mcp__remoet__unsave_job",
"mcp__remoet__delete_linktree"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as remoet. Review it before you use it.
Capability tags behind 3 rules
- mcp__remoet__update_profile outbound
- mcp__remoet__get_digests private-data, untrusted-input
- mcp__remoet__get_linktrees private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.remoet-labs/remoet-mcp/verify?hash=0047f8449a42e5db5683e8bd2388dca0b58b348d2e620eb3cdb06ef979f628c9" | jq -e '.changed == false'Pinned hash 0047f8449a42, from Nov 20, 2026, 10:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.remoet-labs/remoet-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.remoet-labs/remoet-mcp)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:46 UTC.
remoet-mcp server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the remoet-mcp server safe?
- No scan can promise that. What its definitions show: 24 tools, 13 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the remoet-mcp server delete data?
- Yes. 4 tools can delete, cancel or revoke something: delete_profile_item, unstar_listing, unsave_job and delete_linktree.
Can the remoet-mcp server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the remoet-mcp server have?
- 24 tools: 4 destructive, 9 write, 11 read. delete_profile_item, unstar_listing, unsave_job, delete_linktree, update_profile, save_work_experience, save_project, save_education and 16 more.
Does the remoet-mcp server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the remoet-mcp server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): update_profile.
Has the remoet-mcp server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.