Developers · MCP

Let your AI client run the scanner, not guess the answer.

The Model Context Protocol is how tools talk to AI clients like Claude, Cursor, and custom agents. ProofKit’s endpoint speaks the core of it - initialize, tools/list, tools/call - over plain HTTP. Three tools work with no token at all: scan a resume against the 23-check rubric, search live job listings, list templates. Three more act on your saved resumes and need a bearer token you mint below while signed in.

Get my MCP token See the tools

Endpoint: https://proofkit.store/mcp (POST JSON-RPC 2.0).

The tools

Six calls. Three are public.

Schemas are served live by tools/list - this table is the human version.

Tool	Token?	What it does
`proofkit_scan_resume`	No	Runs the deterministic 23-check ATS scan: score, 5 category scores, and every failed check with its fix. No AI involved.
`proofkit_search_jobs`	No	Live remote-friendly listings from a public board: title, company, tags, salary, apply URL. Cached 5 minutes.
`proofkit_list_templates`	No	The 15 template ids, which are free and which need Pro.
`proofkit_list_resumes`	Yes	Your saved resumes: id, title, template, last updated.
`proofkit_read_resume`	Yes	One resume by id, including its full data.
`proofkit_write_resume`	Yes	Creates a saved resume on your account. Free plan keeps its 1-resume cap - the tool tells you instead of silently failing.

Your token

Mint a bearer token, paste it in your client.

Client config (bearer header form):

{
  "mcpServers": {
    "proofkit": {
      "url": "https://proofkit.store/mcp",
      "headers": { "Authorization": "Bearer PASTE_YOUR_TOKEN" }
    }
  }
}

If your client only accepts a URL with no custom headers, it cannot attach the bearer yet - the three public tools still work without one.

What this is - and isn’t. It is a small, honest subset of MCP over HTTP: initialize, tools/list, tools/call, and ping. It is not a full session-management layer, there is no OAuth dance, and there is no per-token dashboard. A token is a bearer secret: anyone holding it can call the resume tools as you for 90 days. Don’t commit it, don’t paste it into a public chat. We can’t revoke a single token early, so treat leaks seriously and write to hello@proofkit.store if you need help rotating.

Questions

What people ask about the endpoint.

What works without signing in?

Scanning a resume, searching jobs, and listing templates are public - point any MCP client at the endpoint and call them. The resume list/read/write tools need the bearer token because they touch your account.

Will it change my resume in the builder?

No. proofkit_write_resume creates a saved copy in your account list; it never overwrites a resume, and it does not touch the draft stored in your browser. Edit it in the builder afterwards if you want.

Why does the scan beat asking the model directly?

Because it is the same deterministic rubric the site runs - the one behind the score, the export header, and the proof link. A model guessing at “ATS rules” gives you a different answer every time; this tool gives you the same 23 checks every time.

Scan first. Automate second.

The endpoint is for workflows. The builder is where the resume actually gets better.

Open the builder Plans and quotas