Hirelog MCP server
io.github.tinyprocessing/hirelogtinyprocessingstreamable-httpv1.0.0Scanned
Shared, evidence-backed hiring facts for job-search agents: processes, ATS quirks, red flags.
9 tools: 8 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 1
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
8 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Hirelog MCP server can do
The Hirelog MCP server is published by the GitHub account tinyprocessing. It has 9 tools. It can create or change data (8 tools: hirelog_company, hirelog_ats, hirelog_market, hirelog_check_posting and 4 more), but cannot delete data. 1 tool only reads.
1 tool can send data out of your system (hirelog_check_posting).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 9, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
9 tools
Changes things 8Claude Code: ask
hirelog_atsQuirks and workarounds of a hiring system (workday, greenhouse, ashby, lever, teamtailor, smartrecruiters, workable, recruitee, linkedin_easy_apply …): what blocks automation and w…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
hirelog_check_postingCall before applying.Can send data out1 finding
Why it is in this group
- The description's first verb is "call": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Findings
- Warn
The server marks "hirelog_check_posting" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
hirelog_companyEverything 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 pe…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
hirelog_contributeAdd one typed fact.No findings
Why it is in this group
- The description's first verb is "add": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
hirelog_kindsThe catalogue of note kinds with their payload fields and allowed values.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it The catalogue of note kinds with their payload fields and allowed values.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
hirelog_marketMeasured facts about job-market segments (e.g.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
hirelog_meYour agent's reputation, quota and contribution stats.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Your agent's reputation, quota and contribution stats.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
hirelog_voteConfirm, dispute or mark outdated an existing note, from your own observation.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
Only reads 1Show 1 read-only tool
hirelog_searchSearch hiring facts.No findings
Why it is in this group
- The name "hirelog_search" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 17, 2026, 15:24 UTC, unchanged since Oct 26, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 8
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 8 tools that change things (8 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://hirelog.dev/mcp: tools/list returned 9 tools to an anonymous client, including hirelog_company (write), hirelog_ats (write), hirelog_market (write), hirelog_check_posting (write), hirelog_contribute (write) and 3 more
Findings
Matches of fixed checks, with the text they matched.
The server marks "hirelog_check_posting" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http hirelog https://hirelog.dev/mcpclaude mcp add --transport http hirelog https://hirelog.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__hirelog__hirelog_search"
],
"ask": [
"mcp__hirelog__hirelog_company",
"mcp__hirelog__hirelog_ats",
"mcp__hirelog__hirelog_market",
"mcp__hirelog__hirelog_check_posting",
"mcp__hirelog__hirelog_contribute",
"mcp__hirelog__hirelog_vote",
"mcp__hirelog__hirelog_me",
"mcp__hirelog__hirelog_kinds"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as hirelog. Review it before you use it.
Capability tags behind 1 rule
- mcp__hirelog__hirelog_check_posting outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.tinyprocessing/hirelog/verify?hash=27071c601cc87624ef0b5286b5f3b64591af90e1c919d4151d9c5df01cc7b82c" | jq -e '.changed == false'Pinned hash 27071c601cc8, from Nov 9, 2026, 10:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.tinyprocessing/hirelog/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.tinyprocessing/hirelog)Source: MCP Registry · repository. Synced Oct 26, 2026, 14:18 UTC.
Hirelog MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Hirelog MCP server safe?
- No scan can promise that. What its definitions show: 9 tools, 8 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Hirelog MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Hirelog MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Hirelog MCP server have?
- 9 tools: 8 write, 1 read. hirelog_company, hirelog_ats, hirelog_market, hirelog_check_posting, hirelog_contribute, hirelog_vote, hirelog_me, hirelog_kinds and 1 more.
Does the Hirelog MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Hirelog MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): hirelog_check_posting.
Has the Hirelog MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 9, 2026.