# Temsor API — Turkey & EU business data (remote · api.temsor.com)

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

- Trust score: 62/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.temsor.com`: 62/100 (this document), [markdown](https://verifymcp.io/servers/com-temsor-api/api.md), [page](https://verifymcp.io/servers/com-temsor-api/api)

## Channel facts

- Endpoint: `https://api.temsor.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 15 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 55/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3354 tokens (~223/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 74% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-temsor-api https://api.temsor.com/mcp
```

### Codex

```toml
[mcp_servers.com-temsor-api]
url = "https://api.temsor.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-temsor-api": {
      "type": "remote",
      "url": "https://api.temsor.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-temsor-api --url https://api.temsor.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-temsor-api:
    url: "https://api.temsor.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-temsor-api": {
      "type": "http",
      "url": "https://api.temsor.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 61, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 59, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-27 (score 60, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 60)

First indexed and scored.

## MCP tools (15)

### `email_verify` (~193 tokens)

E-mail Verification

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.

Input parameters:

- `email` (string, required): E-mail address to check.
- `rejectFreeProviders` (boolean)
- `rejectRoleAccounts` (boolean)

### `eu_vat_validate` (~210 tokens)

EU VAT Number Validation

Validates an EU VAT number against the official VIES register, with per-country format checks and honest handling of upstream outages.

VIES is free but unreliable: member-state services drop out individually and a failed lookup can easily be mistaken for a rejection. Treating an outage as "invalid" means charging VAT to a customer who should have been exempt — an error with a price tag. So this endpoint never returns `invalid` when the service could not answer; it returns `unknown` and names the reason, and reports whether that country's service is currently up. Format is checked locally first, so an obvious typo never becomes an upstream call. Results are cached for 24 hours. Note that most member states do not publish the company name; when they do, it is returned.

Input parameters:

- `countryCode` (string): Country code, when the number is given without a prefix.
- `vatNumber` (string, required): VAT number with or without the country prefix, e.g. "DE811907980".

### `iban_validate` (~179 tokens)

IBAN Validation

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 IBANs additionally resolve to the bank name.

Input parameters:

- `expectCountry` (string): Beklenen ülke kodu (ISO 3166-1 alfa-2).
- `iban` (string, required): IBAN, boşluklu veya boşluksuz.

### `model_drift` (~259 tokens)

LLM Endpoint Drift

Independent daily record of what changed behind a provider endpoint: which alias resolved to which model, and when behaviour shifted.

Providers update models behind stable endpoint names. This endpoint publishes an independent measurement: a fixed probe suite is sent daily at temperature 0, three repeats per probe, and the identity a provider declares in its own response (`modelVersion`, `system_fingerprint`, region) is recorded alongside. A change is only reported as drift when the repeats agree with each other and disagree with the previous run — same-day disagreement is noise, not drift. `aliases` answers "what was actually behind `gemini-flash-latest` on that day"; a question that cannot be answered retroactively.

Input parameters:

- `days` (integer): Kaç günlük tarihçe (yalnız `events`).
- `limit` (integer)
- `provider` (string): Sağlayıcıya göre süz (gemini, groq, cerebras, mistral).
- `severity` (string): Yalnız `events` görünümünde.
- `view` (string): `aliases`: takma ad → arkasındaki gerçek model tarihçesi · `events`: sapma olayları · `probes`: son koşudaki sonda durumu.

### `phone_validate` (~242 tokens)

Phone Number Validation

Validates and normalises a phone number to E.164, classifies the line type, and resolves the province for Turkish landlines.

For signup and checkout flows that need to store one canonical form and reject typos early. Turkish numbers are handled in depth: landline area codes resolve to a province, mobile and special ranges (toll-free 0800, fixed-rate 0850, premium 0900) are classified, and every accepted input comes back in both E.164 and national notation.

One thing this endpoint deliberately does not claim: the current mobile operator. Turkey has had number portability since 2008, so a 0532 number may well be on another network today. Competing APIs report the prefix owner as "the operator" and customers pick SMS routes on that basis. We return it as `originallyAllocatedTo` with the caveat attached, because a confident wrong answer costs more than an honest gap.

Input parameters:

- `defaultCountry` (string): ISO 3166-1 alpha-2 country to assume when the number has no international prefix. Defaults to TR.
- `phone` (string, required): Phone number in any common format.

### `sanctions_screen` (~336 tokens)

Sanctions & PEP Screening

Screens a name against six official sanctions lists — US OFAC, UN, EU, UK OFSI, Switzerland SECO and Canada — with transliteration-aware fuzzy matching.

Six official lists are reduced to one schema, so a name is checked everywhere at once instead of six integrations. Cyrillic and Arabic names are transliterated, titles and corporate suffixes are stripped, and known spelling families are unified — "Abd al-Rahman", "Abdul Rahman" and "Abdulrahman" reach the same record. Every hit explains itself: which name matched, whether it was an alias the source flags as weak, and how the birth year and country compared. Supply `birthYear` whenever you have it; it removes most false positives. `asOf` screens against the lists as they stood on a past date, which is the question auditors actually ask — note that this is bounded by when our archive begins, reported in `coverage`.

Input parameters:

- `asOf` (string): Screen against the lists as they stood on this date. Limited by when our archive begins.
- `birthYear` (integer): Known birth year. The single strongest false-positive filter available.
- `country` (string): Known country or nationality.
- `limit` (integer)
- `minScore` (number): Score floor. 0.92+ reads as a match, 0.80+ as possible.
- `name` (string, required): Name to screen — person or organisation.
- `sources` (array): Defaults to all lists.
- `type` (string): Restrict to one subject type. Narrowing this removes most false positives.

### `series_history` (~212 tokens)

Time Series History

Returns the accumulated history of public data series with change statistics and a source receipt for every point.

Currently ingesting the Turkish Central Bank daily FX bulletin (`tcmb.usd`, `tcmb.eur`, …), normalised to one unit so JPY-style 100-unit quotes stop biting. Leave `seriesId` empty to list the catalogue. `fillGaps` carries the last value across weekends and holidays; `includeEvidence` attaches the source URL and content hash for every point, so a value can still be defended years later.

Input parameters:

- `fillGaps` (boolean)
- `from` (string): Başlangıç tarihi (dahil).
- `includeEvidence` (boolean): Her nokta için kaynak URL ve içerik özetini döndürür.
- `limit` (integer)
- `seriesId` (string): Seri kimliği, ör. `tcmb.usd`. Boş bırakılırsa katalog döner.
- `to` (string): Bitiş tarihi (dahil).

### `shipping_identify` (~237 tokens)

Tracking Number Identification

Identifies which carrier a tracking number belongs to, validates it where a checksum exists, and returns the canonical tracking link.

Built for order systems that receive numbers from many carriers and have to route the customer to the right tracking page. Turkish carriers mostly use plain numeric ranges that overlap, so a single confident answer is often impossible — this returns a ranked candidate list instead of inventing certainty, because sending a customer to the wrong carrier's page makes them think the parcel is lost. Universal Postal Union (S10) numbers are fully verified: the mod-11 check digit is computed, the service type and origin country are decoded. For formats whose checksum we have not verified against the standard, the result says `not-verified` rather than guessing — a wrong rejection is worse than an honest unknown. Delivery status is deliberately out of scope: Turkish carriers require merchant credentials for that, and scraping their sites would be fragile and against their terms.

Input parameters:

- `country` (string): Destination or origin country hint, e.g. "TR". Narrows the candidates.
- `trackingNumber` (string, required): Tracking number, with or without spaces and dashes.

### `tr_address_parse` (~155 tokens)

Turkish Address Parser

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.

Input parameters:

- `address` (string, required): Serbest metin adres.
- `defaultProvince` (string): Adreste il geçmiyorsa varsayılacak il.

### `tr_business_days` (~168 tokens)

Turkish 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 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.

Input parameters:

- `addDays` (integer): Bu kadar İŞ GÜNÜ ekle/çıkar.
- `countHalfDaysAsWork` (boolean): Arife yarım günleri iş günü sayılsın mı?
- `end` (string): Verilirse aradaki iş günü sayılır.
- `start` (string, required): Başlangıç tarihi (YYYY-AA-GG).

### `tr_fuel_prices` (~300 tokens)

Turkey Fuel Prices

Petrol, diesel and heating-oil pump prices for all 81 Turkish provinces, including the price in force on any past date.

Today's pump price is on a public web page; the archive is not. This endpoint answers the question that actually costs money: what was diesel in Ankara on 12 March? Pass `asOf` for the price in force on that day — if the distributor did not change prices that day, the previous price is carried forward and `effectiveFrom` says when it started, with `carriedForward: true`. Pass `from`/`to` to get the change events in a window, each with the percentage move. Every figure carries the source URL and a content hash of the page it was read from, so the number can still be defended in an audit years later. Leave `province` empty to list coverage.

Input parameters:

- `asOf` (string): Price in force on this date (YYYY-MM-DD). Omitted → latest known price.
- `from` (string): With `to`: return the price changes in this window.
- `includeDistricts` (boolean): Adds districts whose pump price differs from the province reference price.
- `product` (string): Fuel product. Omitted → every product available for that province.
- `province`: Province name or plate code — "Ankara", "istanbul" or 34. Leave empty to list covered provinces.
- `to` (string)

### `tr_invoice_build` (~454 tokens)

Turkish e-Invoice Builder

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.

Input parameters:

- `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, required)
- `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, required)
- `issueTime` (string)
- `lines` (array, required)
- `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, required)
- `uuid` (string): Document UUID (ETTN). Generated when omitted.

### `tr_invoice_parse` (~115 tokens)

Turkish e-Invoice (UBL-TR) Parser

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.

Input parameters:

- `xml` (string, required): UBL-TR e-Fatura / e-Arşiv XML içeriği.

### `tr_money_to_words` (~167 tokens)

Amount to Turkish 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,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.

Input parameters:

- `amount` (required): Tutar. "1.234,56" ve 1234.56 biçimlerinin ikisi de kabul edilir.
- `currency` (string)
- `style` (string): Çıktı harf biçimi.
- `wrapHash` (boolean)

### `tr_validate` (~127 tokens)

Turkish ID & Number Validation

Validates Turkish national ID, tax number, IBAN, licence plate, IMEI and barcodes 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.

Input parameters:

- `type` (string): Belirtilmezse biçimden otomatik tespit edilir.
- `value` (string, required): Doğrulanacak değer.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-temsor-api/api#diagnostics

## Score history

- 2026-08-03: 62
- 2026-08-02: 62
- 2026-08-01: 61
- 2026-07-31: 61
- 2026-07-30: 59
- 2026-07-29: 60
- 2026-07-28: 60
- 2026-07-27: 60
- 2026-07-26: 60

## Links

- Remote endpoint: https://api.temsor.com/mcp
- Website: https://api.temsor.com/docs
- Changelog RSS feed: https://verifymcp.io/servers/com-temsor-api/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-temsor-api/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-temsor-api/api