INDIVIDUAL MCP TOOL
estimate_pay
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.
LIVE ENDPOINT
https://agent.kariaa.com/mcp
Connect to this endpoint to inspect the live schema for estimate_pay and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Potential side effects detected · medium confidence · heuristic, not a guarantee.
- A tool name or description suggests a financial action.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.kariaa-datahouse]
url = "https://agent.kariaa.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"kariaa-datahouse": {
"type": "http",
"url": "https://agent.kariaa.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: kariaa-datahouse
Remote MCP URL: https://agent.kariaa.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"kariaa-datahouse": {
"url": "https://agent.kariaa.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"kariaa-datahouse": {
"type": "http",
"url": "https://agent.kariaa.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "kariaa-datahouse",
"transport": "streamable-http",
"url": "https://agent.kariaa.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
list_tasks— The open DataHouse tasks: title, kind (video, photo, voice, text), the unpaid verification sample each wants and the rate paid work earns after verification.get_task— 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.whoami— The account behind the key, whether the basics a task needs are in (legal name, phone, location, occupation), and today's usage.update_profile— Save the basics a task needs: legal first and last name, phone in E.apply_to_task— Join a DataHouse task for the person.request_upload— A one-time signed URL for ONE sample file of a task the person joined.confirm_upload— After the PUT: register the object at `path` as a sample of the task.remove_sample— Take back one staged sample (a wrong or bad file) so another can be uploaded in its place.