Skip to content
MCPSTAMP
MCP server report

GigHQ.ai MCP server

ai.gighq/gighq

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 91 of 100 (grade A), higher than 62.2% of the 33,003 registry servers that responded over HTTPS that day. Ready for Gemini and MCP Registry. Not ready for Claude and ChatGPT.

Measured facts

Score
91A
Sign-in
OAuth
Tools listed
34
Protocol version
2025-11-25
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Not ready Blocked by Human-readable title on every tool.
ChatGPT app directory Not ready Blocked by issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT) and Human-readable title on every tool.
Gemini Connected Apps Ready No blocking check failed.
Official MCP Registry Ready No blocking check failed.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

4 checks to fix

  1. Fails

    Human-readable title on every tool

    tool_titles

    Blocks Claude and ChatGPT.

    Measured 34/34 without title: search_companies, get_company_details, get_job_details, update_job_application_status, toggle_job_application_interest and 29 more

    Add a short human-readable "title" to every tool (shown in store UIs and consent screens).

  2. Fails

    issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT)

    auth_chatgpt_metadata

    Blocks ChatGPT.

    Measured token_endpoint_auth_methods_supported missing

    Use the exact metadata "issuer" string in the protected resource metadata authorization_servers list (no trailing-slash or case differences), and list token_endpoint_auth_methods_supported (for example ["none"] for public clients) in the au

  3. Warning

    Tool descriptions

    tool_descriptions

    Measured 1 over 2000 chars: add_career_entry

    Keep each tool description between 60 and 2000 characters: when to use it, what it returns, key limits.

  4. Warning

    JSON-RPC error for unknown method

    jsonrpc_errors

    Measured HTTP 401 instead of a JSON-RPC error

    Route the method first and answer unknown methods with JSON-RPC error -32601 before the auth check, or return a JSON-RPC error body with the 401.

23 checks passed

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, GET answers SSE or 405, initialize latency, serverInfo name and version, Server instructions, tools capability declared, Sign-in method the store supports (OAuth or none), 401 carries WWW-Authenticate resource_metadata, Protected resource metadata (RFC 9728), Resource metadata "resource" equals the server URL, Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields, PKCE S256 advertised, Client registration (DCR or Client ID Metadata Documents), refresh_token grant advertised, tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable, readOnlyHint or destructiveHint on every tool, Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT).

Run a fresh check

This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

McpStamp score for GigHQ.ai

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Fmcp.gighq.ai%2Fmcp)](https://www.mcpstamp.com/r/ai-gighq-gighq/)

HTML

<a href="https://www.mcpstamp.com/r/ai-gighq-gighq/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Fmcp.gighq.ai%2Fmcp" alt="McpStamp score" height="20"></a>
Registry entry

About this server

Job-search tracker for AI agents: applications, stale follow-ups, skills gaps, H-1B lookup.
Registry name
ai.gighq/gighq
Remote URL
https://mcp.gighq.ai/mcp
Version
1.0.0
Source
github.com/gighq-ai/gighq-skill
Website
www.gighq.ai/mcp-server/
Checked
2 November 2026, engine 1.2.0, no credentials

The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.

More grade A servers

All grade A servers · All server reports · State of MCP readiness, November 2026