An MCP Server for computer-use in Windows OS
Kariaa is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Find jobs worldwide, check posts for scams, see typical pay, and apply to DataHouse remote tasks.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http kariaa-mcp https://agent.kariaa.com/mcp
# 2 — ask your agent for something these tools do
# list_tasks, get_task, whoami and 16 more
Kariaa costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http kariaa-mcp https://agent.kariaa.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
19 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
The open DataHouse tasks: title, kind (video, photo, voice, text), the unpaid verification sample each wants and the rate paid work earns after verification. No key needed. Filter by file kind.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | no | Only tasks that take this file kind |
| limit | integer | no | Default 25 |
One task in full: description, the task's own material (instructions: the sentences to read, texts to label, answers to rate), the unpaid verification sample with how-to steps and rules, allowed file kinds, the qualification questions (with ids, for apply_to_task) and the rate paid work earns after verification.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_id | string | yes | — |
The account behind the key, whether the basics a task needs are in (legal name, phone, location, occupation), and today's usage.
No parameter schema on file.
Save the basics a task needs: legal first and last name, phone in E.164 (+1…), location as "City, Country", occupation (one to five titles, "student" is fine), language.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| legal_first_name | string | no | — |
| legal_last_name | string | no | — |
| phone_number | string | no | — |
| location | string | no | — |
| occupation | array | no | — |
| language | string | no | — |
| string | no | — |
Join a DataHouse task for the person. answers maps each question id from get_task to the answer (a string, or a list for multiselect); every required question needs one. Optional preferred rate in their words ("$2 per clip"). One application per task; a task with a sample unlocks its sample step at once.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_id | string | yes | — |
| answers | object | no | — |
| preferred_rate | string | no | — |
| note | string | no | — |
A one-time signed URL for ONE sample file of a task the person joined. PUT the raw bytes to upload_url with the returned headers, then call confirm_upload with the path. Kind must match the task; up to 100 MB; up to 10 files per task.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| submission_id | string | yes | — |
| filename | string | yes | — |
| mime_type | string | yes | — |
| size_bytes | integer | yes | — |
After the PUT: register the object at path as a sample of the task. Returns how many samples are in and how many the task wants.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| submission_id | string | yes | — |
| path | string | yes | — |
Take back one staged sample (a wrong or bad file) so another can be uploaded in its place. Only before submit_samples. file_id comes from confirm_upload, get_submission or my_submissions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| submission_id | string | yes | — |
| file_id | string | yes | — |
A one-tap link to this task's upload page on kariaa.com, already signed in, where the person picks their photos, voice notes or videos from their phone or computer. Use it whenever you cannot send the file bytes yourself (chat apps). The link works once, for 15 minutes; give it to the person as is.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| submission_id | string | yes | — |
For a text task: the person's written answer (20 to 20,000 characters), stored as a .txt sample.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| submission_id | string | yes | — |
| text | string | yes | — |
| filename | string | no | — |
Send the staged samples of a task for review. Needs every sample the task asks for. Optional text_response for notes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| submission_id | string | yes | — |
| text_response | string | no | — |
Every DataHouse task the person joined, newest first, with its stage (pending_review, sample_needed, in_review, approved, rejected).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
One task the person joined: stage, staged files, review outcome and the next step.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| submission_id | string | yes | — |
Live job openings for a role, near a place or remote, from job boards (LinkedIn, Indeed, Glassdoor, ZipRecruiter, national boards) and remote-job sites, newest relevant first, with links to apply on the employer's page. Works without a key. Pass the role as people say it ("electrician", "nurse", "data analyst") and the place as "City, Country".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| role | string | yes | The job title or kind of work |
| location | string | no | "City, Country" or a country; leave out for anywhere |
| remote | boolean | no | Only remote jobs |
| limit | integer | no | Default 10 |
One job from search_jobs in full: description, requirements, pay when stated, posted date and the link to apply. Use it to tailor a resume or cover letter to the posting.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | yes | — |
Warning signs in a job post, recruiter message or offer (fees, upfront payments, personal email domains, link shorteners, pressure, requests for ID or bank details), each with the exact quoted line. Rule-based. Pass the text in English; translate it first if needed, keeping amounts, links, phone numbers and emails exactly as written.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | The full post or message, in English |
What employers state for a role in a city or country, from recent postings that list pay: the typical range, how many postings it comes from, and examples with links. When there are too few, say so and research further yourself.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| role | string | yes | — |
| location | string | yes | "City, Country" or a country |
Keep a job from search_jobs on the person's Kariaa list to come back to. Needs a Kariaa API key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | yes | — |
The jobs the person saved, newest first, with whether each is still open. Needs a Kariaa API key.
No parameter schema on file.
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Kariaa or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_tasks | no tags | |
| get_task | no tags | |
| whoami | no tags | |
| update_profile | state-write | state-write: declares readOnlyHint: false |
| apply_to_task | state-write | state-write: declares readOnlyHint: false |
| request_upload | state-write | state-write: declares readOnlyHint: false |
| confirm_upload | state-write | state-write: declares readOnlyHint: false |
| remove_sample | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| get_upload_link | state-write | state-write: declares readOnlyHint: false |
| add_text_sample | state-write | state-write: declares readOnlyHint: false |
| submit_samples | state-write | state-write: declares readOnlyHint: false |
| my_submissions | no tags | |
| get_submission | no tags | |
| search_jobs | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_job | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| check_job_post | no tags | |
| estimate_pay | no tags | |
| save_job | state-write | state-write: declares readOnlyHint: false |
| my_saved_jobs | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Kariaa can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.