Himalayas Remote Jobs MCP vs Pinpoint

Himalayas Remote Jobs MCP 50

No machine payment protocol; paid extras return Stripe checkout links (0). Plus price public (10 of 20). Free search and posting (20). Public tools need no account (20). 0 + 10 + 20 + 20 = 50.

Pinpoint 0

No x402, MPP or L402 (0). No prices are published. The site has a request pricing form that leads to a sales call (0). No free tier, sandbox or self-serve trial was found. Integration vendors can ask for a demo account by email (0). A customer admin creates the key in settings, and the MCP servers need that key or a browser sign-in (0). 0 + 0 + 0 + 0 = 0.

Himalayas Remote Jobs MCP 25

No status page found (0). No history (5). Some limits documented with numbers (100 candidate searches a day, 10 messages a minute) (10 of 15). No retry guidance (0). No SLA (0). Not labelled beta; the old SSE endpoint is retired with 410 Gone (10). 0 + 5 + 10 + 0 + 0 + 10 = 25.

Pinpoint 64

Graded on the REST API with the hosted lines. Statuspage site at status.pinpoint.support with three components (Pinpoint, Pinpoint Support, Social Advertising) and incident history, none named for the API (20). The history feed read on 2 November has one incident in the 90 days from 4 August, emails stuck in sending for 6 hours 41 minutes on 1 September 2026, which hit one function and reads as minor (20). The 8 October reading came from the page's /api/ path, which its robots.txt disallows, and is replaced by the feed. No request rate limit with numbers was found in the developer docs, llms.txt or the help centre (0). Every operation documents a 429 response with the code too_many_requests, but no Retry-After header, no backoff guidance and no idempotency keys were found (4). The July 2026 Sales Agreement sets a 99.5 per cent monthly uptime target with service credits, per the 8 October check, not re-read on 2 November (10). The API is v1 with a changelog at 1.0.28 and no beta label (10). 20 + 20 + 0 + 4 + 10 + 10 = 64.

Himalayas Remote Jobs MCP 42

OAuth 2.1 with PKCE and client metadata documents (25 of 30). Read-only public set; writes such as send_message and job posts are annotated (12 of 20). Job posts and recruiter messages are third-party text with no injection guidance (0). No audit log (0). No security.txt (404) or certifications found (5 of 20). The privacy policy follows the Australian Privacy Principles. 25 + 12 + 0 + 0 + 5 = 42.

Pinpoint 78

API keys are sent in the X-API-KEY header only. Each key is set to none, read, or write and delete per data category, can be edited and deleted, and several can exist. No expiry or rotation setting is described. The per-tenant MCP server uses OAuth with PKCE (S256), dynamic client registration, a revocation endpoint and two scopes, tools:read and tools:write (27). A key can be read-only, the MCP guide recommends a read-only key for AI tools, and the per-tenant MCP server acts with the signed-in user's permissions. No per-action confirmation is documented beyond the OAuth consent screen (15). CVs, cover letters and answers are candidate-written. The AI approach page lists red-teaming and guardrails for Pinpoint's own AI, and nothing addresses API or MCP clients (5). An API Logs tab lists every request with path, method, response, key, IP address and duration, and MCP actions are recorded against the user (15). ISO 27001, ISO 42001 and SOC 2 Type II, annual third-party penetration tests, and a valid security.txt on tenant hosts (contact security@pinpointhq.com, expiry 31 December 2027, read on 2 November on workwithus.pinpointhq.com; app.pinpointhq.com now disallows crawlers, so the 8 October reading there is struck). The vulnerability disclosure page still has no body. No bug bounty was found (16). 27 + 15 + 5 + 15 + 16 = 78.

Himalayas Remote Jobs MCP 46

Closed service under terms naming Himalayas Remote Jobs Pty Ltd (15). Privacy policy under the Australian Privacy Principles; retention periods not given (15 of 30). Dated retirement of the SSE endpoint (10 of 20). Subprocessors not found (5 of 20). 15 + 15 + 10 + 5 = 45.

Pinpoint 78

Closed service with a published Sales Agreement, dated July 2026 and governed by English law. The August 2025 and October 2025 versions are paths robots.txt now closes (15). The privacy policy, the Data Processing Addendum of July 2026 and the Sales Agreement are published. The addendum promises deletion within 30 days of termination and breach notice within 72 hours, while the security FAQ says 15 days for production and 45 days for backups, a small disagreement, per the 8 October check (22). No deprecation policy was found. Changelog 1.0.28 describes a change to US address fields made in May 2026 and calls two write restrictions temporary, with no end date (4). 21 sub-processors listed with purpose and location, updated 16 October 2025. Data is stored in Amsterdam, Dublin and London on AWS and DigitalOcean, and the sub-processor list adds Frankfurt (18). 15 + 22 + 4 + 18 = 59.

Himalayas Remote Jobs MCP 58

79 tools, about 78 KB (5), split into public, job-seeker and employer sets (5 back). Filters and paging on search (15 of 20). Errors not documented (5 of 20). All visible tools annotated, 34 read-only (20). Public tools work with no setup (8 of 15). 10 + 15 + 5 + 20 + 8 = 58.

Pinpoint 73

fields[...] sparse fieldsets for each resource type, extra_fields for costly attributes, include for related records and a .json suffix for a plainer body (22). page[number] and page[size] (default 100, maximum 1,000), sort, stats[total]=count and filters by job, stage, email, phone, dates and visibility (20). JSON:API errors with code, status, title and detail, such as X-API-KEY header not provided, with a help centre table of status codes (16). No idempotency keys. external_system_reference can be written and filtered on, creates are rejected for duplicate candidates where the company disallows them, and all five tools on the documentation MCP server carry readOnlyHint and destructiveHint (8). Create Application needs three attributes and a job, and list calls need none. No official SDK was found (7). 22 + 20 + 16 + 8 + 7 = 73.

Himalayas Remote Jobs MCP 50

Registry update and tag v1.0.3 on 21 October 2026 (30). Fewer than three dated releases found in 90 days (0). Repository issues not read (0). Official registry entry app.himalayas/mcp (15). Docs repository with server.json; server source not public (5 of 10). 30 + 0 + 0 + 15 + 5 = 50. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.

Pinpoint 40

Changelog entry 1.0.28 was posted on 4 August 2026 per the changelog page, 90 days before 2 November, the last day it counts, and no newer entry is listed in llms.txt (20). One API changelog entry falls in the 90 days from 4 August. The website also has monthly product release posts for August, September and October 2026, dated only by month and about the product rather than the API, so we give half (10). A public changelog, an integrations email address and a help centre with live chat (10). No official SDK was found, and we couldn't reach the official MCP registry to look for an entry (0). No packages to assess (0). 20 + 10 + 10 + 0 + 0 = 40.