List your agent

Temsor API — Turkey & EU business data

MCP server● Hosted · onlinev1.0.0

Turkey & EU business data: validation, sanctions screening, parsing, FX and fuel price history

What you can do with it

Share of each task's required capabilities it covers

Prefer a ready-made agent?

An MCP server is a connector for your own assistant. These finished products do the job for you: monitor prices.
All AI agents to monitor prices, ranked →

Similar tools

Listed for the same task: monitor prices

Reviews

No review yet. Used Temsor API — Turkey & EU business data? Be the first to help others choose.

What it does

Temsor API — Turkey & EU business data is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to one capability: price monitoring. That makes it a candidate for tasks such as monitor prices or compare products online.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.0.0
PriceNot in the registry
First seen26 Sept 2026
Last checked6d ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)

Hosted endpoint

  • https://api.temsor.com/mcp streamable-http

In Claude Code: claude mcp add --transport http temsor-api-turkey-eu-business-data https://api.temsor.com/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "temsor-api-turkey-eu-business-data": {
      "url": "https://api.temsor.com/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 1d ago

ONLINE Temsor API — Turkey & EU business data answered an MCP connection on 13 Nov 2026 and introduced itself as temsor API 1.0.0 (MCP protocol 2025-06-18).

43 tools offered to AI assistants

  • email_verify · Checks an e-mail address: syntax, whether the domain can actually receive mail, disposable and role-account detection, and typo correction. No SMTP probing. Most competitors connect to the target server and try RCPT TO, which sounds thoroug
  • iban_validate · Validates an IBAN from any of 70+ countries: checksum, country length and in-country account structure, and resolves the bank and branch codes. Most free libraries stop at the mod-97 checksum. That only says the digits are self-consistent —
  • pbx_audio_chunk · Notify an optional audio chunk / customer URI for a live or archived call (idle $0). Prefer customer storage URI. Temsor keeps a pointer; STT only while a call is active.
  • pbx_calls · List recent calls with transfer path crumbs — site + customer archive browser. GET /v1/pbx/calls?limit=20. Scoped by x-temsor-pbx-key when set. Idle $0. No DID sales.
  • pbx_calls_get · Get one call by id with transfer graph — customer detail drawer. GET /v1/pbx/calls/get?call_id=…. Scoped by x-temsor-pbx-key. found=false if missing. Idle $0.
  • pbx_calls_graph · Handoff graph + transfer edges — who→whom→where the promise stuck (moat). Idle $0. GET /v1/pbx/calls/graph?call_id=…&stuck_at=310. Returns path, path_tr (plain-language summary), edges, and raw transfers. Compounding asset for search/orches
  • pbx_dictionary · Managed SaaS domain dictionary (E4) — example packs thicken per pilot (tenant-scoped aliases). Boosts search + Fact extract. No invented premiums. GET /v1/pbx/dictionary?domain=hotel|pbx_provider|insurance|finance|energy|automotive|all (leg
  • pbx_dictionary_add · Add a synonym/alias (tenant-scoped or global demo) — E4 compounding thickens search boost + Fact extract. ≤60/hour/key → 429. Idle $0. No invented premiums. POST /v1/pbx/dictionary/add {term, alias, domain:hotel|pbx_provider|insurance|finan
  • pbx_events · Ingest call-ops events → open promises + transfer crumbs for search/orchestration. Optional HMAC. Idle $0 when no calls. Demo stores events in memory/file. Auth: omit, x-temsor-pbx-key, or x-temsor-signature = hex(HMAC-SHA256(api_key, body)
  • pbx_facts · List extracted facts (IMEI, room, tariff…) from the durable index — filter by call_id, kind, domain, q. GET /v1/pbx/facts?call_id=&kind=&domain=hotel|pbx_provider|insurance|finance|energy|automotive|all&q=&limit=50. Facts come from transcri
  • pbx_facts_get · Get one extracted fact by id — detail drawer for site + customer. GET /v1/pbx/facts/get?id=…. Scoped by x-temsor-pbx-key. found=false if missing. Idle $0. No DID sales.
  • pbx_index_partial · Upsert mid-call partial index (utterances → fact/promise hints). Path to ≤400ms whisper; ≤600/hour/key → 429; idle $0. POST /v1/pbx/index/partial {call_id, text?, speaker?, t_ms?, is_final?, live?, end_call?, promote?}. Streams partial STT
Show 31 more
  • pbx_index_partial_get · GET mid-call partial index — accumulating facts/promises/snippets while live. GET /v1/pbx/index/partial/get?call_id=…. Returns live partial state for whisper ≤400ms path. Idle $0 when no live call. Managed SaaS in-call index; no DID sales.
  • pbx_ingest_transcript · Heuristic promise extractor from transcript text — creates open Promise docs (idle $0, no LLM). Detects promise-like sentences (we will, I promise, refund, cancel, call you back, tomorrow…). Optional persist_promises=false for extract witho
  • pbx_persons · Light CRM from call graph / facts — caller phones+names and extension identities seen on transfers. GET /v1/pbx/persons?call_id=&kind=caller|extension|all&q=&limit=50. Durable Person rows from pbx-index plus derived extension identities (ex
  • pbx_persons_get · Get one light-CRM identity by id — caller Person or derived extension. GET /v1/pbx/persons/get?id=per_001|ext_101. Scoped by x-temsor-pbx-key. found=false if missing. Idle $0. No DID sales.
  • pbx_promises · List open/broken call promises for agent handoff tracking — hotel / MSP sales demo. Idle $0. GET /v1/pbx/promises?status=open returns open/unclosed promises with transfer/handoff path for orchestration. Scoped by x-temsor-pbx-key when set.
  • pbx_promises_act · E1 moat: who→whom→promise → orchestra handoff intent (whisper/transfer/hold). Idle $0. No live PSTN. Own PBX = advanced footnote. POST /v1/pbx/promises/act {promise_id, action?}. Loads the promise + call graph, suggests whisper/transfer/hol
  • pbx_promises_close · Mark an open promise kept or broken with an optional privacy-safe note — makes the sales demo writable, not read-only. ≤60/hour/key → 429. POST /v1/pbx/promises/close {promise_id, status:kept|broken, note?}. Phones/emails in note are scrubb
  • pbx_promises_export · Export open/broken promises as CSV or JSON — hotel / PBX-provider unclosed-promise sales list. GET /v1/pbx/promises/export?status=open|closed&format=csv|json. CSV/JSON include closed_at, close_note, path crumbs. Scoped by x-temsor-pbx-key w
  • pbx_promises_reopen · Undo a kept/broken close — restore an open promise so the sales demo can reverse a mis-click. ≤60/hour/key → 429. POST /v1/pbx/promises/reopen {promise_id}. Only kept|broken → open; clears closed_at/close_note. Scoped by x-temsor-pbx-key wh
  • pbx_redact · Privacy-first erasure (default-on SaaS): clear derived index by id/phone; durable audit who/what/when + tenant scope. ≤30/hour/key → 429. Managed pointer only — not a legal deletion SLA. E.3 Privacy-first redaction for managed SaaS. mode=an
  • pbx_redact_audit · List recent erasure actions — who/what/when + tenant scope. Managed SaaS derived-index audit; not a legal deletion SLA. GET /v1/pbx/redact/audit?limit=20. Durable audit from POST /v1/pbx/redact (E.3). Tenant-scoped. Derived index cleared; r
  • pbx_register · Register a pilot PBX; returns pbx_id + API key once (hashed at rest). ≤5/hour/IP → 429. Idle $0. Control-plane register. API key shown once; stored hashed at rest. Send x-temsor-pbx-key to scope GET /v1/pbx/promises to this pbx_id. No speec
  • pbx_search · Agent archive search over call promises and facts — voice-Google for call-ops, not a receptionist bot. Idle $0. Demo index + domain dictionary v0. Filters: status, date, ext, competitor, stuck_after (transfer/handoff hop). Returns call-grap
  • pbx_status · Control-plane status — promise/orchestra/search counts + idle $0. No DID sales. GET /v1/pbx/status. Scoped by x-temsor-pbx-key when set. Derived index on Temsor for agent search/orchestration. Idle $0. Advanced: own PBX/Asterisk stays on cu
  • pbx_webhooks · Register or list outbound webhooks — customer URL receives promise/fact/orchestra/redact events (HMAC if secret). POST write ≤30/hour/key → 429. POST /v1/pbx/webhooks {url, secret?, events?, ping?} registers. GET lists. ping:true sends a te
  • pbx_webhooks_deliveries · List last N outbound webhook deliveries (stub or live) — promise/fact/orchestra/redact/ping. GET /v1/pbx/webhooks/deliveries?limit=20&webhook_id=. Durable log of Temsor→customer POSTs. HMAC when secret set. Idle $0. No DID sales. Erasure-aw
  • pbx_whisper_status · Capability: mode=stub|ready from TEMSOR_RTP_*. No live RTP on forge; idle $0. GET /v1/pbx/whisper/status. Reports MediaBridge config presence (TEMSOR_RTP_PATH). mode=ready means path env set — not that Asterisk RTP is flowing. live_rtp/list
  • pbx_whisper_suggest · Live agent handoff cards (≤3): open promises/facts from in-call index. Idle $0. Lab: TEMSOR_RTP_LAB=1 → lab_latency_ms. POST /v1/pbx/whisper/suggest {call_id, partial_text}. Returns open promises and facts as whisper cards for agent handoff
  • phone_validate · Validates and normalises any phone number to E.164, with structural checks for every country calling code. For signup and checkout flows that need to store one canonical form and reject typos early. Any common input (spaces, dashes, bracket
  • tr_address_parse · Splits a free-form Turkish address into neighbourhood, street, building, floor, flat, district, province and postcode. Handles the abbreviation chaos (Mah./Mh., Cd./Cad., Sk./Sok., No:12/5, K:3 D:7), cross-checks the province against the po
  • tr_business_days · Adds business days or counts them between two dates, accounting for Turkish public and religious holidays including half-day eves. Ramadan and Sacrifice feasts follow the Hijri calendar and cannot be derived reliably by formula, so announce
  • tr_iban_olustur · Builds a Turkish IBAN from a 5-digit bank code and account number, computing ISO 7064 check digits. A Turkish IBAN is TR + 2 check digits + 5-digit bank code + 1 reserved digit + 16-character account. This pads the account on the left, defa
  • tr_invoice_build · Builds a UBL-TR e-Invoice or e-Archive XML document from plain JSON, computing every total and validating the parties. Selling into Türkiye means issuing a UBL-TR document whose element order is fixed by schema and whose totals must agree t
  • tr_invoice_parse · Turns a UBL-TR e-Invoice or e-Archive XML document into clean JSON: parties, line items, taxes and totals. Works regardless of the namespace prefix the sender used (cbc:, cac:, ns0:), normalises single-line documents into arrays, and report
  • tr_labor · Computes Turkish severance (kıdem), notice (ihbar) and annual-leave entitlement from service dates and the gross wage, using the official ceiling and minimum-wage tables for the given day. Payroll and HR tools in Turkey chase a parameter th
  • tr_money_to_words · Writes a monetary amount out in Turkish words, the way invoices, cheques and promissory notes require. Applies the rules that trip up generic libraries: Turkish says "bin", never "bir bin"; the kuruş part is read separately; and both "1.234
  • tr_posta_kodu · Validates a 5-digit Turkish postal code and resolves the province from the first two digits (plate map). PTT postal codes are five digits; the leading pair matches the province plate code for the 81 provinces. This endpoint checks the shape
  • tr_qr_odeme · Builds a person-to-person TR Karekod (FAST) payment payload from IBAN, name and optional TRY amount. Text only — no PNG. Turkish instant payments (FAST) can start from a TR Karekod that encodes the payee IBAN and name in EMV-style TLV. This
  • tr_tebligat_clock · Computes the deemed-received date and the HMK deadline (with holiday shifting) for a Turkish notification, from the date the underlying event actually happened. Turkish notification law (7201) ties the deadline clock to an event that is not
  • tr_validate · Validates Turkish national ID, tax number, IBAN, licence plate, IMEI, barcodes, KEP, MERSİS, postal code and ISBN from one endpoint, with type auto-detection. Goes past a yes/no: resolves the bank behind an IBAN, the province behind a licen
  • tr_vat · Splits a Turkish amount into net, VAT and (optionally) withholding: who pays the seller, who remits the withheld VAT. For invoice lines and checkout totals that have to show KDV dahil / hariç and, when the parties are in a withholding (tevk

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://api.temsor.com/mcpDECLAREDSRC-001 Official MCP Registry6d ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry6d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry6d ago
Websitehttps://api.temsor.com/docsDECLAREDSRC-001 Official MCP Registry6d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry6d ago
Version1.0.0DECLAREDSRC-001 Official MCP Registry6d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry6d ago

Change history

Baseline
No change detected yet. History builds up as the robots revisit this server.

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run Temsor API — Turkey & EU business data? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor Temsor API — Turkey & EU business dataLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of Temsor API — Turkey & EU business data?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/temsor-api-turkey-eu-business-data?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/temsor-api-turkey-eu-business-data/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about Temsor API — Turkey & EU business data

How do I connect Temsor API — Turkey & EU business data?

Use the hosted endpoint https://api.temsor.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does Temsor API — Turkey & EU business data offer?

When Electra Index connected on 13 Nov 2026, it listed 43 tools: email_verify, iban_validate, pbx_audio_chunk, pbx_calls, pbx_calls_get, pbx_calls_graph, pbx_dictionary, pbx_dictionary_add and more. The full list is in "Live check" above.

Is Temsor API — Turkey & EU business data online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.

What can I use Temsor API — Turkey & EU business data for?

Based on its description, it is most relevant to: monitor prices, compare products online, manage an online store, manage procurement.