mcpcost

so.inkly/inkly

Inkly

Is the Inkly MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-14.

Send, track, and manage documents for eSignature: templates, drafts, signing status, signed PDFs.

needs auth probed 2026-11-14 · HTTP 401 · Bearer

Streamable HTTP error: Error POSTing to endpoint: {"error":{"code":"invalid_api_key","message":"Provide a valid API key in the Authorization header.","param":nu
Endpoint
https://www.inkly.so/mcp (streamable-http)
Host
www.inkly.so
Getting access
OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://www.inkly.so/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server ovulbebmovavtctdbkct.supabase.co, PKCE S256, grants authorization_code, refresh_token.
Read from the server's public OAuth metadata, without a token. Method.
Repository
https://github.com/inkly-so/inkly-mcp
Website
https://www.inkly.so/e-signature-mcp
Registry
active, updated 2026-11-13 · registry entry

Compare this server with others.

More servers

Servers that mention inkly or esignature or documents.

Badge for the README

mcpcost: needs auth

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Atom feed

A mail when this server changes

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

For the publisher

Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.