Get the full context on any candidate or job opening. 
Claude 
ChatGPT 
Cursor 
Gemini 
Windsurf 
VS Code 
JetBrains 
Vercel
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Connect to your AI in seconds.
JobScore connects your AI agent to a full Applicant Tracking System (ATS). It lets you pull everything you need to manage hiring: job details, candidate profiles, team structures, and where applicants came from.
Stop jumping between tabs and get the complete picture of your talent pipeline in one go.
What your AI can do
Get candidate
Pulls a specific applicant's complete profile, including their status and contact history.
Get job
Retrieves the full job description and requirements for one specific opening.
Get me
Verifies your current connection status and user identity within JobScore.
Retrieves a complete catalog of active job listings, including requirements and team identifiers.
Lists every candidate in your system, showing their current stage and unique IDs for tracking.
Gets a specific person's full application history, resume highlights, and contact information.
Lists all users, departments, and dedicated hiring teams within the company account.
Identifies exactly which source (like a referral or job board) brought in each candidate.
Ask an AI about this
Compatible AI Apps
OAuth 2.0 Compatible Gemini Waiting for input…
JobScore: 10 Tools for Talent Acquisition
These tools let your agent interact with every core function of the JobScore ATS, giving you full control over candidate data retrieval.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using JobScore on VinkiusGet Candidate
Pulls a specific applicant's complete profile, including their status and contact history.
Get Job
Retrieves the full job description and requirements for one specific opening.
Get Me
Verifies your current connection status and user identity within JobScore.
List Candidates
Generates a list of all applicants, including their names and current application...
List Departments
Lists every department (e.g., Finance, Engineering) used to categorize jobs in the...
List Hiring Teams
Retrieves a list of designated recruiters and hiring managers assigned to specific roles.
List Jobs
Returns titles, IDs, and departments for every active job opening in the account.
List Locations
Lists all physical office locations where the company hires people.
List Sources
Identifies and lists every channel (LinkedIn, Referral) used to source applicants.
List Users
Outputs a roster of all current users in the JobScore account for administrative...
Connect to your AI in seconds. Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The JobScore integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with JobScore, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by JobScore. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 10 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
The JobScore data spread across five different tabs.
Right now, figuring out the full picture involves opening JobScore and jumping through hoops. You check one tab for job openings (`list_jobs`), then another to see which departments own them (`list_departments`). If you find a match, you have to open yet *another* page just to confirm who is supposed to be running that role (the hiring team). It's clicking, copying IDs, and pasting into spreadsheets.
With this MCP, your agent handles the whole sequence. You ask it for job details, and it automatically pulls in department ownership and team members; you get one clean, structured output instead of five separate browser tabs.
The JobScore API gives you complete candidate visibility.
Instead of having to manually track down a candidate's current status or their full contact history—which often means emailing the recruiter just to find out where they are in the pipeline—you run `get_candidate`. That single call delivers all that crucial data points.
It’s not just reading a name; it’s pulling an entire, validated profile. You know exactly where you stand on any given application.
What your AI can actually do with this
Look, when you're running recruitment, most of the data lives in silos. You might have a list of open jobs here, but then you need to check the status of candidates against those roles, cross-referencing which department owns that job or who on the team is supposed to interview them.
This MCP lets your AI agent access JobScore's full API, so it can gather all that context for you. Your agent doesn't just read a name; it pulls the candidate's entire contact history and current status in one shot. Need to know which department owns this opening? Or where did the applicant originally find the job listing? You get all that data automatically streamed into your workflow, right through Vinkius.
It means you spend time actually hiring people, not building complex reports or manually cross-referencing spreadsheets.
019d75bd-850f-710a-bd95-6e0d8b0d1978 
Here's how it actually works
The bottom line is that your agent combines these separate data points—jobs, people, and teams—into one actionable summary.
First, tell your agent to get all current open jobs using the list_jobs tool. This gives you the core set of opportunities.
Next, run list_candidates to pull a list of applicants and their IDs; then, use those IDs with get_candidate to gather detailed profiles for anyone needing review.
Finally, if you need context, call list_hiring_teams or list_departments. This provides the organizational structure needed to assign next steps.
Who is this actually for?
This is for the HR Tech Manager who spends half their day building custom reports in Airtable because the ATS doesn't talk to anything else. It’s also for the Talent Acquisition Specialist who needs a single source of truth on candidate status, and anyone frustrated by manual data retrieval.
Uses this MCP to check every open job via list_jobs, then uses list_candidates to see who's applied. They cross-reference the source using list_sources before scheduling an interview.
Relies on this tool to quickly check a candidate's full record using get_candidate, or to see which specific hiring team needs to review their materials via list_hiring_teams.
Uses the MCP to verify user identities with list_users and map out department relationships using list_departments, ensuring data accuracy across the entire system.
What Changes When You Connect
Stop guessing where a candidate came from. By calling list_sources, you instantly know if they were a referral, which helps measure your best channels.
You never have to manually check who is responsible for an open role again. Just ask the agent to use list_hiring_teams and get the assigned managers immediately.
Need to compare job requirements against internal structure? Call list_departments first, then use that data when running get_job to ensure you're posting in the right business unit.
When evaluating a candidate, don't just rely on the application form. Use get_candidate to pull their full contact history and resume highlights for complete due diligence.
Need an overview of your entire talent funnel? Running list_candidates gives you names and stages across all roles without needing multiple manual searches.
See it in action
A new role is opening, but the hiring team isn't assigned.
The agent gets a job ID from list_jobs, then calls get_job to get requirements. The next step is asking who should own it; the agent runs list_hiring_teams and identifies the correct department using list_departments.
You suspect a job opening isn't pulling in enough applicants.
The agent uses list_sources to check where candidates are coming from. If that data is good, but the results are low, it prompts you to run get_job for more details and potentially adjust the listing.
You need a quick roster of all available contacts for an internal meeting.
The agent runs list_users to get names and roles, then uses that list to check if specific team members are assigned to relevant jobs via list_hiring_teams.
A candidate's status seems inconsistent across different systems.
The agent runs get_candidate first. If the data is still unclear, it uses list_locations to confirm if the candidate was applying for a role in your main office or one of your smaller branches.
The honest tradeoffs
Searching by department name only
Trying to find all jobs just because you know it's 'Marketing'. You might miss roles that are cross-listed or in a different internal unit.
First, run list_departments to see the official names. Then, use list_jobs, filtering by those exact department IDs, and finally call get_job for details.
Checking candidate status manually
Having to log into JobScore's web portal every time you need a resume highlight or contact detail. It’s slow and prone to human error.
Just run get_candidate in your agent. It pulls the full, up-to-date profile and status without you leaving your workflow.
Assuming a candidate is internal staff
Seeing a name on a list and assuming they are an employee when they're actually just a highly engaged applicant.
Always verify the individual first. Use list_users to check if the person exists as an active employee before treating them as internal.
When It Fits, When It Doesn't
Use this MCP if your process relies on connecting distinct pools of data: job openings, applicant identities, and organizational structure. For instance, you need to know who (list_users) is responsible for a role that requires candidates from a specific department (list_departments). Don't use this if you are only performing simple communication tasks—you just need an email sender tool. If your goal is simply writing copy or summarizing text, your AI client can do that natively; you don't need the API overhead. But if you need to retrieve verifiable records, like running get_candidate against a specific ID, then this MCP is essential.
Questions you might have
How do I find out if my agent can pull all open jobs using list_jobs? +
Yes, list_jobs returns the titles and IDs for every active opening. This is your starting point when you want to know what roles are currently available in the system.
Can I use get_candidate to check an applicant's status? +
Absolutely. get_candidate pulls their full profile, which includes their current application stage and contact history. It’s better than just looking at the main dashboard.
What is the difference between list_departments and list_users? +
Departments define business units (like 'Marketing' or 'Engineering'), while list_users lists actual people who are logged into the account. One defines the function, the other defines the person.
How do I track where candidates came from using list_sources? +
list_sources shows you all the channels—like 'LinkedIn' or 'Referral'—that applicants used to apply. It’s essential for measuring your recruiting effort.
How do I verify my connection status using the `get_me` tool? +
It returns your current authenticated user information. This confirms that your AI agent has successfully connected and is authorized to access the JobScore data for your account.
What job details can I retrieve when I use `get_job`? +
You get comprehensive data including the full job description, specific requirements, and identifiers for the hiring team. This lets you pass detailed information about a single opening to your workflow.
How do I monitor all applicants in my pipeline using `list_candidates`? +
This tool provides a list of every candidate, including their name, current stage in the process, and unique ID. It's essential for quickly surveying your entire talent pool.
Can I identify who is involved with hiring using `list_hiring_teams`? +
Yes, this lists all associated hiring teams, helping you pinpoint specific recruiters and managers tied to certain roles. It's key for coordinating job-specific personnel.
How do I get JobScore API credentials? +
Log in to your JobScore account, navigate to Admin > Integrations, and generate a Personal Access Token.
Does it support departments and locations? +
Yes, you can list all configured departments and office locations using this MCP.
Can I see candidate details? +
Yes, the list_candidates and get_candidate tools provide access to your applicant data.
We've already built the connector for JobScore. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 10 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.