Temsor API — Turkey & EU business data
REMOTE · API.TEMSOR.COM
Turkey & EU business data: validation, sanctions screening, parsing, FX and fuel price history
Available components
Last scanned (17 hours ago)
Scores higher than 72% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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 → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 43 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 8091 tokens (~188/item across 43 items; 43 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 81% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 43 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 43 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 43 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 8 Nov 26 +1
- Stability: 0.97 → pass security
- 7 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 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
- 28 Oct 26 +6
- Stability: fail → pass ▲ security
- 10 Oct 26 0
- Schema quality: 163 → 188 ▼ functional
- Schema quality: good → excellent functional
- 7 Oct 26 0
- Schema quality: 187 → 163 ▲ functional
- Schema quality: excellent → good functional
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 21 Nov 2026 · Probed https://api.temsor.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=temsor.com | CN=WE1,O=Google Trust Services,C=US | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | fe54b44d9fe271fc0ec41556e30f2215 |
| SANs: temsor.com, *.temsor.com | ||||||
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.temsor.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| temsor.com. | DS published | 2371 | 13 | Verified |
| api.temsor.com. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.temsor.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.temsor.com/mcp | HTTPS enforced | 301 | https://api.temsor.com/mcp |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
email_verify E-mail Verification ~193
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 thorough but produces a confident-looking number you cannot trust: most servers are catch-all, the big providers refuse to answer, and doing it in bulk gets the probing IP blacklisted. We report only what is provable — whether the domain has a mail exchanger, whether it is a known disposable service, whether the mailbox belongs to a role rather than a person, and whether the domain looks like a typo of a common one (gmial.com → gmail.com). Addresses are also normalised, so Gmail dots and +tags stop creating duplicate signups.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | E-mail address to check. | |
| rejectFreeProviders | boolean | – | – |
| rejectRoleAccounts | boolean | – | – |
No output schema declared.
No examples provided.
iban_validate IBAN Validation ~198
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 — not that the number could exist in that country. This checks the country's BBAN structure too, so a wrong-length or wrong-shaped account is rejected before your payment file reaches the bank. When only the two check digits are wrong, the correct ones are computed and returned as a suggestion, because that is what people actually mistype. Turkish, Dutch and Belgian IBANs additionally resolve to a bank name when the national code is in our table; otherwise bankName is null. This is not a SWIFT directory.
| Name | Type | Req | Description |
|---|---|---|---|
| expectCountry | string | – | Expected country code (ISO 3166-1 alpha-2). |
| iban | string | yes | IBAN, with or without spaces. |
No output schema declared.
No examples provided.
pbx_audio_chunk PBX Audio Chunk ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bytes_b64 | string | – | Optional small demo chunk; production prefers URI. |
| call_id | string | yes | – |
| pbx_id | string | – | – |
| t_ms | integer | – | – |
| uri | string | – | Customer-side media URI (preferred). |
No output schema declared.
No examples provided.
pbx_calls PBX Recent Calls ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max recent calls to return (1–100). |
No output schema declared.
No examples provided.
pbx_calls_get PBX Get Call ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | string | yes | Call id (e.g. call_msp_002). |
No output schema declared.
No examples provided.
pbx_calls_graph Call Handoff Graph ~135
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/orchestration: handoff edges, not a bot transcript. Idle $0. No DID sales / no live PSTN.
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | string | yes | Call id whose transfer graph to return. |
| stuck_at | string | – | Optional override for where the promise stuck (extension). |
No output schema declared.
No examples provided.
pbx_dictionary PBX Domain Dictionary ~164
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 (legacy otel|santral_firmasi|sigorta|finans|enerji|otomotiv|msp still accepted). Idle $0, no LLM. Synonyms feed archive search (match crumbs) and transcript Fact extraction. Write path: POST /v1/pbx/dictionary/add.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Domain slice: hotel | pbx_provider | insurance | finance | energy | automotive | all (legacy keys + msp accepted) |
No output schema declared.
No examples provided.
pbx_dictionary_add PBX Dictionary Add Alias ~293
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|finance|energy|automotive, scope?:pbx|global}. Managed SaaS compounding (E4): tenant-scoped aliases thicken search + fact extract. No invented premiums/prices. Idle $0, no LLM. Legacy keys (otel, santral_firmasi, msp…) still accepted.
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | yes | Synonym / alias to add (e.g. cooling, line package). |
| boost | number | – | Search boost weight (default 2). |
| domain | string | – | Domain: hotel | pbx_provider | insurance | finance | energy | automotive (legacy keys + msp accepted). |
| hint_en | string | – | – |
| hint_tr | string | – | – |
| kind | string | – | Fact kind; inferred from seed term when omitted. |
| scope | string | – | pbx = scoped to x-temsor-pbx-key; global = demo-wide. Default: pbx if registered key, else global. |
| term | string | yes | Canonical term (e.g. AC, tariff). Plain Turkish preferred. |
No output schema declared.
No examples provided.
pbx_events Call Events Ingest ~183
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)); bad signature rejected when header present. BridgeEnter → transfer/handoff crumbs. Utterance/text → open Promise docs via heuristic (no LLM). Idle $0. Body ≤256 KiB → 429. Advanced: ARI/Stasis batch shape when customer runs own PBX — not Asterisk-first product copy.
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | yes | ARI / Stasis event batch. Utterance/text fields trigger heuristic promise extract. |
| pbx_id | string | – | PBX id that emitted the ARI batch. |
No output schema declared.
No examples provided.
pbx_facts PBX Facts List ~231
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 transcript extract + domain dictionary; persist in pbx-index. Scoped by x-temsor-pbx-key. Idle $0. No DID sales. Right-to-erasure ready. Advanced: own PBX/Asterisk stays on customer.
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | string | – | Filter by call id (e.g. call_msp_001). |
| domain | string | – | Domain slice: hotel | pbx_provider | insurance | finance | energy | automotive | all (legacy keys + msp accepted). |
| kind | string | – | Fact kind key (imei, oda, tarife, ...) or all. |
| limit | integer | – | Max facts to return (1–200). |
| q | string | – | Free-text filter over kind + value + call_id. |
No output schema declared.
No examples provided.
pbx_facts_get PBX Get Fact ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Fact id (e.g. fact_001). |
No output schema declared.
No examples provided.
pbx_index_partial PBX In-Call Partial Index Upsert ~251
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 queue into accumulating Fact/Promise hints while the call is live. No Temsor STT/LLM — customer posts text. Managed SaaS in-call index; no DID sales. Own PBX optional footnote. Idle $0.
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | string | yes | Live call id to upsert partial index for. |
| end_call | boolean | – | Mark live=false; idle $0 for this call. |
| is_final | boolean | – | Finalized utterance span (vs interim). |
| live | boolean | – | Default true while call is live. |
| pbx_id | string | – | – |
| promote | boolean | – | Promote heuristic hints into durable Promise/Fact docs. |
| speaker | – | – | – |
| t_ms | – | – | – |
| text | string | – | Partial utterance / snippet (customer STT or demo). Empty = metadata-only. |
No output schema declared.
No examples provided.
pbx_index_partial_get PBX In-Call Partial Index Read ~94
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. Own PBX optional footnote.
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | string | yes | Call id whose live partial index to read. |
No output schema declared.
No examples provided.
pbx_ingest_transcript PBX Ingest Transcript ~157
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 without writing. Also wired via utterance text on POST /v1/pbx/events.
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | string | – | – |
| ext | string | – | – |
| pbx_id | string | – | – |
| persist_promises | boolean | – | When false, extract only (dry-run, no write). When true, create Promise docs status=open. |
| transcript | string | yes | TR utterance / transcript text to scan for promises. |
| who | string | – | – |
No output schema declared.
No examples provided.
pbx_persons PBX Persons List ~200
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 (ext_NNN) from Transfer edges / promise.ext. Scoped by x-temsor-pbx-key. Idle $0. No DID sales. Right-to-erasure ready. Advanced: own PBX/Asterisk stays on customer.
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | string | – | Filter persons seen on this call id. |
| include_extensions | boolean | – | Include derived extension identities (default true). |
| kind | string | – | caller = durable Person; extension = derived from call-graph hops; all = both. |
| limit | integer | – | Max persons to return (1–200). |
| q | string | – | Free-text over names, phones, org, extensions, facts. |
No output schema declared.
No examples provided.
pbx_persons_get PBX Get Person ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Person id (e.g. per_001) or extension id (e.g. ext_101). |
No output schema declared.
No examples provided.
pbx_promises Open Call Promises ~99
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. Idle $0. No live PSTN.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | Promise status filter; closed = kept|broken. Sales demo uses open. |
No output schema declared.
No examples provided.
pbx_promises_act Promise → Orchestra Closed Loop ~227
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/hold, records orchestra intent with source_type=promise for agent handoff. Managed SaaS runtime. ≤120/hour/key (shares orchestra bucket). Idle $0. carrier/pstn always false. No cross-tenant graph merge. Advanced: not Asterisk-first glue; own PBX optional footnote.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Default whisper. transfer uses graph stuck_at / promise.ext. |
| agent_ext | string | – | – |
| pbx_id | string | – | – |
| promise_id | string | yes | Open (or any) promise id — closed loop reads call graph then records orchestra intent. |
| skip_forward | boolean | – | Default true — record intent only. |
| stasis_webhook_url | string | – | – |
No output schema declared.
No examples provided.
pbx_promises_close PBX Close Promise ~161
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 scrubbed. Scoped by x-temsor-pbx-key when set. Idle $0 — no LLM/PSTN.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | Optional short operator note. Phones/emails stripped (privacy-safe). |
| promise_id | string | yes | Promise id (prm_*). Sales demo marks open promises kept|broken. |
| status | string | yes | Close outcome: kept (honoured) or broken (not kept). |
No output schema declared.
No examples provided.
pbx_promises_export PBX Promises Export ~113
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 when set. Idle $0.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Export format. |
| status | string | – | Promise status filter; closed = kept|broken. Sales demo uses open. |
No output schema declared.
No examples provided.
pbx_promises_reopen PBX Reopen Promise ~109
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 when set. Idle $0.
| Name | Type | Req | Description |
|---|---|---|---|
| promise_id | string | yes | Promise id (prm_*). Undo a kept|broken close — restore open. |
No output schema declared.
No examples provided.
pbx_redact PBX Redact ~250
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=anonymize|delete. Lookup by target_id or phone. Clears Person/Promise/Fact/partial index + Temsor audio pointers in your tenant only (no cross-tenant). Durable audit. Raw media stays on your side. Not a legal deletion SLA. List: GET /v1/pbx/redact/audit.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | anonymize (default) scrubs fields; delete removes docs. |
| phone | string | – | Caller phone — finds Person phones (+ linked derived index). |
| reason | string | – | Personal-data erasure reason. |
| target_id | string | – | Document id (prm_*, per_*, call_*, fact_*). |
| target_type | string | – | Index document type. Optional when `phone` is set. |
| who | string | – | Actor label for durable audit (defaults to pbx scope / demo-operator). |
No output schema declared.
No examples provided.
pbx_redact_audit PBX Redact Audit ~121
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; raw media not deleted by Temsor. Number→flow managed SaaS; own PBX optional. No DID sales.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max recent forget actions to return (default 20). |
No output schema declared.
No examples provided.
pbx_register PBX Register ~247
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 speech recognition while idle.
| Name | Type | Req | Description |
|---|---|---|---|
| ari_webhook_secret | string | – | ARI webhook signing secret (stored as hint only). |
| string | – | Pilot contact email. | |
| label | string | – | Human label, e.g. hotel or PBX/IT provider site. |
| name | string | – | Pilot contact name (waitlist / register). |
| pbx_id | string | – | Pilot PBX id; auto-minted if omitted. |
| webhook_events | – | – | Event list or comma string: promise.opened|closed, fact.extracted, orchestra.act, redact, or *. |
| webhook_secret | string | – | Optional HMAC secret for outbound webhook signatures (x-temsor-signature). |
| webhook_url | string | – | Optional outbound webhook URL — Temsor POSTs promise/fact/orchestra/redact events. |
No output schema declared.
No examples provided.
pbx_search Voice Archive Search ~176
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-graph path + transfer edges for orchestration. Idle $0. No live PSTN.
| Name | Type | Req | Description |
|---|---|---|---|
| competitor | string | – | – |
| date_from | string | – | ISO date/time lower bound (promise.when_iso / call.started_at). |
| date_to | string | – | ISO date/time upper bound. |
| ext | string | – | – |
| q | string | – | Full-text query over promises, facts, and call summaries. |
| status | string | – | – |
| stuck_after | string | – | Filter: promise stuck after transfer to this extension (to_ext hop). |
No output schema declared.
No examples provided.
pbx_status PBX Status ~75
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 customer.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pbx_webhooks PBX Outbound Webhooks ~252
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 test delivery. Events: promise.opened, promise.closed, fact.extracted, orchestra.act, redact. Signed with x-temsor-signature when secret set. Idle $0. No DID sales. Erasure-aware. Advanced: own PBX/Asterisk stays on customer.
| Name | Type | Req | Description |
|---|---|---|---|
| events | – | – | Events: promise.opened|closed, fact.extracted, orchestra.act, redact, or *. |
| limit | integer | – | List limit (default 50). |
| ping | boolean | – | If true with url → register then ping; if true without url → ping existing. |
| secret | string | – | Optional HMAC-SHA256 secret → x-temsor-signature: sha256=<hex>. |
| url | string | – | Outbound webhook URL (http/https). Present → register; omit on GET → list. |
| webhook_id | string | – | For ping: target webhook id. |
No output schema declared.
No examples provided.
pbx_webhooks_deliveries PBX Webhook Deliveries ~121
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-aware. Advanced: own PBX/Asterisk stays on customer.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max deliveries (default 20). |
| webhook_id | string | – | Filter by webhook id. |
No output schema declared.
No examples provided.
pbx_whisper_status PBX Whisper RTP Status ~130
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/listening always false on forge (R2–R3 IVR sidecar; R4 lab E2E harness). No ≤400ms production claim. TEMSOR_RTP_LAB=1 → optional lab_latency_ms on suggest. No DID sales.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pbx_whisper_suggest PBX Live Whisper Suggest ~171
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. Prefers in-call partial index when present. Mock latency_ms under 400ms (compat stub). Idle $0. No Telnyx/DID/live PSTN. Advanced: optional lab_latency_ms when TEMSOR_RTP_LAB=1 (measured; not prod SLA).
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | string | yes | Active call id for agent UI context. |
| partial_text | string | – | Partial transcript / utterance text (no live speech recognition). |
No output schema declared.
No examples provided.
phone_validate Phone Number Validation ~283
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, brackets, 00 or + prefix, a stray national trunk zero) comes back as E.164 plus national notation, with the country resolved from the calling code. Numbers without an international prefix use `defaultCountry` (US when omitted), so (415) 555-0134 and +1 415 555 0134 store the same. One thing this endpoint deliberately does not claim: the current mobile operator. Numbers are portable in most markets, so a prefix says where a number was first allocated, not where it lives today. Competing APIs report the prefix owner as "the operator" and customers pick SMS routes on that basis. Where we know the original allocation we return it as `originallyAllocatedTo` with the caveat attached, because a confident wrong answer costs more than an honest gap. Countries without a full numbering plan here are validated structurally and say so in `warnings`.
| Name | Type | Req | Description |
|---|---|---|---|
| defaultCountry | string | – | ISO 3166-1 alpha-2 country to assume when the number has no international prefix. Defaults to US. |
| phone | string | yes | Phone number in any common format. |
No output schema declared.
No examples provided.
tr_address_parse Turkish Address Parser ~149
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 postcode, repairs misspelled district names against a dictionary, and returns a confidence score. Anything it could not place is listed in `unparsed` — nothing is dropped silently. Built for shipping, checkout and CRM systems that receive Turkish addresses typed by humans.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Free-text address. |
| defaultProvince | string | – | Province to assume when the address has none. |
No output schema declared.
No examples provided.
tr_business_days Turkish Business Days ~160
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 announced dates are read from a table; years without an official announcement are returned with `confirmed:false` rather than guessed silently. For delivery promises, SLA clocks, payment terms and shipping estimates.
| Name | Type | Req | Description |
|---|---|---|---|
| addDays | integer | – | Add/subtract this many business days (not calendar days). |
| countHalfDaysAsWork | boolean | – | Count Arife half-days as working days? |
| end | string | – | If set, count business days between start and this date. |
| start | string | yes | Start date (YYYY-MM-DD). |
No output schema declared.
No examples provided.
tr_iban_olustur Build Turkish IBAN ~202
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, defaults the reserved digit to 0, computes the mod-97 check digits, and resolves the bank name from the same national table used by IBAN validation when the code is known. Unknown bank codes still produce a structurally valid IBAN with bankName null — existence at the bank is not claimed.
| Name | Type | Req | Description |
|---|---|---|---|
| accountNumber | string | yes | Account number, up to 16 alphanumeric characters (padded left with zeros). |
| bankCode | string | yes | 5-digit Turkish national bank / EFT code (e.g. 00062). |
| reserved | string | – | Reserved BBAN digit after the bank code. Defaults to 0. |
No output schema declared.
No examples provided.
tr_invoice_build Turkish e-Invoice Builder ~454
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 to the kuruş, or the integrator rejects it. This endpoint takes the invoice as ordinary JSON and returns the XML. Totals you send are ignored on purpose — line amounts, per-rate VAT subtotals and the payable amount are all recomputed here, because a rounding difference of one kuruş is the most common rejection. VKN and TCKN checksums are verified, and the amount is written out in Turkish words as invoices require. It does not sign the document and does not transmit it: the financial seal and the submission to the tax authority belong to your certificate and your integrator. What comes back is a document ready to enter that step.
| Name | Type | Req | Description |
|---|---|---|---|
| amountInWords | boolean | – | Adds the payable amount written out in Turkish words as a note, the way invoices require. |
| currency | string | – | ISO 4217. Anything other than TRY requires `exchangeRate`. |
| customer | object | yes | – |
| despatchDocumentId | string | – | Delivery note number, if the goods shipped separately. |
| exchangeRate | number | – | Units of TRY per one unit of `currency`. |
| id | string | – | Invoice number. Omit and supply `series` to have it built from the series and sequence. |
| invoiceTypeCode | string | – | – |
| issueDate | string | yes | – |
| issueTime | string | – | – |
| lines | array | yes | – |
| notes | array | – | – |
| orderReferenceId | string | – | – |
| profile | string | – | TEMELFATURA: no formal objection flow. TICARIFATURA: buyer may accept/reject. EARSIVFATURA: buyer is not an e-Invoice user. |
| sequence | integer | – | Sequence number within the series and year. |
| series | string | – | Three-letter series code, used with `sequence`. |
| supplier | object | yes | – |
| uuid | string | – | Document UUID (ETTN). Generated when omitted. |
No output schema declared.
No examples provided.
tr_invoice_parse Turkish e-Invoice (UBL-TR) Parser ~118
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 reports amount mismatches in `warnings` instead of returning quietly wrong totals. The job that costs accounting and expense software the most engineering time.
| Name | Type | Req | Description |
|---|---|---|---|
| xml | string | yes | UBL-TR e-Invoice / e-Archive (e-Arsiv) XML body. |
No output schema declared.
No examples provided.
tr_labor Turkish Severance, Notice & Leave ~356
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 that changes every January and July: the severance ceiling, the SGK cap, the minimum wage. This endpoint applies the statutory formulae (Labour Law 4857 arts. 17 and 53, former 1475 art. 14) to those tables. The ceiling is applied to the monthly wage, not the total. Stamp tax (0.759%) is deducted from severance; income tax is not — kıdem is exempt. Notice pay IS taxable; we return the gross and say so, because the actual withholding depends on the employee's cumulative tax base. What this will not tell you: whether the employee is entitled to severance at all. That depends on the reason for termination (retirement, just cause, marriage, military service…). Treating the number as "what is owed" is how you lose at trial.
| Name | Type | Req | Description |
|---|---|---|---|
| age | integer | – | Employee age at termination — affects annual-leave entitlement (under 18 or 50+). |
| asOf | string | – | Rate table date. Defaults to endDate. |
| endDate | string | yes | Termination date (YYYY-MM-DD). Inclusive of this day. |
| monthlyGross | number | yes | Gross monthly wage the severance is based on (giydirilmiş brüt). |
| startDate | string | yes | Employment start date (YYYY-MM-DD). |
| unusedLeaveDays | number | – | Unused annual-leave days, if you also want the unused-leave gross. |
No output schema declared.
No examples provided.
tr_money_to_words Amount to Turkish Words ~156
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,56" and "1,234.56" are accepted and told apart automatically. A mandatory field on Turkish e-invoices, cheques and notes — with no off-the-shelf API until now.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | – | yes | Amount. Accepts both "1.234,56" and 1234.56. |
| currency | string | – | – |
| style | string | – | Output letter case. |
| wrapHash | boolean | – | – |
No output schema declared.
No examples provided.
tr_posta_kodu Turkish Postal Code ~127
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, maps 01–81 to the province name, and returns null with confidence none when the prefix is outside that range — it does not invent a district. District-level resolution needs the full PTT directory and is out of scope here.
| Name | Type | Req | Description |
|---|---|---|---|
| postalCode | string | yes | Turkish 5-digit postal code, with or without spaces. |
No output schema declared.
No examples provided.
tr_qr_odeme Turkish FAST / TR Karekod Payload ~279
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 builds the person-to-person organisation (payload format indicator 750210): application template with IBAN, payee name, optional 12-digit kuruş amount, optional free-text explanation, and a CRC-16/CCITT-FALSE trailer. The Turkish IBAN is normalised and checked with ISO 7064 mod-97; non-TR IBANs and non-TRY currencies are rejected. This does not send money and does not render a QR image.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | TRY amount; omitted → static QR (payer enters amount). |
| currency | string | – | Must be TRY if provided. |
| explanation | string | – | Optional remittance note (application free field 10). |
| generatorCode | string | – | QR generator / EFT code (4 digits). Defaults to last 4 of the IBAN bank code. |
| iban | string | yes | Beneficiary Turkish IBAN (with or without spaces). |
| name | string | yes | Payee name shown to the payer (2–26 chars after trim). |
No output schema declared.
No examples provided.
tr_tebligat_clock Turkish Service-of-Process Clock ~598
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 "the date on the letter" — for electronic notification the UETS platform reports send, read AND reached dates, and only the reached date starts the clock (art. 7/a: deemed received 5 calendar days after reaching the address, whether or not it was opened). HMK adds two more rules on top: the day of notification itself does not count (art. 92 — the period starts the next day) and if the computed last day lands on a weekend or a full public/religious holiday, it moves to the next business day (art. 93); a half-day eve (arife) does not shift it. What this will not tell you: whether the notification was itself valid, or what a specific `periodType` (itiraz, temyiz, cevap…) is in days for your case — that number differs by statute and we do not guess it; supply `periodDays` yourself. Only the "hmk" law family is covered so far.
| Name | Type | Req | Description |
|---|---|---|---|
| basisDate | string | yes | The date `basisLabel` describes for this type — for "electronic" this is the date UETS reports the message as reached, not sent or read. |
| hasAttorney | boolean | – | Whether the addressee has a registered attorney of record. When true and `type` is not "vekil", a TK 11 warning is added noting that service should have gone to the attorney. |
| ilanenDeemedDays | integer | – | Only valid with type "ilanen": number of days the competent authority set for the notice to become deemed received (TK 31), 7-15, default 7. Not the number of days for the underlying period. |
| lawFamily | string | yes | Body of procedural law the period is computed under. Only "hmk" (Code of Civil Procedure) is supported so far. |
| periodDays | integer | yes | Length of the statutory or judicial period, in days, counted from `periodStart`. |
| periodType | string | – | Free-text label for the period (e.g. "itiraz", "temyiz"), echoed back only — not mapped to a day count. |
| subjectToJudicialRecess | boolean | – | Whether this matter is subject to the judicial recess (adli tatil, HMK 104) instead of being exempt. Only affects the result when `lawFamily` is "hmk" and the computed last day falls in the 20 July -… |
| type | string | yes | Notification method. Determines which event `basisDate` refers to and whether the deemed-received date is same-day or shifted. |
No output schema declared.
No examples provided.
tr_validate Turkish ID & Number Validation ~131
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 licence plate and the GS1 country prefix behind a barcode. Pure local computation — no upstream service is called, so latency is microseconds and the answer never changes for the same input.
| Name | Type | Req | Description |
|---|---|---|---|
| type | string | – | Omitted → inferred from the format. |
| value | string | yes | Value to validate. |
No output schema declared.
No examples provided.
tr_vat Turkish VAT & Withholding ~304
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 (tevkifat) situation, the split between what the buyer pays the seller and what the buyer remits to the tax office. Rates are 0, 1, 10 and 20 percent. Withholding is a fraction of the VAT (2/10 through 10/10), or a named code from the GİB partial-withholding list. The 2026 threshold (TRY 12,000 gross) is reported and compared with the amount, but `applies` is always null: whether withholding actually applies depends on the taxpayer status of both parties, which this endpoint does not know. Feeding it a fraction is not a legal opinion.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | The amount to tax. See amountIncludesVat. |
| amountIncludesVat | boolean | – | If true, `amount` is the gross (KDV dahil); if false, it is the net/matrah. |
| rate | – | – | VAT rate in percent. 0, 1, 10 or 20. |
| withholding | string | – | Withholding fraction such as "5/10", or a code from the list (reklam, tasima, hurda, isgucu…). |
No output schema declared.
No examples provided.
How do I install the Temsor API — Turkey & EU business data MCP server?
Temsor API — Turkey & EU business data is a hosted endpoint at https://api.temsor.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.temsor.com
claude mcp add --transport http com-temsor-api 'https://api.temsor.com/mcp'
What is the Temsor API — Turkey & EU business data MCP server?
Temsor API — Turkey & EU business data is an MCP server listed in the public MCP registry as com.temsor/api. Turkey & EU business data: validation, sanctions screening, parsing, FX and fuel price history. This page covers its hosted endpoint (https://api.temsor.com/mcp).
Is the Temsor API — Turkey & EU business data MCP server safe to use?
Temsor API — Turkey & EU business data scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Temsor API — Turkey & EU business data MCP server expose?
Temsor API — Turkey & EU business data exposes 43 tools: email_verify, iban_validate, pbx_audio_chunk, pbx_calls, pbx_calls_get, and 38 more. Their descriptions and schemas cost roughly 8,091 tokens of context every time the server is loaded.
Does the Temsor API — Turkey & EU business data MCP server require authentication?
No. We connected to Temsor API — Turkey & EU business data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Temsor API — Turkey & EU business data MCP server still maintained?
Temsor API — Turkey & EU business data is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Temsor API — Turkey & EU business data MCP server?
VerifyMCP ran 12 checks on Temsor API — Turkey & EU business data, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Temsor API — Turkey & EU business data: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.