# Kamy (remote · mcp.kamy.dev)

Document API for AI-native software: render PDFs, e-sign, PAdES-seal, and verify.

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- remote · `mcp.kamy.dev`: 69/100 (this document), [markdown](https://verifymcp.io/servers/dev-kamy-kamy/mcp.md), [page](https://verifymcp.io/servers/dev-kamy-kamy/mcp)

## Channel facts

- Endpoint: `https://mcp.kamy.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-04.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1695 tokens (~121/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 97% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http dev-kamy-kamy https://mcp.kamy.dev/mcp
```

### Codex

```toml
[mcp_servers.dev-kamy-kamy]
url = "https://mcp.kamy.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-kamy-kamy": {
      "type": "remote",
      "url": "https://mcp.kamy.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-kamy-kamy --url https://mcp.kamy.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-kamy-kamy:
    url: "https://mcp.kamy.dev/mcp"
```

### Other

```json
{
  "mcpServers": {
    "dev-kamy-kamy": {
      "type": "http",
      "url": "https://mcp.kamy.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 67, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 64)

First indexed and scored.

## MCP tools (14)

### `list_templates` (~20 tokens)

List templates

List Kamy's public system PDF templates. No authentication required.

### `get_template_schema` (~83 tokens)

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 right fields with the right types instead of guessing. No authentication required.

Input parameters:

- `slug` (string, required): Template slug — e.g. 'invoice', 'receipt', 'uae-tax-invoice'.

### `render_pdf` (~74 tokens)

Render PDF

Render a PDF from a Kamy template and data when a Kamy API key is configured. Without a key, returns dashboard setup instructions.

Input parameters:

- `data` (object, required): Data to populate the template
- `format` (string)
- `template` (string, required): Template slug (e.g., 'invoice') or template UUID

### `validate_payload` (~98 tokens)

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 received, allowed values, an example) so you can fix the data before render_pdf. Requires a Kamy API key.

Input parameters:

- `data` (object, required): The data payload to validate against the template schema.
- `template` (string, required): Template slug (e.g. 'invoice') or template UUID.

### `extract_document` (~149 tokens)

Extract document (Kamy Ingest)

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 extraction matches the source. Use this when an agent needs to read an inbound document and act on it.

Input parameters:

- `source_base64` (string): Base64-encoded PDF bytes. Use when the source isn't publicly fetchable.
- `source_url` (string): Public URL to a PDF (preferred). One of source_url or source_base64 is required.
- `template` (string, required): Predefined template id. invoice/receipt for AP and POS docs, contract for legal agreements, id_document for passports/IDs, generic_form for anything else.

### `ask_kamy` (~74 tokens)

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.

Input parameters:

- `question` (string, required): The question to ask Kamy about — how to render a template, why a render failed, what plan to pick, etc.

### `install_sdk` (~50 tokens)

Install Kamy SDK

Get install commands and setup code for @kamydev/sdk in your framework.

Input parameters:

- `framework` (string, required): The framework the user is working with
- `packageManager` (string): Package manager to use

### `generate_integration_code` (~49 tokens)

Generate integration code

Generate copy-paste integration code for a specific Kamy template and framework.

Input parameters:

- `framework` (string, required): Target framework
- `template` (string, required): Template slug (e.g., 'invoice')

### `create_signature_request` (~572 tokens)

Send for e-signature

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.

Input parameters:

- `authMethod` (string): Identity-verification mode. `link` (default) — possession of the secret URL is the only check. `email_otp` — sign page renders a 6-digit OTP gate; code emailed to `signerEmail`. `sms_otp` — same gate…
- `ccEmails` (array): Up to 10 observer addresses CC'd on the invite and the completion notice. Not signers themselves.
- `expiresIn` (integer): How long (seconds) the sign link stays valid. Defaults to 30 days. Min 1 hour, max 30 days.
- `message` (string): Optional message rendered in the email invitation body.
- `placedFields` (array): Up to 100 sender-defined fillable fields stamped onto the PDF at sign time. Use for flat PDFs that don't ship AcroForm widgets. Names must be unique.
- `position` (object): Optional sender-chosen signature placement in PDF points (72 dpi, origin bottom-left). Defaults to bottom-right of the last page sized 220×64 pt; when omitted, the signer can drag the placeholder on…
- `reminderCadenceHours` (integer): When set (24–168), the auto-reminder cron resends the invite every N hours while the request stays pending, up to 3 reminders. Omit for no auto-reminders.
- `renderId` (string, required): Render UUID returned by render_pdf or any /v1/render call. The render's PDF is the document the signer will receive.
- `requireStamp` (boolean): Require the signer to upload a company stamp / seal alongside their personal signature (UAE, KSA, JP, KR, IN, CN B2B workflows). Server refuses to seal without one.
- `signOnEveryPage` (boolean): When true, the server stamps the signer's signature on every page of the source PDF instead of only the configured position. Common B2B contract pattern.
- `signatureTemplateId` (string): Apply a signature template's defaults (placedFields, position, message, expiresIn, ccEmails). Request-level fields override the template.
- `signerEmail` (string, required): Recipient email address.
- `signerName` (string, required): Recipient full name. Must be typed verbatim by the signer to confirm intent.
- `signerPhone` (string): E.164 phone number. Required when `authMethod` is `sms_otp`; ignored otherwise. Example: `+14155551234`.

### `list_signature_requests` (~52 tokens)

List signature requests

List signature requests created by the configured Kamy account, newest first. Without a key, returns dashboard setup instructions.

Input parameters:

- `limit` (integer): Default 50.
- `offset` (integer): Default 0.

### `get_signature_certificate` (~112 tokens)

Get Certificate of Completion URL

Returns the authenticated download URL for a signature request's Certificate of Completion PDF — the process audit trail (invite → opened → consent → signed, with IP / user-agent) that legal teams expect. Only available after the request reaches a terminal state. Without a key, returns dashboard setup instructions.

Input parameters:

- `signatureRequestId` (string, required): ID of the signature_request to fetch the Certificate of Completion for. Must be in a terminal state (signed / declined / delegated / voided / expired); pending requests return 409.

### `pki_sign_pdf` (~248 tokens)

PKI-sign PDF

Cryptographically sign an existing render with PAdES when a Kamy API key is configured. Without a key, returns dashboard setup instructions.

Input parameters:

- `location` (string): Optional /Sig dictionary Location.
- `reason` (string): Optional /Sig dictionary Reason — surfaced in Acrobat's signature panel. ASCII-coerced server-side.
- `renderId` (string, required): Render UUID returned by render_pdf or any /v1/render call. The PDF will be sealed with a Kamy-issued X.509 leaf certificate.
- `signerEmail` (string): Override the signer email. Defaults to the account's email.
- `signerName` (string): Override the signer display name. Defaults to the account's full_name.
- `withRevocationInfo` (boolean): When false, skip embedding the Kamy CA CRL into the PKCS#7 SignedData (PAdES-B-T instead of B-LT). Online verifiers can still fetch the CRL via the Distribution Point on the leaf cert. Default: true.
- `withTimestamp` (boolean): When false, skip the RFC 3161 timestamp call (PAdES-B-B instead of B-T). Default: true.

### `verify_pdf_signature` (~81 tokens)

Verify PDF signature

Compute the kamy.dev/verify URL for a PDF without making a Kamy API call. Pass the PDF as base64; the MCP Worker hashes it in-memory and does not store or forward it.

Input parameters:

- `pdfBase64` (string, required): Base64-encoded PDF bytes. The MCP Worker hashes the file in-memory and does not store or forward it.

### `get_api_key_instructions` (~33 tokens)

Get API key instructions

Return step-by-step instructions for creating a Kamy API key in the dashboard. Does not open the browser.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-kamy-kamy/mcp#diagnostics

## Score history

- 2026-08-04: 69
- 2026-08-03: 69
- 2026-08-02: 68
- 2026-08-01: 68
- 2026-07-31: 67
- 2026-07-30: 67
- 2026-07-29: 66
- 2026-07-28: 66
- 2026-07-27: 65
- 2026-07-26: 64

## Links

- Remote endpoint: https://mcp.kamy.dev/mcp
- Repository: https://github.com/Kamy-Development/kamy-plugin
- Changelog RSS feed: https://verifymcp.io/servers/dev-kamy-kamy/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-kamy-kamy/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/dev-kamy-kamy/mcp