Skip to main content
Glama
deenesjakoruzh
jjfisherdev

@firsthandapi/mcp-server

by jjfisherdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

@firsthandapi/mcp-server — FirstHandAPI MCP 서버

에이전트를 위한 Zero-to-job (부트스트랩 모드)

아직 API 키가 없으신가요? 그래도 서버를 시작할 수 있습니다 — 단일 signup 도구만 노출됩니다:

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

org_name과 email로 signup을 호출하면 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 평가를 위한 ground truth 데이터, 멀티모달 모델을 위한 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

다운로드 URL이 포함된 승인된 파일 가져오기

get_credits

크레딧 잔액 확인

모든 작업 생성 도구는 선택적 location 매개변수를 허용합니다: 텍스트 기반의 경우 { city, state }, 좌표 기반 제약 조건의 경우 { latitude, longitude, radius_km }.

환경 변수

  • FIRSTHAND_API_KEY (필수) — API 키

  • FIRSTHAND_BASE_URL (선택) — API 기본 URL (기본값: 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