Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Remote Impact Jobs

REMOTE · REMOTEIMPACT.ORG

Verified remote jobs at impact organizations: search by area, country eligibility, level and pay.

Available components

+4 this week 75 Trust /100

Last scanned (1 hour ago)

Scores higher than 69% of remote servers

Reachable. Last reached 23 Oct 2026.

Category Project Management

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 446 tokens (~111/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 67% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “search_jobs” rewrote its description, which is the text the model reads security
    • Schema quality: 92 → 111 ▼ functional
    • “search_jobs” added an optional parameter “salary_currency” cosmetic
    • “search_jobs” reworded the description of “min_salary” cosmetic
  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 14 Oct 26 +9
    • Authorization: unverified → partial ▲ security
    • Tool coverage: 55% → 64% ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • Tool “get_job” now declares an output schema ▲ functional
    • Tool “get_organization” now declares an output schema ▲ functional
    • Tool “list_areas” now declares an output schema ▲ functional
    • Tool “search_jobs” now declares an output schema ▲ functional
    • First check of Tool coverage: 100 functional
    • “get_organization” reworded the description of “slug” cosmetic
  • 13 Oct 26 62

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 23 Oct 2026 · Probed https://remoteimpact.org/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=remoteimpact.org CN=WE1,O=Google Trust Services,C=US 28 Aug 2026 26 Nov 2026 ECDSA 256 ECDSA-SHA256 d6da7491b9242b470edbdba540be453e
SANs: remoteimpact.org, *.remoteimpact.org
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of remoteimpact.org. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
org. present 26974 8 Verified
remoteimpact.org. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.googletagmanager.com https://www.google-analytics.com https://js.stripe.com https://www.gstatic.com https://unpkg.com https://cdn.jsdelivr.net; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com data:; img-src 'self' data: https:; connect-src 'self' https://www.google-analytics.com https://region1.google-analytics.com https://api.stripe.com; frame-src 'self' https://js.stripe.com https://hooks.stripe.com; base-uri 'self'; form-action 'self' https://checkout.stripe.com; frame-ancestors 'none'; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(self), usb=(), interest-cohort=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://remoteimpact.org/mcp/ Verified 200
http (plaintext) http://remoteimpact.org/mcp/ HTTPS enforced 301 https://remoteimpact.org/mcp/
MCP tools · 4 exposed · ~320 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_job ~36

Full record for one open role by slug or id, including verification and eligibility.

NameTypeReqDescription
idstringyesJob slug or numeric id
NameTypeReqDescription
job–yes–

No examples provided.

get_organization ~44

Organization details (homepage, careers page) and its open roles on Remote Impact.

NameTypeReqDescription
slugstringyesOrganization slug, e.g. from a job's organization.slug
NameTypeReqDescription
jobsarrayyes–
organization–yes–

No examples provided.

list_areas ~23

Impact areas (categories) with the number of open roles in each.

Input schema present but exposes no named parameters.

NameTypeReqDescription
areasarrayyes–

No examples provided.

search_jobs ~217

Find currently listed remote roles with source and uncertainty information. Filter by text, impact area, the applicant's country, job type, level, minimum annual pay and recency. Returns the best matches with eligibility, pay and links (5 per call without a key, 10 with a free key, 25 with commercial access).

NameTypeReqDescription
areastring–Impact area slug from list_areas, e.g. climate-environment
countrystring–Country the applicant lives in, e.g. Kenya
job_typestring––
levelstring––
limitinteger––
min_salaryinteger–Minimum supported annual lower salary bound; requires salary_currency. No currency conversion.
posted_within_daysinteger––
querystring–Free text: role, skills, organization
salary_currencystring–Explicit pay currency, e.g. USD or EUR; required with min_salary.
worldwide_onlyboolean–Only roles open from anywhere
NameTypeReqDescription
jobsarrayyes–
totalintegeryes–

No examples provided.

Install

How do I install the Remote Impact Jobs MCP server?

Remote Impact Jobs is a hosted endpoint at https://remoteimpact.org/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · remoteimpact.org

# add to Claude Code
claude mcp add --transport http org-remoteimpact-jobs 'https://remoteimpact.org/mcp/'
Common questions

What is the Remote Impact Jobs MCP server?

Remote Impact Jobs is an MCP server listed in the public MCP registry as org.remoteimpact/jobs. Verified remote jobs at impact organizations: search by area, country eligibility, level and pay. This page covers its hosted endpoint (https://remoteimpact.org/mcp/).

Is the Remote Impact Jobs MCP server safe to use?

Remote Impact Jobs scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Remote Impact Jobs MCP server expose?

Remote Impact Jobs exposes 4 tools: search_jobs, get_job, list_areas, get_organization. Their descriptions and schemas cost roughly 320 tokens of context every time the server is loaded.

Does the Remote Impact Jobs MCP server require authentication?

No. We connected to Remote Impact Jobs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Remote Impact Jobs MCP server still maintained?

Remote Impact Jobs is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.