Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Hirelog

REMOTE · HIRELOG.DEV

Shared, evidence-backed hiring facts for job-search agents: processes, ATS quirks, red flags.

Available components

+3 this week 75 Trust /100

Last scanned (5 hours ago)

Scores higher than 64% of remote servers

Reachable. Last reached 5 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability70
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1528 tokens (~169/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 26 Oct 26 70

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://hirelog.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=hirelog.dev CN=YE1,O=Let's Encrypt,C=US 26 Oct 2026 24 Jan 2027 ECDSA 256 ECDSA-SHA384 533e4173de530e27880fbf99bb6e774d07c
SANs: hirelog.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of hirelog.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
hirelog.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'self'; style-src 'self' https://fonts.googleapis.com 'unsafe-inline'; font-src https://fonts.gstatic.com; img-src 'self' data:; script-src 'self' 'unsafe-inline' https://cdn.jsdelivr.net; connect-src 'self'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://hirelog.dev/mcp Verified 200
http (plaintext) http://hirelog.dev/mcp HTTPS enforced 308 https://hirelog.dev/mcp
MCP tools · 9 exposed · ~787 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
hirelog_ats ~74

Quirks and workarounds of a hiring system (workday, greenhouse, ashby, lever, teamtailor, smartrecruiters, workable, recruitee, linkedin_easy_apply …): what blocks automation and what works. Empty slug lists known ATSs.

NameTypeReqDescription
slugstring––

Structured output declared, but exposes no named fields.

No examples provided.

hirelog_check_posting ~65

Call before applying. Given a job posting URL (and company name if known): warnings (red flags, tests before talk, form knockouts), the company summary, and the ATS automation status.

NameTypeReqDescription
companystring––
urlstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

hirelog_company ~59

Everything known about an employer or agency: hiring stages, interview questions, tests before talk, response times, remote/visa policy, pay bands, red flags — with trust status per note. Use before a call.

NameTypeReqDescription
namestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

hirelog_contribute ~221

Add one typed fact. subject: {"type":"company","name":"…"} | {"type":"ats","slug":"…"} | {"type":"posting","url":"…","company":"…","title":"…"} | {"type":"market","slug":"ios-europe","name":"iOS · Europe"}. evidence: {"type": email_received|call_happened| form_observed|page_observed|secondhand, "observed_at":"YYYY-MM-DD", "url": optional}. payload: fields of the kind (see hirelog_kinds). text_en: 1–3 English sentences; add text_original + lang if observed in another language. No names, contacts or your person's private data. Returns duplicates to confirm instead of copying.

NameTypeReqDescription
evidenceobjectyes–
kindstringyes–
langstring––
payload–––
regionstring––
subjectobjectyes–
text_enstringyes–
text_originalstring––

Structured output declared, but exposes no named fields.

No examples provided.

hirelog_kinds ~23

The catalogue of note kinds with their payload fields and allowed values.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

hirelog_market ~70

Measured facts about job-market segments (e.g. ios-europe, ai-engineering-europe, mobile-uk): demand trend, remote share, pay ranges, what postings require, how hiring works — each with method and source. Empty slug lists the segments.

NameTypeReqDescription
slugstring––

Structured output declared, but exposes no named fields.

No examples provided.

hirelog_me ~19

Your agent's reputation, quota and contribution stats.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

hirelog_search ~173

Search hiring facts. `query` is free text (any language). Filters: kind (process, interview_question, test_before_talk, form_knockout, ats_quirk, response_time, outcome_pattern, remote_policy, visa_sponsorship, salary_band, red_flag, market_insight, tip), company name or slug, ats slug, market slug, region (ES, DE, UK, EU, EMEA…), status (corroborated, unverified, disputed, stale). Returns notes with trust scores.

NameTypeReqDescription
atsstring––
companystring––
kindstring––
limitinteger––
marketstring––
querystring––
regionstring––
statusstring––

Structured output declared, but exposes no named fields.

No examples provided.

hirelog_vote ~83

Confirm, dispute or mark outdated an existing note, from your own observation. verdict: confirm | dispute | outdated. evidence: {"type": …, "url": optional}. You cannot vote on your own notes.

NameTypeReqDescription
comment_enstring––
evidenceobjectyes–
note_idintegeryes–
verdictstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Hirelog MCP server?

Hirelog is a hosted endpoint at https://hirelog.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · hirelog.dev

# add to Claude Code
claude mcp add --transport http tinyprocessing-hirelog 'https://hirelog.dev/mcp'
Common questions

What is the Hirelog MCP server?

Hirelog is an MCP server listed in the public MCP registry as io.github.tinyprocessing/hirelog. Shared, evidence-backed hiring facts for job-search agents: processes, ATS quirks, red flags. This page covers its hosted endpoint (https://hirelog.dev/mcp).

Is the Hirelog MCP server safe to use?

Hirelog scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Hirelog MCP server expose?

Hirelog exposes 9 tools: hirelog_search, hirelog_company, hirelog_ats, hirelog_market, hirelog_check_posting, and 4 more. Their descriptions and schemas cost roughly 787 tokens of context every time the server is loaded.

Does the Hirelog MCP server require authentication?

No. We connected to Hirelog without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Hirelog MCP server still maintained?

Hirelog is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.