GigHQ.ai
v1.0.0Job-search tracker for AI agents: applications, stale follow-ups, skills gaps, H-1B lookup.
Endpoint health
online- Last checked
- 11/20/2026, 6:17:38 AM
- Latency
- 72 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:ai.gighq%2Fgighq
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"ai.gighq/gighq": {
"url": "https://mcp.gighq.ai/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
25 shown · authentication unknown
add_career_entry
Saves a new career journal entry to the user's GigHQ profile. Use this to document professional achievements, projects, skills acquired, or reflections tied to a specific role. Entry types: 1 = achievement — a concrete win, result, or impact (default) 2 = project — a specific initiative the user owned or contributed to 3 = skill_acquired — a new skill, tool, or capability gained 4 = reflection — a lesson learned or professional observation Tip: if the user hasn't specified a role, call `list_experiences` first, present the options, and ask which role this entry belongs to. Then pass the confirmed integer ID as `experience_id`. experience_id is optional — entries without one are valid but less useful for resume generation and interview prep, since they can't be linked to a specific role. STAR structure (achievement entries): walk the user through their story in order, one piece at a time — don't interrogate with a checklist — Situation: the context or challenge beforehand Task: what specifically needed to be done or the goal to achieve Action: the concrete steps actually taken Result: the outcome, ideally with (1) scale of action: how much, how many, what scope (team size, users, codebase size, budget, requests/sec, etc.), (2) direct result: the measurable outcome (latency reduced by X%, errors down by Y, shipped Z weeks ahead of schedule), and (3) organizational impact: what that result meant for the business, team, or users (saved $X, unblocked N engineers, contributed to Y% revenue growth) Write `description` as a clearly labeled STAR narrative — "Situation: ... Task: ... Action: ... Result: ..." — rather than one unstructured paragraph. Before calling this tool for an achievement entry, confirm you have all four STAR parts from the user. If the Result's numbers are genuinely unavailable, note that in the description and ask the user to follow up later via update_career_entry. Project entries benefit from the same Result-quantification numbers but don't need the full STAR narrative structure. Put the quantified numbers from Result in the `metrics` field as well — not buried only in the description.
Schema valid · SHA-256 1c1b8d2fa742…
View input schema
Connections
streamable-http
https://mcp.gighq.ai/mcp