Kariaa
REMOTE · AGENT.KARIAA.COM · 2 COMPONENTS
Find jobs worldwide, check posts for scams, see typical pay, and apply to DataHouse remote tasks.
Available components
Last scanned (6 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (remove_sample). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2095 tokens (~95/item across 22 items; 21 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 26% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety92
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 2 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "estimate_pay" implies "pay" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 0
- Tool coverage: 21% → 26% ▲ functional
- New tool “my_earnings” functional
- New tool “request_payout” functional
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://agent.kariaa.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agent.kariaa.com | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 11 Oct 2026 | 11 Apr 2027 | RSA 2048 | SHA256-RSA | bf48d663535ec722b73f8abf2f484de |
| SANs: agent.kariaa.com | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
| CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 1 Aug 2013 | 15 Jan 2038 | RSA 2048 | SHA256-RSA | 33af1e6a711a9a0bb2864b11d09fae5 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agent.kariaa.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| kariaa.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agent.kariaa.com/mcp | Verified | 200 | |
| http (plaintext) | http://agent.kariaa.com/mcp | HTTPS enforced | 301 | https://agent.kariaa.com/mcp |
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 →
add_text_sample Add a written answer ~56
For a text task: the person's written answer (20 to 20,000 characters), stored as a .txt sample.
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | – | – |
| submission_id | string | yes | – |
| text | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| file | – | – | The stored answer |
| ready_to_submit | – | – | All samples in |
| received | – | – | Samples in |
| wanted | – | – | Samples the task needs |
No examples provided.
apply_to_task Apply to a task ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | – | – |
| note | string | – | – |
| preferred_rate | string | – | – |
| task_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| already_applied | – | – | True when it existed |
| next | – | – | The next tool |
| sample_requirements | – | – | What to send |
| stage | – | – | sample_needed or pending_review |
| submission_id | – | – | The application |
No examples provided.
check_job_post Check a job post or offer for scam signs ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The full post or message, in English |
| Name | Type | Req | Description |
|---|---|---|---|
| risk | – | – | low, elevated or high |
| signals | – | – | Warning signs, each with the quoted evidence |
| translate_first | – | – | True when the post must be translated to English first |
No examples provided.
confirm_upload Confirm an uploaded sample ~54
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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
| submission_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| file | – | – | The registered sample |
| ready_to_submit | – | – | All samples in |
| received | – | – | Samples in |
| wanted | – | – | Samples the task needs |
No examples provided.
estimate_pay Pay for a role in a place ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | yes | "City, Country" or a country |
| role | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| currency | – | – | Currency |
| examples | – | – | Postings with stated pay and links |
| period | – | – | hour, month or year |
| postings | – | – | Postings the range comes from |
| typical_high | – | – | 75th percentile of the high ends |
| typical_low | – | – | 25th percentile of the low ends |
No examples provided.
get_job Open a job ~53
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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| company | – | – | Employer |
| description | – | – | The posting |
| how_to_apply | – | – | How to apply |
| job_id | – | – | Job id |
| pay | – | – | Pay when stated |
| requirements | – | – | Requirements |
| title | – | – | Title |
| url | – | – | Where to apply |
No examples provided.
get_submission Get a submission ~34
One task the person joined: stage, staged files, review outcome and the next step.
| Name | Type | Req | Description |
|---|---|---|---|
| submission_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| next | – | – | What to do next |
| stage | – | – | Where it stands |
| submission_id | – | – | The application |
No examples provided.
get_task Get a DataHouse task ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| instructions | – | – | The task's own material: sentences to read, texts to label, answers to rate |
| next | – | – | The next tool |
| pay | – | – | Rate for paid work after verification |
| program_rules | – | – | Rules for every task |
| qualification_questions | – | – | Questions to answer in apply_to_task, with ids |
| rules | – | – | Task rules |
| sample | – | – | The unpaid verification sample: count, instructions, how_to, looks_like |
| task_id | – | – | Task id |
| title | – | – | Title |
No examples provided.
get_upload_link Get a link to upload samples from a phone ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| submission_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| expires_in_minutes | – | – | Link lifetime |
| signed_in | – | – | Whether the link signs the person in |
| url | – | – | One-tap upload page link |
No examples provided.
list_tasks List DataHouse tasks ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Only tasks that take this file kind |
| limit | integer | – | Default 25 |
| Name | Type | Req | Description |
|---|---|---|---|
| count | – | – | How many |
| signed_in | – | – | Whether a key was sent |
| tasks | – | – | Open DataHouse tasks: task_id, title, summary, sample, pay, allowed_file_kinds, url |
No examples provided.
my_earnings My earnings ~32
The signed-in person's Kariaa balance, earnings, and payout requests. Platform earnings stay on those platforms.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| balance | – | – | Current payable balance: amount and currency |
| entries | – | – | Recent ledger credits |
| methods | – | – | Supported payout methods: paypal, venmo, giftcard, crypto |
| min_payout | – | – | Minimum balance required to request a payout |
| payouts | – | – | Recent payout requests |
| pending | – | – | Amount currently in an open payout request |
| total_earned | – | – | Lifetime earned: amount and currency |
No examples provided.
my_saved_jobs My saved jobs ~33
The jobs the person saved, newest first, with whether each is still open. Needs a Kariaa API key.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| count | – | – | How many |
| jobs | – | – | Saved jobs, newest first, with whether each is still open |
No examples provided.
my_submissions My submissions ~44
Every DataHouse task the person joined, newest first, with its stage (pending_review, sample_needed, in_review, approved, rejected).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| submissions | – | – | Each task joined, with stage and samples |
No examples provided.
remove_sample Remove a sample before submitting ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| file_id | string | yes | – |
| submission_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| received | – | – | Samples in |
| removed | – | – | The sample taken back |
| wanted | – | – | Samples the task needs |
No examples provided.
request_payout Request a payout ~102
Ask Kariaa to pay the whole balance. Methods: paypal, venmo, giftcard, crypto. An admin sends the money. One open request at a time, minimum 10.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Omit, or pass the whole balance. |
| destination | string | – | Must match the destination saved on the profile. |
| method | string | yes | paypal, venmo, giftcard, or crypto |
| note | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| amount | – | – | Amount requested |
| currency | – | – | Currency |
| destination | – | – | Where the payout will be sent |
| method | – | – | paypal, venmo, giftcard, or crypto |
| note | – | – | Optional note |
| payout_id | – | – | The created payout request id |
| requested_at | – | – | When requested |
| status | – | – | requested |
No examples provided.
request_upload Request a sample upload URL ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | yes | – |
| mime_type | string | yes | – |
| size_bytes | integer | yes | – |
| submission_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| expires_in_seconds | – | – | URL lifetime |
| headers | – | – | Headers for the PUT |
| path | – | – | Pass to confirm_upload |
| upload_url | – | – | Signed URL to PUT the bytes to |
No examples provided.
save_job Save a job ~42
Keep a job from search_jobs on the person's Kariaa list to come back to. Needs a Kariaa API key.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | – | – | Job id |
| saved | – | – | True when on the list |
| saved_count | – | – | Saved jobs |
No examples provided.
search_jobs Search jobs ~146
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".
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Default 10 |
| location | string | – | "City, Country" or a country; leave out for anywhere |
| remote | boolean | – | Only remote jobs |
| role | string | yes | The job title or kind of work |
| Name | Type | Req | Description |
|---|---|---|---|
| count | – | – | How many |
| jobs | – | – | Openings: job_id, title, company, location, work_type, pay, posted, url, source, match |
| location | – | – | Place searched |
| more_pending | – | – | True while more boards are still being searched; the same search shortly after adds them |
| role | – | – | Role searched |
No examples provided.
submit_samples Submit the samples ~48
Send the staged samples of a task for review. Needs every sample the task asks for. Optional text_response for notes.
| Name | Type | Req | Description |
|---|---|---|---|
| submission_id | string | yes | – |
| text_response | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| files_count | – | – | Files sent |
| submitted | – | – | True when sent for review |
| submitted_at | – | – | When |
No examples provided.
update_profile Update profile basics ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | – | |
| language | string | – | – |
| legal_first_name | string | – | – |
| legal_last_name | string | – | – |
| location | string | – | – |
| occupation | array | – | – |
| phone_number | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| missing | – | – | Still missing |
| ready_to_apply | – | – | Basics complete |
| rejected | – | – | Fields refused, with the reason |
| saved | – | – | Fields saved |
No examples provided.
whoami Who am I ~36
The account behind the key, whether the basics a task needs are in (legal name, phone, location, occupation), and today's usage.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| missing | – | – | Basics still missing |
| profile | – | – | Basics on file |
| quota | – | – | Today's usage |
| ready_to_apply | – | – | Whether the basics are complete |
| signed_in | – | – | Whether a valid key was sent |
No examples provided.
How do I install the Kariaa MCP server?
Kariaa is a hosted endpoint at https://agent.kariaa.com/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 · agent.kariaa.com
claude mcp add --transport http com-kariaa-mcp 'https://agent.kariaa.com/mcp'
What is the Kariaa MCP server?
Kariaa is an MCP server listed in the public MCP registry as com.kariaa/mcp. Find jobs worldwide, check posts for scams, see typical pay, and apply to DataHouse remote tasks. This page covers its hosted endpoint (https://agent.kariaa.com/mcp).
Is the Kariaa MCP server safe to use?
Kariaa scores 72 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 Kariaa MCP server expose?
Kariaa exposes 21 tools: list_tasks, get_task, whoami, update_profile, apply_to_task, and 16 more. Their descriptions and schemas cost roughly 1,464 tokens of context every time the server is loaded.
Does the Kariaa MCP server require authentication?
No. We connected to Kariaa without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Kariaa MCP server still maintained?
Kariaa is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.