Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"remoet": {
"url": "https://api.remoet.dev/mcp",
"type": "http",
"headers": {
"Authorization": "Bearer YOUR_KEY"
}
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Connect your AI agent to Remoet, the job platform built for agents. Search tech companies by their real tech stack, star the ones you'd actually work for, pull jobs from that shortlist, and manage your developer profile, all through conversation.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in data / ai-ml
Query and manage PostgreSQL databases directly from AI assistants
Dynamic problem-solving through sequential thought chains
Persistent memory using a knowledge graph
Manage Supabase projects — databases, auth, storage, and edge functions
MCP Security Weekly
Get CVE alerts and security updates for io.github.remoet-labs/remoet-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Connect your AI agent to Remoet, the job platform built for agents. Search tech companies by their real tech stack, star the ones you'd actually work for, pull jobs from that shortlist, and manage your developer profile, all through conversation.
This repo ships a local stdio MCP server (Node + TypeScript) plus the metadata MCP clients and directory registries need. The local server advertises Remoet's full tool catalog (snapshotted from the live server) and forwards calls to the hosted MCP at https://api.remoet.dev/mcp with your Bearer key. The hosted server is closed source and remains the source of truth for execution.
Most users connect to the hosted server directly (see Quick install below). The local package is for clients that prefer stdio or build/scan systems that require a runnable local server.
https://api.remoet.dev/mcpRemoet has company-level tech stack data nobody else has, so an agent can match you to companies by the technologies they actually use, not recruiter keyword tags. Star the companies that fit, and your agent pulls fresh jobs from that shortlist. It also manages your profile, applications, saved jobs, and weekly digests, all over MCP.
Free tier is the whole product with caps. Paid tiers unlock real-time job data and higher limits. No credit card for the free tier.
See tools.md for the full tool catalog.
Claude Code, Claude Desktop, Claude Web, Cursor, VS Code, Windsurf, Codex, and any MCP-compatible client. Also installable as an agentskills.io skill on OpenClaw (via ClawHub) and Hermes Agent. See Quick install.
Two transports, same tools:
https://api.remoet.dev/mcp expects an API key as a Bearer header (Authorization: Bearer <key>). Best for CLI and always-on agents.https://api.remoet.dev/mcp/oauth runs OAuth 2.1 with PKCE and dynamic client registration. Best for browser clients like Claude Web and Desktop custom connectors.Generate a key at remoet.dev/onboarding. The same key works for MCP and the REST API.
claude mcp add --transport http --scope user remoet https://api.remoet.dev/mcp --header "Authorization: Bearer YOUR_KEY"
Then restart Claude Code (exit and relaunch) so the new server's tools load in a fresh session.
Add to your client's MCP config (the JSON in .mcp.json works as a template):
{
"mcpServers": {
"remoet": {
"type": "http",
"url": "https://api.remoet.dev/mcp",
"headers": { "Authorization": "Bearer YOUR_KEY" }
}
}
}
Add a custom connector pointing at https://api.remoet.dev/mcp/oauth and complete the browser sign-in. No API key to paste.
Remoet also ships as an agentskills.io skill, with one-command installs on Hermes and OpenClaw.
hermes skills tap add remoet-labs/agent-skills
hermes skills install remoet-labs/agent-skills/skills/remoet
openclaw skills install remoet
I work in Rails, React, and Postgres. Which companies on Remoet hire for that stack?
If you prefer a local stdio MCP server (or a build/scan system needs one), the same package is runnable directly.
With Node:
npm install
npm run build
REMOET_API_KEY="<your-key>" node dist/index.js
The server speaks MCP over stdio. Set REMOET_API_KEY to a free-tier key from remoet.dev/onboarding. Optionally override the upstream endpoint with REMOET_MCP_URL (defaults to `https://api.remoet.dev/