jobhunt.app/mcp

Security and reporting a vulnerability

How JobHunt limits access to your account and how to report a security problem.

Updated

Step by step

  1. Report a problem privately

    Email security@jobhunt.app. Describe what you found, the steps that reproduce it, and which page, tool or command it affects. Use a test account of your own; do not read, change or keep anyone else's data. Do not include passwords, tokens or other people's information in the report. The same address is listed in https://jobhunt.app/.well-known/security.txt, with the support contact form as a second route.

  2. How connections are limited

    Assistants and the command connect with OAuth and a one-use code checked by PKCE. Each connection receives only the permissions you approved, and you can disconnect it from Integrations in the sidebar. API keys are limited to the permissions they were created with, can expire, can be revoked, and are delivered encrypted to the recipient that asked for them. Text inside a job posting or message is treated as content, not as an instruction to your agent. Any assistant can introduce itself to JobHunt, by design; nothing is connected until you approve it, and the approval screen shows an unknown app's name as its own claim, in quotes, beside the host it returns you to, with a note that JobHunt cannot confirm the name.

  3. What stays under your control

    Your workspace is private unless you choose to share a document or page. You can export your account data, and you can erase your account and its saved work from the account pages.

  4. What to expect

    We aim to acknowledge reports within 5 working days. JobHunt does not run a bounty programme.

What happens next

A security report reaches JobHunt without being posted publicly.

Reports are accepted at security@jobhunt.app and through the support contact form.

Troubleshooting

If you do not hear back within 5 working days, or the email bounces, use the support contact form at https://jobhunt.app/support/contact and say only that you have a security report, without the details. Do not post details of an unfixed problem in public.

Technical detailsAPI operations and permissions

These operation details and permissions come from the API contract.

READget_connected_account

Identify the JobHunt account connected by these credentials. The opaque account ID stays unchanged across renaming, reconnection and token refresh. This does not select or change a resume contact profile.

GET /api/v1/journey/get_connected_account

DECLARED PERMISSIONS

  • read:profile
View input, output and access requirements →