A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Nothing to run from here
GigHQ.ai is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
34
tools declared
remote
at its publisher
—
calls last 7d
What it does
Job-search tracker for AI agents: applications, stale follow-ups, skills gaps, H-1B lookup.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http gighq-ai-mcp https://mcp.gighq.ai/mcp
# 2 — ask your agent for something these tools do
# search_companies, get_company_details, get_job_details and 31 more
GigHQ.ai costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
GIAll 1 server
gighq1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http gighq-ai-mcp https://mcp.gighq.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
34 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search for companies by name to retrieve their unique identifiers (UUIDs).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The name of the company to search for (e.g., 'Human') |
Get detailed information about a company (applicants by status, Community Signal, H1B sponsorship status, employee count, website, etc.) using its UUID. The metrics window defaults to the last 30 days. Optional startDate and endDate parameters support other date ranges. Returns GigHQ's recorded company data and community metrics for the selected window.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| companyId | string | yes | The UUID for the company (obtain from search_companies), or a plain company name — the tool will auto-resolve a name to a UUID if a valid UUID is not provided. |
| startDate | string | no | Start of the metrics window in ISO 8601 format (YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS). Compute this from natural-language ranges: 'last 6 months' → today minus 6 months, 'last year' → today minus 12 mont |
| endDate | string | no | End of the metrics window in ISO 8601 format. Defaults to today if omitted. |
Get detailed community metrics for a specific job listing (applicants by status, average days per status, Community Signal) using its UUID. The metrics window defaults to the last 30 days. When the user requests a longer period — e.g. "last 6 months", "last year", "since January" — compute startDate and endDate from that phrase and pass them explicitly.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | string | yes | The unique identifier (UUID) for the job listing. |
| startDate | string | no | Start of the metrics window in ISO 8601 format (YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS). Compute from natural-language ranges: 'last 6 months' → today minus 6 months, 'last year' → today minus 12 months. D |
| endDate | string | no | End of the metrics window in ISO 8601 format. Defaults to today if omitted. |
STOP — if the user says "not interested", "no longer interested", "withdraw interest", "remove from pipeline", or any equivalent: do NOT call this tool. Call toggle_job_application_interest instead. There is no "not interested" status here; attempting to use REJECTED or any other status as a proxy is wrong. Updates the status of a job application by its UUID to one of the supported pipeline stage
| Parameter | Type | Required | Notes |
|---|---|---|---|
| uuid | string | yes | The UUID of the job application to update (the 'uuid' field, not the numeric 'id'). |
| currentStatus | string | yes | The current status of the job application (required to validate the transition). |
| status | string | yes | The new status for the job application. |
Use this tool when the user says "not interested", "no longer interested", "withdraw interest", "I'm out", "remove from pipeline", or any equivalent phrase. This is the ONLY correct tool for withdrawing interest — do not use update_job_application_status as a proxy. Deactivates an active application (or reactivates a previously deactivated one). Mirrors the "I am no longer interested in this role
| Parameter | Type | Required | Notes |
|---|---|---|---|
| uuid | string | yes | The UUID of the job application to update (the 'uuid' field, not the numeric 'id'). |
| currentIsActive | boolean | yes | The current active state of the application. Pass true if the application is currently active (this will deactivate it); pass false if it is currently inactive (this will reactivate it). Retrieve this |
Retrieves a summary of the user's 10 most recent job applications, including status, company name, and correspondence dates. totalCount in the response reflects the full number of applications, not just the 10 returned — mention it if it's larger than the list shown, and point the user to search_job_applications for the rest.
No parameter schema on file.
Search the user's job applications by company name, status, or both. Use this when the user asks about a specific company's application, wants to find a particular application to view or update its status, or wants to know how many applications are in a given status (e.g. "how many applications are in Prospecting?"). Omit company to search across all companies — required when the request is sta
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company | string | no | Company name to search for. Case-insensitive substring match. Omit to search across all companies. |
| status | string | no | Optional: filter results to a specific application status. |
| isActive | boolean | no | Default true (active applications only). Pass false to search applications marked 'no longer interested'. |
| take | integer | no | Max results to return (default 20, max 50). |
| skip | integer | no | Offset for pagination (default 0). |
Fetches the full details of a single job application by its UUID — status history, correspondence dates, job description, and related metadata. Do NOT use this tool when the user asks about notes ("do I have any notes", "show me my notes", "list notes"). Use list_job_application_notes for that. Tip: if you only have a company name, call search_job_applications first to get the UUID.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| uuid | string | yes | The UUID of the job application (the 'uuid' field, not the numeric 'id'). |
Creates a new job application entry in GigHQ, or reuses an existing active one for the same company+job if the backend finds one — check alreadyExist in the response. Calling find_job_application first is still recommended when you want to inspect a possible match before deciding. New applications always start in PROSPECTING status — there is no way to create directly into APPLIED/INTERVIEWING/
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company | string | yes | The name of the company you applied to. |
| job | string | yes | The job title or role you applied for. |
| source_url | string | no | The URL of the job posting, if known. Saved best-effort after create/find. |
| job_description | string | no | The full job description text, if known. Saved best-effort after create/find. |
Checks whether the user already has a saved job application for a SPECIFIC posting — call this before create_job_application to avoid creating a duplicate. Matches BOTH company name and job title (case-insensitive substring on each), so it can tell two different roles at the same company apart. search_job_applications cannot do this — it only filters by company/status/isActive, not job title. Bot
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company | string | yes | Company name to match (case-insensitive substring). |
| job | string | yes | Job title to match (case-insensitive substring). |
Enriches or corrects an existing job application's saved posting details: source URL and/or job description. Use this when the user finds the JD later, wants to add the posting link, or wants to correct the saved description. Do NOT use this for status changes — use update_job_application_status. Do NOT use this for withdraw/reactivate ('not interested') — use toggle_job_application_interest. Thi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| uuid | string | yes | The UUID of the job application to update. Find it with search_job_applications, find_job_application, or get_recent_applications. |
| source_url | string | no | The URL of the job posting. |
| job_description | string | no | The full job description text. Replaces any previously saved description for this application. |
Looks up a company by name and returns GigHQ's recorded H1B sponsorship and concurrent H1B flags. Returns unknown when a flag is unavailable. These results describe the data recorded in GigHQ.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company_name | string | yes | The name of the company to look up (e.g., 'Google'). |
Returns job applications that haven't had a status update in a configurable number of days, along with a suggested follow-up action for each. Useful for surfacing applications the user may have forgotten about.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | Number of days without a status change before an application is considered stale. Defaults to 14. |
Generates a weekly job search health summary. Aggregates up to 30 active applications and surfaces status distribution, conversion rates, longest-open applications, pipeline clustering insights, and a suggested focus area for the coming week.
No parameter schema on file.
Retrieves a saved GigHQ job application, candidate profile data, and the most relevant Career Journal evidence for assessing role fit. Career evidence is ranked by job keywords, competency coverage, evidence quality, recency, and diversity; the default is 20 entries, grouped by competency bucket (career_journal.competency_rollup) to make coverage and gaps easy to spot. This read-only tool supplies
| Parameter | Type | Required | Notes |
|---|---|---|---|
| application_uuid | string | yes | UUID of the saved GigHQ job application. |
| career_entry_limit | integer | no | Maximum Career Journal entries to return (default 20, max 50). |
Assembles everything needed to prepare for an interview on a saved GigHQ job application: the job and company context, the candidate's full profile, their Career Journal grouped by role (for STAR/CAR story material), which evidence best matches the role (to emphasize) and which competencies are weakly covered (to address or reframe), and a company briefing (Community Signal, H1B status, size). Thi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| application_uuid | string | yes | UUID of the saved GigHQ job application to prepare for. |
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 = refle
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | Short headline summarising the entry (e.g. 'Led migration of payments service to microservices'). |
| description | string | yes | Full narrative in the user's own words. For achievement entries, write it as a labeled STAR narrative — "Situation: ... Task: ... Action: ... Result: ..." — not one unstructured paragraph. For other t |
| type | integer | no | Entry type: 1=achievement, 2=project, 3=skill_acquired, 4=reflection. Pass an integer or the label string. Defaults to 1. |
| experience_id | integer | no | Integer ID of the GigHQ experience record (role) this entry belongs to. Use list_career_entries or the gighq://experience resource to find the ID. |
| entry_date | string | no | ISO 8601 date when this happened, e.g. '2024-03-15'. Defaults to today if omitted. |
| metrics | string | no | Three-number quantification: (1) scale of action, (2) direct result, (3) organizational impact. E.g. 'Serving 50k daily users [scale] — reduced checkout latency from 2.1s to 0.4s [result] — increased |
| tags | string | no | Comma-separated skill or topic tags, e.g. 'TypeScript, system design, stakeholder management'. |
Updates an existing career journal entry. Only the fields provided will be changed — all other fields remain as-is. Use this to refine descriptions, add missing numbers to the metrics field, correct the entry date, or re-type an entry. This is the right tool to backfill quantification on entries saved without a full three-number breakdown (scale of action, direct result, organizational impact).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| uuid | string | yes | UUID of the career entry to update. Returned by add_career_entry or list_career_entries. |
| title | string | no | Updated headline for the entry. |
| description | string | no | Updated narrative text. |
| type | integer | no | Updated type: 1=achievement, 2=project, 3=skill_acquired, 4=reflection. Pass an integer or the label string. |
| experience_id | integer | no | Updated experience (role) ID to attach this entry to. |
| entry_date | string | no | Updated ISO 8601 date, e.g. '2024-06-01'. |
| metrics | string | no | Updated quantifiable impact using the three-number rule: (1) scale of action, (2) direct result, (3) organizational impact. Use this to backfill missing numbers on entries that were saved without them |
| tags | string | no | Updated comma-separated tags. |
Returns the user's career journal entries from GigHQ, newest first. Supports optional filtering by entry type and date range. Use this tool to: - Review what the user has already documented before starting a journaling session - Find entries to update or refine - Identify gaps (roles with few or no entries) - Synthesise entries into resume bullets or interview stories Entry type filter v
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | integer | no | Filter by entry type: 1=achievement, 2=project, 3=skill_acquired, 4=reflection. Omit for all types. |
| start_date | string | no | ISO 8601 start date to filter entries on or after, e.g. '2024-01-01'. |
| end_date | string | no | ISO 8601 end date to filter entries on or before, e.g. '2024-12-31'. |
| take | integer | no | Number of entries to return (default 25, max 100). |
| skip | integer | no | Number of entries to skip for pagination. |
Permanently deletes a career journal entry by UUID. This action cannot be undone — confirm with the user before calling. Use list_career_entries to find the UUID if you don't have it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| uuid | string | yes | UUID of the career entry to delete. Returned by add_career_entry or list_career_entries. |
Returns a set of context-aware reflection questions to guide a career journaling session. Use this at the start of any journaling conversation to orient the discussion. The tool reads the user's GigHQ experience records and existing career entries to tailor the questions — surfacing the most relevant role, estimating tenure, and flagging roles with sparse documentation. Session types: achievem
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_type | string | no | Type of journaling session. Defaults to 'quarterly'. |
Returns the user's work experience records with their integer IDs. Use this tool BEFORE calling add_career_entry or update_career_entry to find the correct experience_id for the role the entry belongs to. Present the role list to the user and confirm which one they mean before saving. This is the tool-based alternative to the gighq://experience resource and works in all contexts includin
No parameter schema on file.
Adds a note to a job application's timeline. Use this to log any touchpoint or interaction — a call, a LinkedIn message, a referral conversation, a networking event, etc. category is required. Infer the best-fit category from the note content before calling. Use this mapping: • text_message — contact via SMS/text • email_external — contact via email • call — phone or video call • link
| Parameter | Type | Required | Notes |
|---|---|---|---|
| application_id | string | yes | UUID of the job application to attach this note to. |
| body | string | yes | The note text (plain text or Markdown). Max 3000 characters. |
| category | string | yes | Category tag for the note. Use a slug from the tool description (e.g. 'call', 'in_person_meeting'). Display labels like 'Call' or 'In-Person Meeting' are also accepted. |
Use this tool when the user asks about notes on a job application — "do I have any notes", "show me my notes", "what notes do I have", etc. Returns all user-authored notes for a job application ordered by date, including UUID, body text, category, and timestamp. Use the returned UUIDs in follow-up update_job_application_note or delete_job_application_note calls.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| application_id | string | yes | UUID of the job application whose notes to retrieve. |
Updates the body or category of an existing job application note. Both body and category are required — the backend replaces the full note on update. If the user only mentions updating the body and doesn't specify a category, infer the best-fit category from the note content using this mapping: • text_message — contact via SMS/text • email_external — contact via email • call — phone or vide
| Parameter | Type | Required | Notes |
|---|---|---|---|
| note_uuid | string | yes | UUID of the note to update. Returned by add_job_application_note or list_job_application_notes. |
| application_id | string | yes | UUID of the job application this note belongs to. |
| body | string | yes | Updated note text. Max 3000 characters. |
| category | string | yes | Category tag for the note. Use a slug from the tool description (e.g. 'call', 'in_person_meeting'). Display labels like 'Call' or 'In-Person Meeting' are also accepted. |
Permanently deletes a note from a job application's timeline. This action cannot be undone — confirm with the user before calling. Use list_job_application_notes to find the note UUID if you don't have it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| note_uuid | string | yes | UUID of the note to delete. Returned by add_job_application_note or list_job_application_notes. |
| application_id | string | yes | UUID of the job application this note belongs to. |
Searches the user's job-search contacts in GigHQ — recruiters, hiring managers, referrals, and other people they are networking with. Use this tool to: - Find a contact before drafting an outreach or follow-up message - See who the user already knows at a company before an interview or application - Review which contacts are stuck at a given outreach stage Status filter values: not_contact
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | Filter by contact name (case-insensitive substring match). |
| status | string | no | Filter by outreach status. |
| take | integer | no | Number of contacts to return (default 25, max 100). |
| skip | integer | no | Number of contacts to skip for pagination. |
Returns full details for one of the user's job-search contacts: profile info, outreach status, linked job applications, and the complete interaction history (calls, LinkedIn messages, coffee chats, etc.). Use this before drafting outreach or follow-up messages so the message reflects what has already been said, and before interviews to remind the user who they know at the company. Find the UUID w
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact_id | string | yes | UUID of the contact. |
Updates a contact's outreach status in GigHQ. A status-change entry is automatically logged in the contact's interaction history. Status progression: not_contacted → reached_out → responded → in_conversation → connected. Use 'cold' when the thread has gone quiet. Find the contact's UUID with search_contacts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact_id | string | yes | UUID of the contact. |
| status | string | yes | New outreach status. |
Logs a touchpoint with one of the user's job-search contacts — a call, a LinkedIn message, a coffee chat, a referral conversation, etc. The entry appears in the contact's interaction timeline in GigHQ. type is required. Infer the best-fit type from what happened: • text_message — SMS/text • email_external — email • call — phone or video call • linkedin_connection_request — sent or acc
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact_id | string | yes | UUID of the contact. |
| type | string | yes | Kind of interaction being logged. |
| body | string | yes | Short note about the interaction — what was discussed or sent. Max 3000 characters. |
| occurred_at | string | no | ISO 8601 date the interaction happened, e.g. '2026-07-10'. Defaults to now. |
Retrieves the user's saved CareerCompass data: professional objectives, positioning statement, categorized skills (technical/soft/management/other), and target market (industries, company size, geographic location). Cheap read — prefer this over generate_career_compass whenever the user just wants to review what's already saved.
No parameter schema on file.
Runs GigHQ's CareerCompass AI pipeline against the user's resume data to generate 3 candidate professional objective statements, a positioning statement, categorized skills, and a suggested target market (industries, company sizes, geographic locations). This is an EXPENSIVE, one-time 'career strategy' action (4 parallel AI completions server-side) — not a cheap or repeatable lookup. Prefer get_ca
| Parameter | Type | Required | Notes |
|---|---|---|---|
| career_stage | string | no | The user's career stage, if known. Omit if not established in the conversation. |
| career_switch_details | object | no | Required for useful output when career_stage is 'Career Switcher'. |
Persists CareerCompass data to the user's GigHQ profile. This REPLACES the full saved record — any array field you omit (technical_skills, soft_skills, management_skills, target_industries, company_size, geographic_location, other_skills) is saved as empty, not left unchanged. Call get_career_compass first and pass through every field the user isn't changing. Only call this after the user has revi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| professional_objectives | string | no | The chosen professional objective statement. |
| positioning_statement | string | no | The chosen positioning statement. |
| technical_skills | array | no | Technical skills. Omitting this clears any previously saved technical skills. |
| soft_skills | array | no | Soft skills. Omitting this clears any previously saved soft skills. |
| management_skills | array | no | Management skills. Omitting this clears any previously saved management skills. |
| other_skills | array | no | Other skills. Omitting this clears any previously saved other skills. |
| target_industries | array | no | Target industries. Omitting this clears any previously saved target industries. |
| company_size | array | no | Target company sizes. Omitting this clears any previously saved company sizes. |
| geographic_location | array | no | Target geographic locations. Omitting this clears any previously saved locations. |
| career_stage | string | no | — |
| career_switch_type | string | no | — |
| target_industry | string | no | Single primary target industry, distinct from the target_industries list. |
| target_role | string | no | Single primary target role. |
| is_complete | boolean | no | Defaults to true server-side. Pass false only for an explicit partial/in-progress save. |
| progress_step | integer | no | Wizard step reached, for an in-progress save (is_complete: false). |
| objective_suggestions | array | no | The AI-generated objective candidates shown to the user, so a resumed session can show the same options. |
| target_job_titles | array | no | Up to 5 target job titles. |
Assembles the user's profile, experience, career journal evidence (with a broad competency rollup), and saved CareerCompass data (if any) for recommending role titles to target. This is the inverse of get_job_fit_evidence: instead of evaluating fit for one specific job, it starts from the candidate's profile. Role taxonomy only — it does NOT validate recommendations against live job-market demand
| Parameter | Type | Required | Notes |
|---|---|---|---|
| industry_preference | string | no | Industry the user wants to target, if stated. |
| seniority | string | no | Seniority level the user is targeting, if stated. |
| open_to_pivot | boolean | no | Whether the user is open to a role/industry pivot, if stated. |
| location_preference | string | no | Remote/hybrid/location preference, if stated. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install GigHQ.ai or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.0 · scanned 24 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest507244be29db4cb1dfdb689da3efa858153eb522b794584248c6e6f9541bfae7
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_companies | no tags | |
| get_company_details | no tags | |
| get_job_details | no tags | |
| update_job_application_status | state-write | state-write: declares readOnlyHint: false |
| toggle_job_application_interest | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| get_recent_applications | no tags | |
| search_job_applications | no tags | |
| get_job_application | no tags | |
| create_job_application | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| find_job_application | no tags | |
| update_job_application | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| lookup_h1b_sponsorship | no tags | |
| check_stale_applications | no tags | |
| weekly_job_search_summary | no tags | |
| get_job_fit_evidence | no tags | |
| prepare_for_interview | no tags | |
| add_career_entry | state-write | state-write: declares readOnlyHint: false |
| update_career_entry | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| list_career_entries | no tags | |
| delete_career_entry | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| get_career_journal_prompts | no tags | |
| list_experiences | no tags | |
| add_job_application_note | external-sinkstate-write | external-sink: keyword "sms"; state-write: declares readOnlyHint: false |
| list_job_application_notes | no tags | |
| update_job_application_note | external-sinkstate-write | external-sink: keyword "sms"; state-write: declares readOnlyHint: false, destructiveHint: true |
| delete_job_application_note | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| search_contacts | no tags | |
| get_contact | no tags | |
| update_contact_status | state-write | state-write: declares readOnlyHint: false |
| add_contact_interaction | external-sinkstate-write | external-sink: keyword "sms"; state-write: declares readOnlyHint: false |
| get_career_compass | no tags | |
| generate_career_compass | no tags | |
| save_career_compass | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| recommend_target_roles | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest507244be29db4cb1
Scanned2026-10-24
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish GigHQ.ai can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.