Himalayas Remote Jobs
Remote jobs MCP server — search 100,000+ remote jobs, post listings, find candidates, and check salary benchmarks from Claude, ChatGPT, Cursor, and any MCP client. Free, no API key required.
Is Himalayas Remote Jobs safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Himalayas Remote Jobs
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Himalayas Remote Jobs scores 44.5/100 (Grade D), ranked #1078 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.0/10; 60% of recent commits are signed; last pushed 2026-08-06. Every point is earned from checkable signals — never paid placement. How scoring works →
How Himalayas Remote Jobs compares in MCP Servers
- #629 Stats Compass 44.7 +0.2
- #630 GitMCP 44.5 ±0
- #631 Himalayas Remote Jobs 44.5 this agent
- #632 Ocm MCP Server 44.3 −0.2
- #633 Revolut MCP 44.2 −0.3
Bars show each HVTrust score; the tick marks Himalayas Remote Jobs’s 44.5.
Where the 44.5 comes from
HVTrust dimensions vs the MCP Servers average
44.5 / 100 · 100.0% confidenceHimalayas Remote Jobs MCP Servers average (775 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
29.9 / 100Supply Chain Trust
Common questions about Himalayas Remote Jobs
Does Himalayas Remote Jobs publish package provenance?
Does Himalayas Remote Jobs have an OpenSSF Scorecard?
Is Himalayas Remote Jobs actively maintained?
What license does Himalayas Remote Jobs use?
Are Himalayas Remote Jobs's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Himalayas Remote Jobs's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Himalayas Remote Jobs?
For maintainers
HVTrust scores Himalayas Remote Jobs from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/himalayas-remote-jobs)
<a href="https://hvtracker.net/agents/himalayas-remote-jobs"><img src="https://hvtracker.net/badge/himalayas-remote-jobs.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON