JobHound

by Null-Phnix

Overview Schema Related Servers Score Discussions

Python

Local

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v0.1.0
Disambiguation4/5
Each tool serves a distinct function: scanning, listing, retrieving, updating, applying, and daemon control. The only potential confusion is between `jobhound_get` and `jobhound_get_for_tailoring`, but their descriptions clarify the different outputs.
Naming Consistency4/5
All tools use the `jobhound_` prefix with snake_case verbs like `get`, `list`, `scan`, `update`, `apply_tailored`. Minor deviations are `jobhound_status` (a noun rather than a verb) and `jobhound_get_for_tailoring` (a longer phrase), but the pattern is consistent enough to predict tool purpose.
Tool Count5/5
9 tools is well-scoped for a job application automation server. Each tool covers a necessary step in the workflow: scanning, queuing, tailoring, applying, tracking, and daemon lifecycle.
Completeness4/5
The core workflow is fully covered: scan → list → get_for_tailoring → apply_tailored, plus status updates and daemon control. Minor gaps include no tool for manually adding or deleting jobs, but these are not essential for the automated pipeline.
Average 3.8/5 across 9 of 9 tools scored. Lowest: 2.9/5.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 0 commits in the last 12 weeks
- Last stable release on March 11, 2026
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. It adds that the tool returns a cover letter 'if applied,' which is useful conditional behavior, but it does not describe potential errors, absence of a job, or any side effects. For a read-only getter this is acceptable but still minimal.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise and front-loaded. Every sentence adds necessary information: the first states the purpose, the second defines the argument. There is no fluff or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple get-by-ID tool, the description covers the core purpose and param. However, it lacks any mention of how this differs from related tools like get_for_tailoring, and does not address failure modes or return value specifics. The presence of an output schema reduces the need to describe returns, but the tool's place among siblings is unclear.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description coverage is 0%, so the description must compensate for parameter meaning. However, the description merely restates the schema's type and name ('job_id: integer ID') without adding context about where to find the ID, its format, or any constraints. This adds no value beyond the structured schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb ('Get') and the resource ('full details for a job'), including the conditional inclusion of a cover letter. It is specific enough to understand the tool's core function, though it does not explicitly distinguish it from sibling tools like jobhound_list or jobhound_get_for_tailoring.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives like jobhound_list or jobhound_get_for_tailoring. The description implies use when a specific job_id is available, but does not state exclusions or when another tool would be more appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure, but it only states the action without revealing side effects, idempotency, or state changes. It doesn't say what occurs if the daemon is already running or whether resuming triggers other processes.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no redundant words, immediately stating the action. It is efficiently structured and every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is very simple with no parameters, and an output schema exists to cover return values. The description provides the essential purpose but lacks usage context and behavioral detail. It is minimally adequate for a straightforward daemon control action.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has zero properties, so there are no parameter semantics to explain. Per the baseline rule for 0-parameter tools, a score of 4 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb 'Resume' and clearly identifies the resource 'JobHound daemon', making the action unambiguous. It does not explicitly differentiate from siblings like jobhound_pause, but the verb itself implies the opposite action.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no guidance on when to use this tool versus alternatives. It doesn't mention that it should be used after jobhound_pause or that the daemon must be paused. No contextual or exclusionary guidance is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It does not explicitly state that this is a read-only operation, nor does it mention any side effects, authentication needs, or data freshness. While a summary might be inferred as safe, that is not stated.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that is concise and front-loaded, communicating the essential purpose without unnecessary words. It is efficiently structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple with no parameters and has an output schema, so return values need not be explained. However, the description lacks context about what 'JobHound activity' encompasses, what statuses are counted, or whether the summary is global or scoped. This leaves room for ambiguity in tool selection.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the baseline is 4. The description does not need to add parameter meaning, and it does not conflict with the schema, which is empty.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it provides a summary of job counts by status, which distinguishes it from sibling tools like jobhound_get and jobhound_list that focus on individual job details. The phrasing 'Summary of JobHound activity' is somewhat vague but immediately clarifies with 'job counts by status.'
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use this tool versus alternatives. It does not mention contexts, exclusions, or directional hints to other tools. The description merely states what it does without explaining appropriate scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden. It discloses the fallback attempt order and that the outcome is recorded in the database, which is useful. However, it does not mention potential side effects like sending emails, irreversibility, or failure behavior beyond the fallback chain, leaving gaps in transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and front-loaded: a clear purpose sentence, a fallback chain sentence, a database side-effect sentence, and a structured Args block. Each sentence earns its place; no fluff. The Args block is a bit redundant with the schema but justifiable given the lack of schema descriptions.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be described. The description covers the tool's action, fallback strategy, and database recording. However, it omits prerequisites (e.g., job_id must reference a valid job, tailored_cv should come from get_for_tailoring), error handling if all attempts fail, and potential duplicate-application guards. These gaps make it adequate but not complete for a side-effectful action.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has no parameter descriptions (0% coverage), so the Arg list in the description is necessary. It names all three parameters and adds 'markdown' for tailored_cv, but otherwise just restates the schema's names and types. It provides no constraints, examples, or relationships to other tools, so it adds minimal meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb-resource pair: 'Submit an application using the tailored CV and cover letter.' It clearly identifies the tool's sole purpose and differentiates it from sibling tools like status, get, update, and get_for_tailoring, which serve different actions.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is used when you have a tailored CV and cover letter ready, and the fallback chain (LinkedIn MCP → direct POST → Blackreach) gives context on how it attempts to submit. It doesn't explicitly exclude alternatives, but no sibling tool overlaps with applying, so the usage is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full transparency burden. It adds that the output includes 'database IDs', which is useful for chaining with other tools. However, it does not disclose default behavior (e.g., when status is omitted), pagination, ordering, or any side effects. The verb 'List' implies read-only, but this is not stated explicitly.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise with two sentences. The main purpose is stated first, followed by a focused parameter explanation. Every word contributes value; there is no padding or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple (one optional parameter) and has an output schema, so the description does not need to detail return values. It covers the core purpose, the parameter's allowed values, and the fact that database IDs are included. Missing the default status and explicit usage guidance, but overall adequate for a low-complexity tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 0% parameter descriptions, and the description compensates by enumerating the allowed status values ('new, queued, applied, failed, interviewing, rejected'). It also explains the parameter's role ('by status'). It does not mention the default value (queued) which is present in the schema but not repeated, and does not clarify if the parameter is optional or required beyond the schema's default.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb ('List'), the resource ('jobs'), and the specific scope ('by status with their database IDs'). It distinguishes from siblings like jobhound_get (which likely fetches a single job) and jobhound_status (which likely checks a specific status).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or mention sibling tools. The only usage context is implied by the phrase 'List jobs by status', which is not differentiated from other listing or status-related tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden. It clearly states what is returned (job description and full resume) and implies a read-only operation via the verb 'Get', but does not explicitly disclose non-mutation or any side effects. It also gives a precondition for job_id (from list 'queued'). This is adequate but not exhaustive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences and an Args block, all compact and informative. The main purpose is stated first, followed by the return content and the next action. No filler words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one parameter, clear return), the description covers the essential workflow: what it returns, what to do next, and where the ID comes from. The presence of an output schema covers structured return details, so the high-level return summary is sufficient. It could mention error cases but that's a minor gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema only provides the type and required flag for job_id, with no description. The description adds critical meaning: the ID must come from jobhound_list('queued'), which is a significant addition. This compensates for the 0% schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb 'Get' and identifies the resource ('everything needed to write a tailored application'), and explicitly returns the job description and full resume. It differentiates from sibling 'jobhound_get' by indicating its role in the tailoring workflow and specifying the returned items.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It provides workflow guidance: after reading, generate a tailored CV and cover letter, then call jobhound_apply_tailored(job_id, tailored_cv, cover_letter). It also tells the user where the job_id comes from (jobhound_list('queued')), which helps select the correct input. However, it doesn't explicitly contrast this with jobhound_get, but the name and context imply the distinction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of disclosing behavioral traits. It makes the mutating nature clear ('update') and lists valid status values, but it does not mention potential side effects, reversibility, or any required permissions. For a simple update, this is adequate but not fully transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and well-structured: a one-sentence purpose, a one-sentence usage guideline, and a compact argument list. Every element earns its place with no wasteful words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter update tool, the description covers purpose, usage, and arguments. The presence of an output schema means return values need not be described. It falls short only by omitting any prerequisites or notes on what the update does to existing data, but overall it is largely complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, but the description compensates fully by documenting both parameters: 'job_id: integer ID' and 'status: interviewing, rejected, applied, failed, queued.' This adds critical meaning, including an explicit enum list that is missing from the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: 'Manually update a job's status.' The verb 'update' combined with the resource 'job status' is specific and distinct from sibling tools like jobhound_get or jobhound_status, which likely read or retrieve status.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides explicit context for when to use the tool: 'Use this when you get an interview invite or rejection.' This gives clear usage guidance, though it does not explicitly mention alternatives or exclusions, which is why it doesn't score a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It explicitly states that the scan loop stops applying, which is the key behavioral effect. It does not cover edge cases like idempotency or in-flight operations, but the core behavior is clearly disclosed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence that front-loads the action and resource, adding only the necessary clarification about the scan loop. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter tool with a clear output schema, the description adequately covers the tool's purpose and effect. Sibling names like jobhound_resume provide related context, making the description complete for an agent to select and invoke correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the description fully covers the semantics by simply stating the action. The baseline of 4 for no-parameter tools applies, and the description adds no confusion.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb 'Pause' and identifies the resource 'JobHound daemon', with clarifying detail 'scan loop stops applying' that clearly distinguishes it from sibling tools like jobhound_status or jobhound_resume.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage context (when you want to halt scanning) but does not explicitly state when not to use or reference alternatives. However, the sibling tool jobhound_resume is implicitly complementary, making the usage clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose side effects. It clearly states that jobs above a score threshold are saved with status 'queued' and that a summary plus queued IDs are returned. This gives the agent a good model of the behavior, though it doesn't specify threshold values or idempotency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is four concise sentences, each adding value: action, outcome, return value, and next steps. No filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter tool with an output schema, the description covers the operation, side effects, return content, and downstream steps. It is sufficient for an agent to correctly invoke and process the tool's results.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
This tool has zero parameters, so the baseline is 4. The description adds no parameter-specific details because there are none; it correctly omits any schema repetition.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear multi-step action: fetch jobs from all configured sources, score them, and queue high-scoring ones. This distinguishes it from sibling tools like jobhound_list or jobhound_get, which are for querying existing jobs.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It provides explicit next-step guidance, telling the agent to call jobhound_list('queued') then jobhound_get_for_tailoring(id). This implies jobhound_scan is the entry point for processing new jobs, though it doesn't enumerate exclusions or alternative scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![jobhound MCP server](https://glama.ai/mcp/servers/Null-Phnix/jobhound/badges/card.svg)](https://glama.ai/mcp/servers/Null-Phnix/jobhound)

Score Badge

Copy to your README.md:

[![jobhound MCP server](https://glama.ai/mcp/servers/Null-Phnix/jobhound/badges/score.svg)](https://glama.ai/mcp/servers/Null-Phnix/jobhound)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Null-Phnix/jobhound'

If you have feedback or need assistance with the MCP directory API, please join our Discord server