Skip to main content
Glama
deenesjakoruzh
jjfisherdev

@firsthandapi/mcp-server

by jjfisherdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

@firsthandapi/mcp-server — FirstHandAPI MCP 服务器

从零到上岗（引导模式）

还没有 API 密钥？照样可以启动服务器——它会暴露一个 signup 工具：

npx @firsthandapi/mcp-server        # no env var needed

调用 signup 并传入 org_name 和 email，即可获得 API 密钥和 $2.50 的免费额度（密钥只显示一次——请保存好），然后配置好密钥重新启动：

claude mcp add firsthandapi -e FIRSTHAND_API_KEY=fh_live_... -- npx @firsthandapi/mcp-server

配置好密钥后，全部 7 个任务工具即可解锁：create_job、create_job_and_wait、get_job、list_jobs、get_job_files、cancel_job、get_credits。

FirstHandAPI 的官方 MCP 服务器——人机协同（HITL）众包数据采集。让 Claude Code、Cursor 及其他 AI 代理能够从真实人类工作者那里采集照片、音频、视频和屏幕录制，并带有自动化 AI 质量评分。

适用场景：UGC 采集、用于 AI 评估的真实数据、多模态模型的 LLM 训练数据。

Related MCP server: simple-fal-mcp

安装

npm install @firsthandapi/mcp-server

配置

Claude Code

{
  "mcpServers": {
    "firsthand": {
      "command": "npx",
      "args": ["@firsthandapi/mcp-server"],
      "env": {
        "FIRSTHAND_API_KEY": "fh_live_your_key_here"
      }
    }
  }
}

Cursor

添加到 .cursor/mcp.json：

{
  "firsthand": {
    "command": "npx @firsthandapi/mcp-server",
    "env": { "FIRSTHAND_API_KEY": "fh_live_..." }
  }
}

工具

工具

描述

create_job

发布内容采集任务

get_job

获取任务状态和详情

create_job_and_wait

发布任务并等待完成

list_jobs

列出所有任务（支持筛选）

cancel_job

取消一个进行中的任务

get_job_files

获取已批准的文件及下载链接

get_credits

查看账户余额

所有任务创建工具都接受一个可选的 location 参数：基于文本的 { city, state } 或基于坐标的 { latitude, longitude, radius_km } 约束。

环境变量

  • FIRSTHAND_API_KEY（必填）——你的 API 密钥

  • FIRSTHAND_BASE_URL（可选）——API 基础地址（默认：https://api.firsthandapi.com）

  • FIRSTHAND_TIMEOUT_MS（可选）——请求超时时间（默认：30000）

许可证

专有

Available Tools

1 tool
signupA

Create a FirstHandAPI buyer account and receive an API key plus $2.50 in free credits. Use this when the server is running without FIRSTHAND_API_KEY. The key is shown ONCE — store it, then restart the MCP server with FIRSTHAND_API_KEY set to unlock the job tools.

ParametersJSON Schema
NameRequiredDescriptionDefault
emailYesContact email for the account (must not be a disposable address)
org_nameYesOrganization or project name

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It discloses the critical behavioral trait that the API key is shown only once and that the server must be restarted with FIRSTHAND_API_KEY. It does not cover failure modes or response details, but the most important operational quirk is clearly communicated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences with no filler. It front-loads the action and outcome, then adds necessary operational guidance. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter setup tool with no output schema, the description covers the purpose, the trigger condition, and the critical one-time-key warning. It could be slightly more explicit about the response format, but the operational guidance is strong enough to make the tool usable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with both email and org_name already described in the input schema. The tool description adds no parameter-specific meaning beyond the schema, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Create') with a clear resource ('FirstHandAPI buyer account') and states concrete outcomes (API key plus $2.50 in credits). This makes the tool's function unmistakable even without sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use the tool: 'when the server is running without FIRSTHAND_API_KEY.' It also provides clear follow-up steps (store the key, restart the MCP server, set the env var) and explains the purpose ('unlock the job tools').

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev0.2.0
    • First observedsignup
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.1/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusion or overlap. Its purpose is clearly defined as account creation and API key retrieval.

Naming Consistency5/5

With a single tool, naming is perfectly consistent by definition. The verb-form 'signup' is clear and unambiguous, even if it doesn't follow a verb_noun pattern.

Tool Count2/5

The server's own description mentions 'job tools' that will be unlocked after restart, yet only signup is exposed. A single tool is too few for the apparent broader API scope, making the tool set feel thin and incomplete.

Completeness1/5

The server is described as a FirstHandAPI MCP server with the intent to provide job tools, but only signup is available. This creates a severe gap—users can create an account but cannot perform any actual job operations, leaving the advertised surface almost entirely absent.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • instruckt-mcp

    tdwesten
    A
    license
    A
    quality
    B
    maintenance
    MCP server for instruckt visual annotations. Enables AI agents to retrieve pending annotations, view screenshots, and resolve annotations.
    3
    21 npm
    MIT

  • agenhire

    tonypk
    A
    license
    Not graded
    quality
    D
    maintenance
    MCP server for AgentHire, an AI talent marketplace enabling agents to browse jobs, apply, manage interviews, and handle offers. Supports employer job creation, candidate matching, and compliance tips.
    6 npm
    MIT