Planned: connect your assistant

The planned Klarseal MCP server would expose your own orders, certificates and invoices to the assistant you already use. Every tool would be read-only except two: preparing a renewal, which returns a checkout link, and opening a support thread.

Specified, not deployed

https://mcp.klarseal.com/mcp is reserved and does not answer requests. The server is planned, not available, and no opening date is promised. It would need a customer sign-in, which Klarseal does not offer, because that is where you would grant a scope and take it back. Orders are followed through the status link in the emails Klarseal sends. Nothing below describes a running service — it describes the contract being built, so you can judge the boundaries before you connect anything.

Tools

list_orders: Your orders, newest first: order number, product, the customer-facing status label and the date it last changed.
get_order_status: One order: status label, the sentence saying what happens next, and who acts (you, Klarseal or Certum). It returns no date or time window.
list_certificates: Issued certificates with subject, serial number, the validity window and the order they came from.
get_expiry: Days remaining on one certificate and its expiry date, formatted DD.MM.YYYY.
get_invoice: An invoice as a download link plus its JSON twin — net, MVA, total and the order it belongs to.
prepare_renewal: A checkout link for renewing an existing certificate. Charges nothing and commits you to nothing.
get_signing_instructions: The signtool command for your certificate: the subject name to match, the timestamp URL and the file type.
open_support_thread: Opens a support thread with the order attached and returns its reference so you can follow it.
get_identity_check_expectations: What Certum will ask the named person for, and which documents are involved. It cannot complete the check.

Seven of the nine only read. prepare_renewal returns a link andopen_support_thread starts a conversation — neither moves money, changes an order or touches a key.

Scopes

Read ordersorders:readOrder numbers, products, status history.
Read certificates and expirycertificates:readSubject, serial, validity window, days remaining.
Read invoicesinvoices:readInvoice documents and their JSON twin.
Prepare renewalsrenewals:prepareReturns a checkout link. Cannot pay.
Open support threadssupport:writeStarts a thread. Cannot change an order.

Consent would be per scope, granted on the OAuth screen one at a time and revocable there. Every call would be written to an audit log. No scope grants payment, signing, identity verification or revocation — those five limits are listed in full on thedevelopers hub.

What it looks like from the other side

The point of the server would be that a one-line question gets a one-line answer. The assistant reads; you still decide, pay and sign.

A conversation, end to end

you  → is our signing certificate still valid?
mcp  → get_expiry() → active until 14.03.2027 (187 days)
you  → renew it
mcp  → prepare_renewal() → checkout link, nothing charged
you  → (you pay, you sign)

Connecting a client

These are the configurations the server is being built to accept. They will not connect to anything until the endpoint opens, and you would sign in on the consent screen rather than pasting a key into a config file.

Claude · claude_desktop_config.json

{
  "mcpServers": {
    "klarseal": {
      "url": "https://mcp.klarseal.com/mcp",
      "scopes": ["orders:read",
                 "certificates:read",
                 "renewals:prepare"]
    }
  }
}

ChatGPT · connector settings

Settings → Connectors → Create

  Name         Klarseal
  Server URL   https://mcp.klarseal.com/mcp
  Auth         OAuth

Scopes are chosen on Klarseal's consent
screen, not in ChatGPT.

Cursor · ~/.cursor/mcp.json

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "klarseal": {
      "url": "https://mcp.klarseal.com/mcp"
    }
  }
}

IDE agents and anything else

Transport   Streamable HTTP
Endpoint    https://mcp.klarseal.com/mcp
Auth        OAuth 2.1, authorisation code with PKCE
Discovery   https://mcp.klarseal.com/.well-known/oauth-protected-resource
Scopes      orders:read certificates:read invoices:read
            renewals:prepare support:write

In Claude Code the same server is added from the terminal withclaude mcp add --transport http klarseal https://mcp.klarseal.com/mcp. Klarseal is not affiliated with Anthropic, OpenAI or Cursor; these are configuration examples, not endorsements.

Want this the day it opens?

Tell us which assistant you use and what you would ask it about a certificate order. That is what decides which tool gets built carefully first.

Order certificate Read the status API spec

Questions about the server

Certificates are issued by Certum, a certificate authority on the EU Trusted List. An assistant reads what Klarseal knows about your order; it never talks to Certum for you.

Can I connect an assistant today?

Not yet. https://mcp.klarseal.com is a reserved host name that does not answer requests, and there is no consent screen to grant a scope on, because Klarseal does not offer the customer sign-in it needs. The server is planned and no opening date is promised. This page is the contract it is being built against — the tool names, the returns and the five scopes are fixed before the first connection is possible.

Can the assistant order, pay for or renew a certificate on its own?

No. prepare_renewal returns a checkout link and nothing more: the payment, the checkout acknowledgements and the authorisation by someone who can sign for the company are completed by a person. There is no scope that authorises a charge, and one will not be added — an assistant that could spend money is not the product.

What will Klarseal see when my assistant calls a tool?

The call, not the conversation. The audit log would record which assistant called which tool under which scope, against which order, and when. The text you exchanged with your assistant would never reach Klarseal, because the client sends the tool call and its arguments — nothing else.

How will I take access away again?

On the same consent screen, which would list every connected assistant with the scopes it holds. Revoking one scope would narrow what it can call; revoking the assistant would end its access outright, and any token it already holds would stop working. Consent would be granted one scope at a time, so nothing is bundled.

Which clients will this work with?

Any MCP client that supports a remote server over streamable HTTP with OAuth — Claude, ChatGPT, Cursor and the IDE agents that speak the same protocol. Klarseal is not affiliated with any of them, and the snippets on this page are configuration examples rather than an endorsement.