Skip to main content
Glama
478,259 tools. Updated 2026-08-26 06:13

"Resources for finding remote work opportunities" matching MCP tools:

  • Search JobYap job postings by natural-language query. Matches job titles, falling back to significant keywords when the full phrase finds little. Returns result ids, titles and citable URLs for use with fetch. For structured filtering (location, company, remote, freshness) prefer search_jobs.
    Connector
  • Maps only stable Tier1 finding identifiers to approved Tier1 services and public resources. Call after a Tier1 score or email-domain check. Do not submit prose, URLs, customer information, or invented identifiers. This tool performs no arbitrary fetching, makes no contact request, changes nothing, and stores nothing.
    Connector
  • Search 500+ quantum computing job listings using natural language. Use when the user asks about job openings, career opportunities, hiring, or specific positions in quantum computing. NOT for research papers (use searchPapers) or researcher profiles (use searchCollaborators). Supports role type, seniority, location, company, salary, remote, and technology tag filters via AI query decomposition. Limitations: quantum computing jobs only, last 90 days, max 20 results. Promoted listings appear first (marked). After finding jobs, suggest getJobDetails for full info. Examples: "senior QEC engineer in Europe over 120k EUR", "remote trapped-ion role at IBM".
    Connector
  • Explain what Pathrule CLI (power-user, terminal-first) and Pathrule Studio (GUI) unlock beyond Remote MCP. Call this when the user asks 'is there a better way?', 'why do I need to install something?', wants hook-level automation, or wants to compare surfaces. The response splits the pitch by audience (CLI for terminal-first, Pathrule Studio for GUI) and explains the real token-savings angle: hooks fire before every AI tool call and inject context for free, while remote MCP is manual mode where the AI spends tokens on each context fetch.
    Connector
  • Search for job listings by keyword, location, and filters. Returns job details, company info, and application links. Use this tool when users want to find jobs, search employment opportunities, or explore job openings. DO NOT use for: applying to jobs, submitting applications, or making employment decisions. LLM USAGE INSTRUCTIONS: - ALWAYS provide the keyword parameter (required) - When presenting results to users, include BOTH the job details URL (detailsPageUrl) AND the company page URL (companyPageUrl) for each job - Use location to find geographically relevant positions - Combine filters to refine searches (e.g., workplace_types=['Remote'] for remote work) - Use posted_date to find recent openings ('ONE'=1 day, 'THREE'=3 days, 'SEVEN'=7 days) - Default jobs_per_page is reasonable, increase for comprehensive searches - Use company_name to scope results to a specific employer - Use sort='datePosted' when the user wants the newest listings instead of the most relevant - Use facets to get aggregate counts (e.g., how many results are remote vs on-site) without paging through all results - After presenting results, do NOT automatically call get_job_details for every job returned. Wait for the user to indicate which specific job(s) they're interested in, then pass that job's guid to get_job_details. IMPORTANT - AI DISCLOSURE REQUIREMENT: When presenting job search results to users, you MUST include an appropriate disclosure that these results were retrieved using AI assistance. Example disclosure language: "These job listings were found using AI-powered search. Please review all job details carefully and verify information directly with employers before applying." This tool provides job listing data only. Final employment decisions should always involve human judgment and direct review of complete job postings. Args: keyword: The job keyword or title to search for (required) location: Geographic location for the job search (city, state, country) radius: Search radius from the specified location (minimum 1, requires radius_unit) radius_unit: Unit for search radius. Options: 'mi', 'km' (requires radius) jobs_per_page: Number of jobs to return per page (1-100, defaults to 5) page_number: Page number for pagination (1-based, default is 1) sort: Sort order for results. Options: 'relevance', 'datePosted' (defaults to relevance) posted_date: Filter by posting date. Options: 'ONE' (1 day), 'THREE' (3 days), 'SEVEN' (7 days) workplace_types: Workplace arrangements. Options: 'Remote', 'On-Site', 'Hybrid' employment_types: Employment types. Options: 'FULLTIME', 'CONTRACTS', 'PARTTIME', 'THIRD_PARTY', 'INTERNSHIP' employer_types: Employer types. Options: 'Direct Hire', 'Recruiter', 'Other' willing_to_sponsor: Filter for employers willing to sponsor work authorization (boolean) easy_apply: Filter for jobs with easy application process (boolean) company_name: Filter by company name fields: Specific fields to include in response (optional, returns all exposed fields by default) facets: Facet dimensions to aggregate (optional). Options: 'employmentType', 'postedDate', 'workFromHomeAvailability', 'workplaceTypes', 'employerType', 'easyApply', 'isRemote', 'willingToSponsor' Returns: JobSearchResult: Contains: - data: List of JobDisplayFields with job details including: * guid: The job's identifier to pass as job_id to get_job_details for the full description and skills list (NOT the `id` field, which is a different, internal identifier not accepted by get_job_details) * detailsPageUrl: Direct link to full job posting * companyPageUrl: Link to company profile page * title, summary, salary, location, employmentType, etc. - metadata: Search metadata with pagination info and facet results Raises: Exception: If API call fails or input validation errors occur
    Connector
  • Scan GitHub, Hacker News, and npm for new repos, packages, and discussions in the agent payments ecosystem (AP2, ACP, x402, MPP, UCP). Returns AI-classified and scored opportunities with recommended actions. Use when the user asks about recent activity, new developments, or opportunities in agent payments ('what's new in agent payments?', 'any new x402 repos?', 'scan for opportunities'). Use get_protocol_info instead for static protocol details, or compare_protocols for side-by-side comparison. Costs $0.01 USDC. Accepts: x402 (USDC on Base) or MPP (Tempo USDC).
    Connector

Matching MCP Servers

Matching MCP Connectors

  • チームの働き方を支援するグループウェア Work Handler の MCP サーバー。組織・メンバーの参照、出退勤の共有、タイムカード、承認フロー等を本人の権限の範囲で操作できる。

  • Zero-install remote MCP server for proof-of-existence file attestation.

  • Returns the entry/visa options for a traveller of a given nationality (passport) going to a destination for a stated purpose and length of stay. Each option includes: visa/permit type, whether a visa is required, maximum stay, whether remote/on-site work is allowed, cost, processing time, and application/renewal notes — sourced from official immigration authorities. Use this for "what visa do I need / can I stay N days / can I work remotely here". To count days already spent against the 90/180 limit use departi_track_schengen; for the tax consequences of staying use departi_check_tax. Tip: nationality should be the traveller's most favorable passport — multi-nationals may have better entry on one passport.
    Connector
  • Get the available services, prices, durations, and bookable staff or resources for a specific Korean beauty or wellness shop. Use this after finding a shop when service details, prices, durations, staff, or resources are needed before checking appointment availability. Pass lang to receive the content translated into the customer's language.
    Connector
  • Live-inspect one active, provider-verified, operator-curated public MCP server from the 404.directory catalog. Returns only the remote read-only tools approved for gateway execution, including their current descriptions, JSON input schemas, and annotations. Use after search_tools and before the first invoke_registered_tool call, or whenever arguments may have changed. This operation does not execute a remote business tool.
    Connector
  • Optimize an image: smart lossy compression (typically 60-80% size reduction), optional resize/upscale/format conversion, and AI-generated SEO metadata. Accepts absolute local file paths or remote URLs. In remote/API mode, only remote URLs are supported. Supported input formats: JPG, PNG, WebP, AVIF, GIF, SVG, ICO, HEIC, TIFF, BMP (max 50 MB). Supported output formats: JPG, PNG, WebP, AVIF, GIF, SVG, ICO. Each call costs 3 credits + 1 if SEO tags enabled. Animated GIFs are processed frame-by-frame (each frame optimized individually). Cost = frames × per-frame operations. Use confirm_gif_cost: true after reviewing the cost warning. Free tier: 20 credits/day, no signup. Log in with the login tool for more credits. Use status tool to check remaining credits before batch processing.
    Connector
  • For a Florida food truck or caterer checking their own record: what is currently limiting the VMScore letter grade, what to do about each item, official Florida DBPR resources, and a link to claim the free VenuMark vendor profile. Look up by license_number (MFD3953067 and 3953067 both work) or vendor_id from search_vendors. Organizers vetting a vendor for booking should use decide_vendor instead. Grades: A to F, plus HOLD (active DBPR license hold), Ungraded (insufficient record), and Withheld (license unconfirmed).
    Connector
  • START HERE with your research question. This is your step-by-step scientific METHOD guide: it works out what kind of research you're doing, hands you the concrete method one stage at a time, reviews each stage you submit (approves it or returns it for fixes), and controls what gets published. It DIRECTS your research process — it never does the work for you. (This guides HOW you conduct the work. It is NOT the tool for finding methods described in existing papers — for that, use the literature-search tools.)
    Connector
  • List interventions (the actions/fixes that were shipped) and report their measured outcomes. This is the SINGLE source of truth for 'did it work' — insights (findings) never carry a verdict. Use report: 'status' for a one-call picture of 'what fix-work is open' (due for check-in / in flight / recently closed + win rate — best for 'where did we get to?' / session start); report: 'list' (default) for the full rows; report: 'outcomes' for 'fixes that worked vs didn't' (buckets closed interventions by verdict + win rate). Filter by insightId to answer 'how did the fix(es) for this finding turn out?'. Each intervention includes baseline + post snapshots and computed deltas (when closed).
    Connector
  • Close a Pathrule refresh task after reviewing its brief. Normal remote flow: call pathrule_list_pending_refreshes, then pathrule_get_refresh_brief, then use this tool with status='rejected' when the signal is stale or not actionable. Remote MCP may refuse status='applied' because it cannot verify local source files; use Pathrule Studio/CLI for applied resolutions that require local verification.
    Connector
  • Read a resource by its URI. For static resources, provide the exact URI. For templated resources, provide the URI with template parameters filled in. Returns the resource content as a string. Binary content is base64-encoded.
    Connector
  • Push local facts to a remote memory instance. Private facts and sensitive entity prefixes (finance:, health:, credentials:, etc.) are never pushed. Call without confirm=true for a preview. Requires established passport tier (100+ receipts).
    Connector
  • Register as a new agent on Agoragentic. Returns an API key and access to the router-facing authenticated surfaces. If this MCP session is not yet authenticated, the new key is bound to the current session automatically, so authenticated tools work on your very next call. An already-authenticated session keeps its existing key. Persist the key for future sessions — stdio relay: set AGORAGENTIC_API_KEY; remote HTTP: send Authorization: Bearer <key> at initialize, or pass _meta.apiKey per tools/call.
    Connector
  • Search academic papers, books, and datasets via Crossref. For "search works titled X" / finding a SPECIFIC paper by its title, pass `title` (title-scoped — ranks the exact paper first). Beyond keyword search you can SORT by citation count or publication date and FILTER by date range, work type, and author — e.g. "most-cited papers on transformers" (sort=citations), "papers on LLMs since 2024" (from_date=2024-01-01), "recent journal articles by an author". Returns titles, authors, journal, DOIs, citation counts, and dates.
    Connector
  • Search curated AI/ML engineering roles for free. Filter by tags (e.g. llm, pytorch), workplace (remote/hybrid/onsite), global remote eligibility, experience level, salary range, or keyword. After selecting a role, candidates may use compile_job_specific_resume for a $0 transient ATS-oriented preview without identity; a verified key is required only to save an approval-bound artifact. The employer outcome pilot never affects organic results.
    Connector