Name: Kamy
Author: dev.kamy

Tools observed via MCP handshake

list_templates — List Kamy's public system PDF templates. No authentication required.
get_template_schema — Fetch the JSON Schema (exact data shape) and a copy-pasteable sample payload for a Kamy system template by slug. Call this before render_pdf so you fill the rig
create_template — Create a new custom PDF template owned by this account: a name, a unique slug, a Handlebars/HTML body, and optional CSS and JSON Schema. The slug is what render
update_template — Edit an existing custom template's DRAFT — name, html, css, schema, tags, visibility — addressed by UUID or slug. Only the fields you pass are changed. Cruciall
publish_template — Make a template version live for rendering. Called with no `version`, it snapshots the current draft into a new version and points published_version at it — thi
rollback_template — Revert a template after a bad release: repoints published_version at the version you name, so every subsequent render immediately serves that snapshot again. Pr
list_template_versions — List a template's immutable version snapshots, newest first, as { id, version, createdAt }. This is where the version number that publish_template and rollback_
get_template_version — Fetch one template version snapshot in full — html, css, schema, createdBy, createdAt — exactly as it was frozen when that version was cut. Use list_template_ve
render_pdf — Render a PDF from a Kamy template and data, and wait for it. This is the default document tool: it blocks until the file exists and hands back { id, url, bytes,
render_docx — Render an editable Word (.docx) document from a Kamy template and data. Takes the same { template, data } payload as render_pdf but produces a different contain
render_pptx — Build a PowerPoint (.pptx) deck from a slide spec: an ordered array of slides, each tagged with one of five fixed layouts (title, bullets, two-column, table, qu
render_xlsx — Build an Excel (.xlsx) workbook from a sheet spec: columns with keys, row objects keyed to those columns, optional Excel number formats and a formula-aware tota
render_html — Compile a Kamy template — or raw Handlebars source you pass inline — against a data payload and get the rendered HTML string back. No browser runs, no PDF is pr
convert_document — Convert a file you already hold — .docx, .xlsx or .csv — into a PDF, preserving its existing content. Pass the bytes base64-encoded together with the original f
merge_pdfs — Concatenate 2–20 existing renders into a single new PDF, in exactly the order the ids are given. Both the inputs and the output are Kamy render ids, so this is
split_pdf — Extract page ranges from one existing render into separate new PDFs — the inverse of merge_pdfs. Each range you pass produces its own render, returned in the sa
edit_pdf — Modify an existing PDF: fill AcroForm fields by name, stamp text at absolute coordinates, or paint opaque boxes over regions. Operations apply in the order give
upload_file — Store an image, font or PDF in the account's asset bucket and get back a `kamy://asset/<id>` reference you can drop anywhere inside a render_pdf / render_html d
get_upload — Look up a stored asset by its upload id: filename, contentType, sizeBytes, status, its `kamy://asset/<id>` reference, and a freshly signed downloadUrl valid for
validate_payload — Dry-run a render payload against a template's schema WITHOUT producing a PDF or using quota. Returns per-field self-healing errors (expected type, value receive
extract_document — Extract structured data from a PDF (invoice, receipt, contract, ID document, or any form). Returns the parsed JSON plus a public verify URL that proves the extr
ask_kamy — Ask Kamy Brain a question about Kamy usage, templates, plans, or errors. Sends the question to Kamy's public assistant endpoint and returns a paragraph answer.
create_signature_request — Send a previously rendered PDF to a signer for e-signature when a Kamy API key is configured. Without a key, returns dashboard setup instructions.
create_envelope — Send a single PDF to 2–10 signers as one envelope. This is the multi-signer counterpart to create_signature_request, which handles exactly one signer — the API
list_signature_requests — List signature requests created by the configured Kamy account, newest first. Without a key, returns dashboard setup instructions.
get_signature_certificate — Returns the authenticated download URL for a signature request's Certificate of Completion PDF — the process audit trail (invite → opened → consent → signed, wi
get_signature_request — Fetch one signature request by id, with the detail list_signature_requests leaves out: the placed_fields layout, signed_at plus signed_ip and signed_user_agent,
get_envelope — Fetch one multi-signer envelope with every recipient in signing order — each with a live sign_url, status, recipient_order, expires_at and last_reminded_at — pl
remind_signature — Resend the signature invitation email. Pass signatureRequestId to nudge one signer, or envelopeId to nudge every currently-pending recipient of an envelope — su
bulk_signature_requests — Fan one already-rendered PDF out to up to 100 independent signers in a single call — the 'send this NDA to everyone on the list' path. Each signer gets their ow
preview_field_placement — Check a placedFields layout against a real render's page geometry before anything is sent: no signature request is created, no email goes out, and no signature
list_signature_templates — List this account's reusable e-signature presets — saved field placements, default invite message, default link lifetime and CC list — newest first. These are s
get_signature_template — Fetch one e-signature preset in full, including the placed_fields array and position that list_signature_templates omits. Use it to inspect or copy an existing
pki_sign_pdf — Cryptographically sign an existing render with PAdES when a Kamy API key is configured. Without a key, returns dashboard setup instructions.
verify_pdf_signature — Turn PDF bytes you are holding into their SHA-256 digest and the matching kamy.dev/verify/{sha256} page URL. Purely local: the MCP Worker hashes the base64 in m
attest_artifact — Cryptographically sign an output your agent produced — a PDF, report, code patch, dataset, email — so a third party can later confirm those exact bytes are the
verify_attestation — Ask Kamy whether a SHA-256 digest has an attestation on record — the tool that actually returns a verdict. Takes a digest, not a file: if what you hold is a PDF
record_agent_action — Append one signed tool_call -> tool_result pair to a tamper-evident ledger. Call it after any consequential tool invocation — a payment, an outbound email, a wr
get_provenance_chain — Replay everything recorded under one run_id — artifacts from attest_artifact and calls from record_agent_action — in order, with each record's link to its paren
trace_record — Record one LLM call — prompt, output, provider, model, tokens, latency — into Kamy Trace, a signed retention ledger. Each record is hashed and signed at write t
trace_record_batch — Write up to 100 Kamy Trace records in one call. Reach for this over trace_record whenever you have more than a couple of buffered LLM calls to persist — it is o
trace_search — Query this account's Kamy Trace records, newest first, filtered by feature, status, provider, tag, or time window. Returns record metadata — model, tokens, late
verify_mcp_server — Detect when an MCP server changes its tool manifest after you adopted it — the 'rug pull' case, where a server you already trusted silently rewrites a tool's de
scan_tool_description — Heuristic pattern scan of MCP tool description text for prompt-injection tells — instructions addressed at the reading model, data-exfiltration hints, attempts
get_started — Everything needed to go from nothing to a rendered document in one call: the steps to create an API key in the dashboard, and — when you name a `framework` — th
get_account — Read everything about the authenticated Kamy account in one call: profile, plan and plan status, the plan's limits (renders per month, API keys, seats, custom t
list_renders — List the documents this account has already produced, newest first. This is how you find a PDF made earlier — in a previous turn, by a schedule, or by another p
get_render — Fetch one previously produced document by its render id, with a freshly signed download URL valid for the next hour. This is the recovery path for an expired li
get_render_pages — Rasterise every page of an existing render to a PNG image and return one signed 1-hour URL per page, with pixel width and height. Use this when a page has to be
extract_from_render — Read the text or the form fields back out of a document this account already rendered, without uploading anything. Pass type='text' (the default) for per-page t
render_async — Queue one PDF render and return immediately with { jobId, status: 'queued' } instead of waiting for the document. Choose this over render_pdf when blocking is n
get_job — Poll an asynchronous render job started by render_async. Returns { jobId, status } where status is 'queued', 'processing', 'completed' or 'failed'; on 'complete
render_batch — Render up to 100 documents in a single blocking call, each from its own template, HTML or URL, and get every result back in one response. Choose this over calli
create_schedule — Set up a recurring render: a cron expression, a template, and where each document goes. Use this instead of render_pdf when the user wants a document produced r
list_schedules — List this account's recurring render schedules, newest first, with the id needed to delete one. Use it to answer what is already automated before creating a dup
delete_schedule — Permanently delete a recurring schedule so it stops firing. There is no undo and no trash — recreate it with create_schedule if it is deleted by mistake, so con
create_webhook — Register an HTTPS endpoint that Kamy POSTs to when work finishes, so a long render or an e-signature does not have to be polled. Use this when the caller owns a
list_webhooks — List the webhook endpoints registered on this account, with the id needed to test one. Each row carries url, events, enabled, and lastDeliveryAt / lastStatus fr
test_webhook — Send a real test.ping event to a registered webhook endpoint — an actual outbound HTTP POST to whatever URL the user configured, signed like a genuine delivery.

when	check	result	http	latency	detail
3 h ago	mcp initialize	ok	200	35 ms	server kamy 1.5.0 · protocol 2025-06-18 · 59 tools
9 h ago	mcp initialize	ok	200	100 ms	server kamy 1.5.0 · protocol 2025-06-18 · 59 tools
16 h ago	mcp initialize	ok	200	29 ms	server kamy 1.5.0 · protocol 2025-06-18 · 59 tools
22 h ago	mcp initialize	ok	200	41 ms	server kamy 1.5.0 · protocol 2025-06-18 · 59 tools
29 h ago	mcp initialize	ok	200	94 ms	server kamy 1.5.0 · protocol 2025-06-18 · 59 tools
2 d ago	mcp initialize	ok	200	36 ms	server kamy 1.5.0 · protocol 2025-06-18 · 59 tools
2 d ago	mcp initialize	ok	200	30 ms	server kamy 1.5.0 · protocol 2025-06-18 · 59 tools
2 d ago	mcp initialize	ok	200	24 ms	server kamy 1.5.0 · protocol 2025-06-18 · 59 tools
2 d ago	mcp initialize	ok	200	44 ms	server kamy 1.5.0 · protocol 2025-06-18 · 59 tools
3 d ago	mcp initialize	ok	200	38 ms	server kamy 1.5.0 · protocol 2025-06-18 · 59 tools

Kamy

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from