Kamy
REMOTE · MCP.KAMY.DEV · SCANNED AUG 3
Document API for AI-native software: render PDFs, e-sign, PAdES-seal, and verify.
Available components
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. How we score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.kamy.dev
claude mcp add --transport http dev-kamy-kamy https://mcp.kamy.dev/mcp
[mcp_servers.dev-kamy-kamy] url = "https://mcp.kamy.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-kamy-kamy": {
"type": "remote",
"url": "https://mcp.kamy.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-kamy-kamy --url https://mcp.kamy.dev/mcp --transport streamable-http
mcp_servers:
dev-kamy-kamy:
url: "https://mcp.kamy.dev/mcp" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +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.
- 1 Aug 26 +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.
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +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.
- 28 Jul 26 +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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://mcp.kamy.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=kamy.dev | CN=WE1,O=Google Trust Services,C=US | 19 Jun 2026 | 17 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | f3e0b7a588778c4513d75a92fb125251 |
| SANs: kamy.dev, mcp.kamy.dev, *.mcp.kamy.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of mcp.kamy.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| kamy.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.kamy.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.kamy.dev/mcp | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
ask_kamy Ask Kamy ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | The question to ask Kamy about — how to render a template, why a render failed, what plan to pick, etc. |
No output schema declared.
No examples provided.
create_signature_request Send for e-signature ~572
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | Recipient email address. |
| signerName | string | yes | 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`. |
No output schema declared.
No examples provided.
extract_document Extract document (Kamy Ingest) ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Predefined template id. invoice/receipt for AP and POS docs, contract for legal agreements, id_document for passports/IDs, generic_form for anything else. |
No output schema declared.
No examples provided.
generate_integration_code Generate integration code ~49
Generate copy-paste integration code for a specific Kamy template and framework.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | yes | Target framework |
| template | string | yes | Template slug (e.g., 'invoice') |
No output schema declared.
No examples provided.
get_api_key_instructions Get API key instructions ~33
Return step-by-step instructions for creating a Kamy API key in the dashboard. Does not open the browser.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_signature_certificate Get Certificate of Completion URL ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| signatureRequestId | string | yes | 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. |
No output schema declared.
No examples provided.
get_template_schema Get template schema ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Template slug — e.g. 'invoice', 'receipt', 'uae-tax-invoice'. |
No output schema declared.
No examples provided.
install_sdk Install Kamy SDK ~50
Get install commands and setup code for @kamydev/sdk in your framework.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | yes | The framework the user is working with |
| packageManager | string | — | Package manager to use |
No output schema declared.
No examples provided.
list_signature_requests List signature requests ~52
List signature requests created by the configured Kamy account, newest first. Without a key, returns dashboard setup instructions.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | Default 50. |
| offset | integer | — | Default 0. |
No output schema declared.
No examples provided.
list_templates List templates ~20
List Kamy's public system PDF templates. No authentication required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pki_sign_pdf PKI-sign PDF ~248
Cryptographically sign an existing render with PAdES when a Kamy API key is configured. Without a key, returns dashboard setup instructions.
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | — | Optional /Sig dictionary Location. |
| reason | string | — | Optional /Sig dictionary Reason — surfaced in Acrobat's signature panel. ASCII-coerced server-side. |
| renderId | string | yes | 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. |
No output schema declared.
No examples provided.
render_pdf Render PDF ~74
Render a PDF from a Kamy template and data when a Kamy API key is configured. Without a key, returns dashboard setup instructions.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Data to populate the template |
| format | string | — | — |
| template | string | yes | Template slug (e.g., 'invoice') or template UUID |
No output schema declared.
No examples provided.
validate_payload Validate payload ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | The data payload to validate against the template schema. |
| template | string | yes | Template slug (e.g. 'invoice') or template UUID. |
No output schema declared.
No examples provided.
verify_pdf_signature Verify PDF signature ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pdfBase64 | string | yes | Base64-encoded PDF bytes. The MCP Worker hashes the file in-memory and does not store or forward it. |
No output schema declared.
No examples provided.