updated 2026-10-16 20:06 UTC

Himalayas Remote Jobs

Repository Website

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.

MCP Servers Listed MIT

Is Himalayas Remote Jobs safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.0 / 10
Provenance None
Signed commits 60%
Last push 71d ago
Compare Himalayas Remote Jobs

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Himalayas Remote Jobs scores 43.2/100 (Grade D), ranked #1157 of 1378 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 could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Himalayas Remote Jobs and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/Himalayas-App/himalayas-mcp, MIT, last pushed 2026-08-06. 60% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.0/10 (scanned Oct 16, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions9
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests -1
    CII-Best-Practices 0
    Code-Review 0
    Contributors 6
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 9
    Vulnerabilities 10

  3. Published packages None

    No registry package. Himalayas Remote Jobs is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-09-09 OSSF Scorecard: 4.0/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Himalayas Remote Jobs’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Himalayas Remote Jobs compares in MCP Servers

  1. #663 Memory MCP 43.5 +0.3
  2. #664 Google Health Fitbit MCP 43.3 +0.1
  3. #665 Himalayas Remote Jobs 43.2 this agent
  4. #666 Apple Docs MCP 43.2 ±0
  5. #667 Claude Context 43.2 ±0

Bars show each HVTrust score; the tick marks Himalayas Remote Jobs’s 43.2.

Where the 43.2 comes from

HVTrust dimensions vs the MCP Servers average

43.2 / 100 · 100.0% confidence

Himalayas Remote Jobs MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.0 / 25
2.5 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
11.9 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
7.3 / 20
5.0 below avg 12.3
AdoptionLog-scaled stars · package downloads
3.2 / 20
4.2 below avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-09
Rank Moved
Rank dropped 11 spots (#1116 → #1127)
2026-09-30
Rank Moved
Rank dropped 11 spots (#1088 → #1099)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.0/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Refresh maintenance signals The repo was last pushed 71 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Himalayas Remote Jobs View MCP Servers Report missing data
27.1
Activity sub-score · out of 100
#665
In MCP Servers

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 →

Signals refreshed 2026-10-16 20:06 UTC · Repo last pushed 71 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
21
Forks
6
Last Push
2026-08-06
71 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
2
Rank Change
▼1
was #1156

Analysis

Activity Inputs

27.1 / 100
StarsRepository reach
8.1 / 30
FreshnessLast push recency
15.1 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
3.9 / 20

Common questions about Himalayas Remote Jobs

Public trust evidence for Himalayas Remote Jobs is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Himalayas Remote Jobs publish package provenance?
No published build provenance is currently detected for Himalayas Remote Jobs. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Himalayas Remote Jobs have an OpenSSF Scorecard?
Himalayas Remote Jobs has an OpenSSF Scorecard score of 4.0/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Himalayas Remote Jobs actively maintained?
Slowing down. Last push was 71 days ago — keep an eye on whether activity resumes.
What license does Himalayas Remote Jobs use?
Himalayas Remote Jobs ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Himalayas Remote Jobs's commits signed?
60% of the last 100 commits to Himalayas Remote Jobs are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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
Scored in HVTrust

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 Server Support
medium confidence
Implemented
Himalayas Remote Jobs appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

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.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 19Listed 2HVTrust 2Scorecard 1Delisted 1MCP 1
2026-10-09
Rank Moved
Rank dropped 11 spots (#1116 → #1127)
2026-09-30
Rank Moved
Rank dropped 11 spots (#1088 → #1099)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 393 spots (#675 → #1068)
2026-09-23
HVTrust Changed
HVTrust up 13.4pts (31.3 → 44.7)
2026-09-22
Newly Listed
First tracked at rank #675
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank dropped 12 spots (#1051 → #1063)
2026-09-12
Rank Moved
Rank dropped 12 spots (#1033 → #1045)
2026-09-09
Scorecard Added
OSSF Scorecard: 4.0/10
2026-09-09
Rank Moved
Rank rose 292 spots (#1317 → #1025)
2026-09-09
HVTrust Changed
HVTrust up 25.9pts (19.6 → 45.5)
2026-09-05
Rank Moved
Rank dropped 12 spots (#1291 → #1303)
2026-09-03
Rank Moved
Rank dropped 16 spots (#1267 → #1283)
2026-09-02
Rank Moved
Rank dropped 21 spots (#1246 → #1267)
2026-09-01
Rank Moved
Rank dropped 19 spots (#1227 → #1246)
2026-08-31
Rank Moved
Rank dropped 22 spots (#1205 → #1227)
2026-08-30
Rank Moved
Rank dropped 21 spots (#1184 → #1205)
2026-08-29
Rank Moved
Rank dropped 23 spots (#1161 → #1184)
2026-08-28
Rank Moved
Rank dropped 27 spots (#1134 → #1161)
2026-08-27
Rank Moved
Rank dropped 19 spots (#1115 → #1134)
2026-08-26
Rank Moved
Rank dropped 62 spots (#1053 → #1115)
2026-08-17
Rank Moved
Rank rose 13 spots (#1054 → #1041)
2026-08-16
Rank Moved
Rank dropped 33 spots (#1021 → #1054)
2026-08-10
Rank Moved
Rank dropped 58 spots (#961 → #1019)
2026-08-08
Newly Listed
First tracked at rank #957
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 43.2 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/himalayas-remote-jobs.svg)](https://hvtracker.net/agents/himalayas-remote-jobs)
HTML:
<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

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON