MCP servers observed by Lowdown
me.freehire/freehire MCP server: daily status and tool changes
Required authentication (HTTP 401/403) on the last 2 consecutive checks (2026-11-16 to 2026-11-19) (Lowdown checks this server every 3 days). Lowdown checks without credentials, so no tools were listed. 2 of 4 checks in the last 30 days had this result. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-13 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:me.freehire/freehire
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:me.freehire/freehire?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-19: the server required authentication (HTTP 401/403).
- Observed days in the last 30: 4
- Answered initialize and tools/list: 2
- Required authentication: 2
- No response: 0
- Remotes differed: 0
Does it require authentication?
It returned HTTP 401/403 on 2 of 4 observed days. Lowdown checks without credentials, so the tools behind authentication were not listed.
Did its tools change recently?
Tool definitions changed on 1 of 1 compared days.
- 2026-11-13: input or output schemas changed, descriptions changed, tool names changed; tool count 51 → 56
What tools does it list?
56 tools on 2026-11-13:
add_cvanswer_bank_deleteanswer_bank_listanswer_bank_saveapply_jobauto_apply_cancelauto_apply_getauto_apply_listauto_apply_retryauto_apply_reviewauto_apply_startbuddy_joinbuddy_leavebuddy_mock_bookbuddy_mock_cancelbuddy_mock_hostsbuddy_mock_listbuddy_mock_schedule_add_overridebuddy_mock_schedule_deletebuddy_mock_schedule_getbuddy_mock_schedule_set_weeklybuddy_mock_settings_setbuddy_mock_slotsbuddy_statuscheck_jobs_openfacetsfetchget_companyget_jobget_planget_profileget_setup_statusjob_market_statslist_filter_valueslist_subscriptionslist_unread_mailmarket_fitmy_jobsreport_jobreport_problemsalary_statssave_jobscreening_answers_getscreening_answers_setsearchsearch_companiessearch_jobssimilar_jobssubscribesubscription_updatessuggest_dictionary_termtrack_jobunsave_jobunsubscribeupdate_profileupdate_subscription
MCP Registry declaration
- Registry name:
me.freehire/freehire - Declared version: 0.8.0
- Status: active
- Declared hosts:
freehire.me
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:me.freehire/freehire", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:me.freehire/freehire?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:me.freehire/freehire -- npx -y freehire-mcp
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).