MCP servers › ai.gighq › gighq

MCP server · registry snapshot 2026-10-24 · last tested 2026-10-24

ai.gighq/gighq

Job-search tracker for AI agents: applications, stale follow-ups, skills gaps, H-1B lookup. — the publisher's description

4 of 4 record checks metRead-only · tools listed 2026-10-24version 1.0.0streamable HTTP34 tools

Summary

ai.gighq/gighq is a remote MCP server listed in the official MCP registry at version 1.0.0. On 2026-10-24 ProtocolProbe connected to it in read-only mode and read its inventory: 34 tools, 0 resources and 0 prompts.

Record checks

4 of 4 record checks met · 4 do not apply · 1 not checked

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not checked: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Repository: public
Tools: 34
Last tested: 2026-10-24

Add to your client

Observed fact

This server accepted a session without any credential and lists 13 tools whose name or declaration suggests they change data (update_job_application_status, toggle_job_application_interest, create_job_application, update_job_application, add_career_entry and 8 more). That is our reading of the names; we did not call them. Source: our connection, 2026-10-24.

How fresh this is

Live-tested: yes, a real session (not a text-only review)
Last tested: 2026-10-24
Mode: read-only (no tool calls)
Latest version: 1.0.0, published 2026-10-23 (registry, as of the 2026-10-24 snapshot)
First listed version: 2026-10-23 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-10-24
Package and repository: checked 2026-10-24
Engine: mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-23, listed on 2026-10-24 with version 1.0.0 (published 2026-10-23).

Source: the official MCP Registry list on 2026-10-23 and on 2026-10-24.

What it is

What does this server offer?

Observed inventory

34tools

0resources

0prompts

None of its 34 tools are described as changing anything. For 34 the reading was uncertain, so no mark is shown.

search_companieson 89 other servers
“Search for companies by name to retrieve their unique identifiers (UUIDs).”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
- namestringrequired“The name of the company to search for (e.g., 'Human')”
get_company_detailson 6 other servers
“Get detailed information about a company (applicants by status, Community Signal, H1B sponsorship status, employee count, website, etc.) using its UUID.”
Publisher declares: read-only yes · destructive no · open-world no
3 inputs, 1 required
- companyIdstringrequired“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.”
- startDatestring“Start of the metrics window in ISO 8601 format (YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS).”
- endDatestring“End of the metrics window in ISO 8601 format.”
get_job_detailson 12 other servers
“Get detailed community metrics for a specific job listing (applicants by status, average days per status, Community Signal) using its UUID.”
Publisher declares: read-only yes · destructive no · open-world no
3 inputs, 1 required
- jobIdstringrequired“The unique identifier (UUID) for the job listing.”
- startDatestring“Start of the metrics window in ISO 8601 format (YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS).”
- endDatestring“End of the metrics window in ISO 8601 format.”
update_job_application_status
“STOP — if the user says "not interested", "no longer interested", "withdraw interest", "remove from pipeline", or any equivalent: do NOT call this tool.”
Publisher declares: read-only no · destructive no · open-world no
3 inputs, 3 required
- uuidstringrequired“The UUID of the job application to update (the 'uuid' field, not the numeric 'id').”
- currentStatusstringrequired“The current status of the job application (required to validate the transition).”
- statusstringrequired“The new status for the job application.”
toggle_job_application_interest
“Use this tool when the user says "not interested", "no longer interested", "withdraw interest", "I'm out", "remove from pipeline", or any equivalent phrase.”
Publisher declares: read-only no · destructive yes · open-world no
2 inputs, 2 required
- uuidstringrequired“The UUID of the job application to update (the 'uuid' field, not the numeric 'id').”
- currentIsActivebooleanrequired“The current active state of the application.”
get_recent_applications
“Retrieves a summary of the user's 10 most recent job applications, including status, company name, and correspondence dates.”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
search_job_applications
“Search the user's job applications by company name, status, or both.”
Publisher declares: read-only yes · destructive no · open-world no
5 inputs
- companystring“Company name to search for.”
- statusstring“Optional: filter results to a specific application status.”
- isActiveboolean“Default true (active applications only).”
- takeinteger“Max results to return (default 20, max 50).”
- skipinteger“Offset for pagination (default 0).”
get_job_application
“Fetches the full details of a single job application by its UUID — status history, correspondence dates, job description, and related metadata.”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
- uuidstringrequired“The UUID of the job application (the 'uuid' field, not the numeric 'id').”
create_job_application
“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.”
Publisher declares: read-only no · destructive yes · open-world no
4 inputs, 2 required
- companystringrequired“The name of the company you applied to.”
- jobstringrequired“The job title or role you applied for.”
- source_urlstring“The URL of the job posting, if known.”
- job_descriptionstring“The full job description text, if known.”
find_job_application
“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.”
Publisher declares: read-only yes · destructive no · open-world no
2 inputs, 2 required
- companystringrequired“Company name to match (case-insensitive substring).”
- jobstringrequired“Job title to match (case-insensitive substring).”
update_job_application
“Enriches or corrects an existing job application's saved posting details: source URL and/or job description.”
Publisher declares: read-only no · destructive yes · open-world no
3 inputs, 1 required
- uuidstringrequired“The UUID of the job application to update.”
- source_urlstring“The URL of the job posting.”
- job_descriptionstring“The full job description text.”
lookup_h1b_sponsorship
“Looks up a company by name and returns GigHQ's recorded H1B sponsorship and concurrent H1B flags.”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
- company_namestringrequired“The name of the company to look up (e.g., 'Google').”

Show 22 more tools

check_stale_applications
“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.”
Publisher declares: read-only yes · destructive no · open-world no
1 input
- daysinteger“Number of days without a status change before an application is considered stale.”
weekly_job_search_summary
“Generates a weekly job search health summary.”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
get_job_fit_evidence
“Retrieves a saved GigHQ job application, candidate profile data, and the most relevant Career Journal evidence for assessing role fit.”
Publisher declares: read-only yes · destructive no · open-world no
2 inputs, 1 required
- application_uuidstringrequired“UUID of the saved GigHQ job application.”
- career_entry_limitinteger“Maximum Career Journal entries to return (default 20, max 50).”
prepare_for_interview
“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…”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
- application_uuidstringrequired“UUID of the saved GigHQ job application to prepare for.”
add_career_entry
“Saves a new career journal entry to the user's GigHQ profile.”
Publisher declares: read-only no · destructive no · open-world no
7 inputs, 2 required
- titlestringrequired“Short headline summarising the entry (e.g.”
- descriptionstringrequired“Full narrative in the user's own words.”
- typeinteger“Entry type: 1=achievement, 2=project, 3=skill_acquired, 4=reflection.”
- experience_idinteger“Integer ID of the GigHQ experience record (role) this entry belongs to.”
- entry_datestring“ISO 8601 date when this happened, e.g.”
- metricsstring“Three-number quantification: (1) scale of action, (2) direct result, (3) organizational impact.”
- tagsstring“Comma-separated skill or topic tags, e.g.”
update_career_entry
“Updates an existing career journal entry.”
Publisher declares: read-only no · destructive yes · open-world no
8 inputs, 1 required
- uuidstringrequired“UUID of the career entry to update.”
- titlestring“Updated headline for the entry.”
- descriptionstring“Updated narrative text.”
- typeinteger“Updated type: 1=achievement, 2=project, 3=skill_acquired, 4=reflection.”
- experience_idinteger“Updated experience (role) ID to attach this entry to.”
- entry_datestring“Updated ISO 8601 date, e.g.”
- metricsstring“Updated quantifiable impact using the three-number rule: (1) scale of action, (2) direct result, (3) organizational impact.”
- tagsstring“Updated comma-separated tags.”
list_career_entries
“Returns the user's career journal entries from GigHQ, newest first.”
Publisher declares: read-only yes · destructive no · open-world no
5 inputs
- typeinteger“Filter by entry type: 1=achievement, 2=project, 3=skill_acquired, 4=reflection.”
- start_datestring“ISO 8601 start date to filter entries on or after, e.g.”
- end_datestring“ISO 8601 end date to filter entries on or before, e.g.”
- takeinteger“Number of entries to return (default 25, max 100).”
- skipinteger“Number of entries to skip for pagination.”
delete_career_entry
“Permanently deletes a career journal entry by UUID.”
Publisher declares: read-only no · destructive yes · open-world no
1 input, 1 required
- uuidstringrequired“UUID of the career entry to delete.”
get_career_journal_prompts
“Returns a set of context-aware reflection questions to guide a career journaling session.”
Publisher declares: read-only yes · destructive no · open-world no
1 input
- session_typestring“Type of journaling session.”
list_experiences
“Returns the user's work experience records with their integer IDs.”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
add_job_application_note
“Adds a note to a job application's timeline.”
Publisher declares: read-only no · destructive no · open-world no
3 inputs, 3 required
- application_idstringrequired“UUID of the job application to attach this note to.”
- bodystringrequired“The note text (plain text or Markdown).”
- categorystringrequired“Category tag for the note.”
list_job_application_notes
“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.”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
- application_idstringrequired“UUID of the job application whose notes to retrieve.”
update_job_application_note
“Updates the body or category of an existing job application note.”
Publisher declares: read-only no · destructive yes · open-world no
4 inputs, 4 required
- note_uuidstringrequired“UUID of the note to update.”
- application_idstringrequired“UUID of the job application this note belongs to.”
- bodystringrequired“Updated note text.”
- categorystringrequired“Category tag for the note.”
delete_job_application_note
“Permanently deletes a note from a job application's timeline.”
Publisher declares: read-only no · destructive yes · open-world no
2 inputs, 2 required
- note_uuidstringrequired“UUID of the note to delete.”
- application_idstringrequired“UUID of the job application this note belongs to.”
search_contactson 14 other servers
“Searches the user's job-search contacts in GigHQ — recruiters, hiring managers, referrals, and other people they are networking with.”
Publisher declares: read-only yes · destructive no · open-world no
4 inputs
- namestring“Filter by contact name (case-insensitive substring match).”
- statusstring“Filter by outreach status.”
- takeinteger“Number of contacts to return (default 25, max 100).”
- skipinteger“Number of contacts to skip for pagination.”
get_contacton 46 other servers
“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, e…”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
- contact_idstringrequired“UUID of the contact.”
update_contact_status
“Updates a contact's outreach status in GigHQ.”
Publisher declares: read-only no · destructive no · open-world no
2 inputs, 2 required
- contact_idstringrequired“UUID of the contact.”
- statusstringrequired“New outreach status.”
add_contact_interaction
“Logs a touchpoint with one of the user's job-search contacts — a call, a LinkedIn message, a coffee chat, a referral conversation, etc.”
Publisher declares: read-only no · destructive no · open-world no
4 inputs, 3 required
- contact_idstringrequired“UUID of the contact.”
- typestringrequired“Kind of interaction being logged.”
- bodystringrequired“Short note about the interaction — what was discussed or sent.”
- occurred_atstring“ISO 8601 date the interaction happened, e.g.”
get_career_compass
“Retrieves the user's saved CareerCompass data: professional objectives, positioning statement, categorized skills (technical/soft/management/other), and target market (industries, company size, geogr…”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
generate_career_compass
“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 ma…”
Publisher declares: read-only yes · destructive no · open-world no
2 inputs
- career_stagestring“The user's career stage, if known.”
- career_switch_detailsobject“Required for useful output when career_stage is 'Career Switcher'.”
save_career_compass
“Persists CareerCompass data to the user's GigHQ profile.”
Publisher declares: read-only no · destructive yes · open-world no
17 inputs
- professional_objectivesstring“The chosen professional objective statement.”
- positioning_statementstring“The chosen positioning statement.”
- technical_skillsarray“Technical skills.”
- soft_skillsarray“Soft skills.”
- management_skillsarray“Management skills.”
- other_skillsarray“Other skills.”
- target_industriesarray“Target industries.”
- company_sizearray“Target company sizes.”
- geographic_locationarray“Target geographic locations.”
- career_stagestring
- career_switch_typestring
- target_industrystring“Single primary target industry, distinct from the target_industries list.”
- target_rolestring“Single primary target role.”
- is_completeboolean“Defaults to true server-side.”
- progress_stepinteger“Wizard step reached, for an in-progress save (is_complete: false).”
- objective_suggestionsarray“The AI-generated objective candidates shown to the user, so a resumed session can show the same options.”
- target_job_titlesarray“Up to 5 target job titles.”
recommend_target_roles
“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.”
Publisher declares: read-only yes · destructive no · open-world no
4 inputs
- industry_preferencestring“Industry the user wants to target, if stated.”
- senioritystring“Seniority level the user is targeting, if stated.”
- open_to_pivotboolean“Whether the user is open to a role/industry pivot, if stated.”
- location_preferencestring“Remote/hybrid/location preference, if stated.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-24.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description: 98% of 98
Tools with a description: 100% of 34
Typical description length: 570 characters

The tool set

Counted from the listing

Tools: 34
Size of the list: about 15,243 tokens for an agent to load (characters ÷ 4)
Naming: 34 of 34 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 34 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-24 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://mcp.gighq.ai/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "gighq": {
      "url": "https://mcp.gighq.ai/mcp"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "gighq": {
      "type": "http",
      "url": "https://mcp.gighq.ai/mcp"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"gighq","type":"http","url":"https://mcp.gighq.ai/mcp"}'

Claude Code

claude mcp add --transport http gighq https://mcp.gighq.ai/mcp

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.gighq.ai/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint mcp.gighq.ai/mcp	Session opened	matches	our test · 2026-10-24
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-24
Repository github.com/gighq-ai/gighq-skill	Opens publicly	matches	api.github.com · 2026-10-24

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: ai.gighq
GitHub owner: an organization (gighq-ai)

Repository: github.com/gighq-ai/gighq-skill
Stars: 0
Repository age: 0–30 days
Last push: 0–30 days ago
Archived: no

Source: the registry entry and api.github.com · 2026-10-24.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 4 record checks met · 4 do not apply · 1 not checked

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
Not checkedRepository publishes a security policy (SECURITY.md)We did not read this repository's security policy.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-24. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about ai.gighq/gighq

Answered from the data above

Is ai.gighq/gighq safe to install?

We do not rate servers as safe or unsafe. 4 of its 4 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does ai.gighq/gighq need an API key or sign-in?

It opened a session without any credential on 2026-10-24. The registry entry declares no required credential; no declaration is not a guarantee.

Has ai.gighq/gighq been security tested?

Partly. 3 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

Where is the source code of ai.gighq/gighq?

In github.com/gighq-ai/gighq-skill, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-24

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

3 exercised12 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 12

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 3

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-24, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
1,207 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 34 tools, 0 resources, 0 prompts.
4,495 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

pending: added in the weekly update

listed 2026-10-24; not classified yet

Pricing modelAI-classified

pending: added in the weekly update

the website is not read yet

Programming language

not stated

GitHub detects no source language in this repository (docs-only or empty)

Hosting type

remote (hosted by the publisher)

registry · 2026-10-24

MCP capability

resources, tools, extensions

our test · 2026-10-24

Transport

streamable HTTP

registry · 2026-10-24

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-24

Lifecycle status

active

registry · 2026-10-24

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

owner: an organization · repository age: 0–30 days · stars: 0–9

api.github.com · 2026-10-24

Maintenance

active

api.github.com · 2026-10-24

Environment

the publisher's infrastructure

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “ai.gighq/gighq: MCP server record.” Data checked 2026-10-24. https://protocolprobe.com/mcp/servers/ai.gighq/gighq

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/ai.gighq/gighq)](https://protocolprobe.com/mcp/servers/ai.gighq/gighq)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology