Provkeep in your AI assistant

Ask Claude, Claude Code or Cursor what a state or the FDA published about a peptide. The answer is the sentence itself, its source and the date we read it.

Addresshttps://provkeep.com/mcp

Free with an account: 300 lookups a month, no card. Make a free account

Claude, on the web and the desktop app

  1. Open Settings, then Connectors, and choose Add custom connector.
  2. Name it Provkeep and paste https://provkeep.com/mcp. Leave the advanced settings empty.
  3. Choose Connect. A Provkeep page opens: sign in, or make a free account.
  4. Choose Allow. Claude now lists Provkeep's tools; the ones that write are marked as writing.

On a Team or Enterprise plan, an owner adds the connector once for the organisation and each person then connects with their own Provkeep sign in.

Claude Code

Add it from your terminal, then sign in from inside Claude Code.

claude mcp add --transport http provkeep https://provkeep.com/mcp
  1. In Claude Code, type /mcp and choose provkeep.
  2. Your browser opens the Provkeep sign in. Choose Allow, and return to the terminal.

Cursor

Add this to ~/.cursor/mcp.json, or to .cursor/mcp.json in one project. Cursor shows a sign in button beside Provkeep in its MCP settings.

{
  "mcpServers": {
    "provkeep": { "url": "https://provkeep.com/mcp" }
  }
}
With a key instead of signing in

Make a key in Settings, Keys, and send it as a header.

{
  "mcpServers": {
    "provkeep": {
      "url": "https://provkeep.com/mcp",
      "headers": { "Authorization": "Bearer pk_live_your_key" }
    }
  }
}

Your own code, or a company's agent

The same address takes a key from Settings, Keys. One request per question; there is no session to open first.

curl https://provkeep.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "Authorization: Bearer $PROVKEEP_KEY" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"lookup_rules",
                 "arguments":{"product":"BPC-157","state":"OH"}}}'

The order API at /developers is unchanged, and is still the way a checkout checks every order.

What the assistant gets back

Ask “What has Ohio published about BPC-157?” and this is the text Provkeep returns, built as this page loaded.

lookup_rulesproduct BPC-157, state OH
Ohio: BPC-157

What Ohio's own sources say, naming BPC-157 (1):
1. "Additionally, peptides such as BPC-157 and other bulk drug substances in category 2 and 3 (see FDA guidance ) cannot be compounded because it violates federal and state law."
   OH pharmacy board: Ten Common Prescriber Clinic and Medical Spa Violations, last read 2026-11-20
   https://www.pharmacy.ohio.gov/documents/pubs/special/ivtherapy/ten%20common%20prescriber%20clinic%20and%20medical%20spa%20violations.pdf

What we read in Ohio: We read Ohio's boards and laws: 4 of 4 sources answered on the latest reading, 2026-11-20.

Federal (applies in every state):
1. "BPC-157 Compounded drugs containing BPC-157 may pose risk for immunogenicity for certain routes of administration and may have complexities with regard to peptide-related impurities and active pharmaceutical ingredient (API) characterization."
   FDA, same page, table headed "Bulk drug substances nominated but withdrawn": previously in category 2, withdrawn by the nominators
   https://www.fda.gov/drugs/human-drug-compounding/certain-bulk-drug-substances-use-compounding-may-present-significant-safety-risks
HHS's 503A peptide policy lists BPC-157 in its Appendix A. Its 10 conditions, quoted: https://provkeep.com/hhs-peptide-policy-conditions

On provkeep.com: https://provkeep.com/states/ohio/peptides

Reading dated 2026-11-21. Rules change, so a kept copy of this answer goes stale: ask Provkeep again for a later reading rather than storing this one.
Provkeep reports what each source published. This is input for a qualified person. It is not legal advice, and it does not decide whether an order should go ahead.

A state with nothing on record says so in those words, with how many of its sources answered, and adds that nothing on record is not permission.

The tools

One answered question is one lookup. A question we could not answer, a product we do not read, or a call refused for the monthly limit counts for nothing.

ToolWhat it doesLookups
lookup_rulesLook up a product's rules in a state1
precheck_orderPre-check an order's products against a state1
nonresident_licensingNon-resident pharmacy licensing in a state1
list_sourcesWhat Provkeep reads in a state0
list_productsProducts Provkeep reads rules for0
account_usageYour Provkeep plan and lookups this month0
record_orderRecord an order in Provkeep (Record plan)0
record_shipmentRecord which lots shipped on an order (Record plan)0
list_auditsYour sealed audits (Record plan)0
what_needs_attentionWhat needs your attention0
list_ordersYour orders0
get_orderOne order in full0
list_changesChanges on the pages Provkeep reads0
list_watched_productsProducts you watch0
hhs_conditionsThe HHS 503A peptide conditions0
list_lotsYour lots and certificates (Record plan)0
create_lotAdd a lot (Record plan)0
record_lot_datesRecord a lot's expiry and beyond-use dates (Record plan)0
set_watched_productsChange the products you watch (Record plan)0

The tools marked Record plan read or change your lots, record orders, or read your sealed audits, and need that plan. Tools that write are marked as writing, so your assistant can ask you first.

Some things stay on provkeep.com, signed in: confirming a certificate, because a person must look at the file; making an audit; billing; your team; your keys; and closing the account.

Lookups a month

PlanPriceLookups a month
Free accountNo card300
MCP$19 a month3,000
Watch$69 a month5,000
Record$149 a month10,000

Lookups reset on the first of each month, UTC. Monthly billing only. See pricing for what else each plan includes.

What it never does

No verdict

It quotes what a source published. It never says an order or a product is allowed, and it never decides whether an order goes ahead. A qualified person does that.

Ask again, never store

Every answer carries the date it was read and asks the assistant to look again rather than keep a copy, because rules change and a kept answer goes stale.

No patient data

No tool takes a name, address, email, phone or date of birth. A product and a state is all a lookup needs.

When something goes wrong

The assistant says it needs to sign in

The connection has no sign in or key yet, or the key was revoked. Connect again, or make a new key in Settings, Keys. A sign in shows there as a key named for the app, and revoking it disconnects that app.

It says the monthly lookups are used

Nothing was looked up, so that answer says nothing about the product. Lookups reset on the first of the month, or move to a plan with more in Settings, Billing.

It says Provkeep does not read that product

It lists the products we do read. Nothing was counted.