← All servers

Finekot API

warnings

api.finekot.com

89 pay-per-call tools for agents: screenshots, scraping, PDF, OCR, TTS, STT, invoices, KYC, utils

https://api.finekot.com/mcpWebsiteNo authMCP 2025-11-25last checked 3 Nov 2026spoke MCP on 1 of 1 check (30 days)initialize in 131 ms

Last checked 3 Nov 2026

  • ✓Answered the MCP handshake (MCP 2025-11-25)
  • ✓Auth detected: No auth
  • ✓Lists 91 tools
  • !1 warning
  • ✓Spoke MCP on 1 of 1 check (30 days)

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✓Claude CodeConnects

The endpoint answers an anonymous handshake, so no credential is needed.

claude mcp add --transport http finekot-api https://api.finekot.com/mcp

Claude Code docs · read on 2026-08-30

✓Claude (claude.ai & Desktop)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Connectors → Add custom connector, then paste https://api.finekot.com/mcp.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✓ChatGPTConnects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://api.finekot.com/mcp.

ChatGPT docs · read on 2026-08-30

✓CursorConnects

The endpoint answers an anonymous handshake, so no credential is needed.

{
  "mcpServers": {
    "finekot-api": {
      "url": "https://api.finekot.com/mcp"
    }
  }
}

Cursor docs · read on 2026-08-30

✓VS Code (Copilot)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

{
  "servers": {
    "finekot-api": {
      "type": "http",
      "url": "https://api.finekot.com/mcp"
    }
  }
}

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 3 Nov 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme
No auth
Protected-resource metadata
✕Not found

Without it a client has to guess where the authorization server lives.

Anonymous access
Handshake succeeds; 91 tools listable
Credentials demanded in prose
✕csv_convert, entity_extract, weather, pdf_sign, e_invoice

These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error.

What the probe found

warningTools needing credentials are listed without a challenge

5 of the 91 tools listed anonymously say in their own descriptions that they need an account or a key (csv_convert, entity_extract, weather, pdf_sign, e_invoice), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.

No server card

Neither the reserved <endpoint>/server-card location nor the domain's /.well-known/ai-catalog.json describes this endpoint (SEP-2127), so a client that discovers servers by domain will not find it.

Tools

accountbank_statement_parsebarcodebase64browsercaptionchange_monitorchart_renderclassifycolor_palettecompany_verifycompresscontract_clause_extractcron_explaincsv_convertdenoisedetect_langdiagram_renderdoc_convertdoc_redactdocx_gendomain_healthe_invoiceemail_verifyembedentity_extractexif_stripextract_jsonfile_type_detectfxhashholidayshtml_pdfiban_validateimage_moderateinvoice_3way_matchinvoice_parseip_geojwt_toolslib_docslink_previewllms_txtmath_evalmcp_hostmd_convertmemorynews_briefocrog_imagepaper_searchpdf_signpdf_textpdf_toolsphone_validateprofanity_filterprompt_guardpurchase_order_extractqrreadability_scoreregex_testremove_backgroundresume_parserewritesanctions_screenscreenshotsemantic_searchseo_auditseo_metaservicesspeech_to_textsql_lintsubtitlessummarizetable_extracttext_difftext_to_speechtranslatetz_convertunit_convertuptimeurl_safetyurl_to_markdownuuidvat_checkvideo_clipvin_decodewatermarkweatherweb_answerweb_searchwebhook_relay

Contract history

3 Nov 2026first recorded contract

Watch this server

Save its public contract as a baseline and manage breaking-change email alerts.

Set up a watch

Route it through the gateway

Put this endpoint behind one find_tools / call_tool pair with the rest of your servers. Part of Pro.

Add to my gateway

Own this server?

Sign in to claim this listing by proving control of its host.

Sponsor this listing

Pins it in a sponsor slot on the directory front page for 30 days, labelled Sponsored.

Sign in to sponsor · $39 / 30 days

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

MCP status badge for Finekot API
[![MCP status](https://mcpi.app/servers/finekot-api/badge.svg)](https://mcpi.app/servers/finekot-api)