Is the Temsor MCP server down?

mcp-registry/com.temsor/api · v1.0.0

healthy
Last checked 2026-10-18 22:56 UTC · handshake 605ms

As of 2026-10-18 22:56 UTC, the Temsor MCP server is up with a Glimind reliability score of 75/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 21 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
99.6%
checks observed
3,754
outages (90d)
21
tools
43

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

Install Temsor MCP server

Add to Cursor Add to VS Code

Claude Code

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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: D (66/100)

D (66/100): 0 error(s), 7 warning(s) across 43 tool(s); ~12,688 tokens of tool definitions.
Scores higher than 2% of 15,339 MCP servers Glimind has audited.
Its tool list costs an agent ~12,688 tokens per session — more than 85% of servers.
66 → 66 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions75
Safety hints11
Token cost64
Client compatibility70
Protocol100
Reliability85
Stability20

What to fix (8)

1 tool definition(s) exceed ~1,200 tokens each (largest: tr_invoice_build, ~1,491).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~891 tokens every session. How to fix →

Tools: tr_invoice_build · saves ~891 tokens/session

43 of 43 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: email_verify, iban_validate, pbx_audio_chunk, pbx_calls, pbx_calls_get and 38 more

43 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

30 parameter(s) across 9 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: email_verify, pbx_audio_chunk, pbx_dictionary_add, pbx_index_partial, pbx_ingest_transcript and 4 more

5 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: pbx_index_partial, pbx_promises_act, pbx_promises_close, tr_posta_kodu, tr_qr_odeme

Handshake + tools/list takes ~2,658 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

In the last 30 days: 42 tool(s) removed and 6 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 20 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 9 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.temsor%2Fapi/fixes

iban_validate 1 change
{
  "name": "iban_validate",
  "description": "Validates an IBAN from any of 70+ countries: checksum, country length and in-country account structure, and resolves the bank and branch codes.\n\nMost 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 com",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "iban"
    ],
    "properties": {
      "iban": {
        "type": "string",
        "maxLength": 42,
        "minLength": 5,
        "description": "IBAN, with or without spaces."
      },
      "expectCountry": {
        "type": "string",
        "maxLength": 2,
        "minLength": 2,
        "description": "Expected country code (ISO 3166-1 alpha-2)."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "IBAN Validation"
}
pbx_calls_get 1 change
{
  "name": "pbx_calls_get",
  "description": "Get one call by id with transfer graph — customer detail drawer.\n\nGET /v1/pbx/calls/get?call_id=…. Scoped by x-temsor-pbx-key. found=false if missing. Idle $0.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "call_id"
    ],
    "properties": {
      "call_id": {
        "type": "string",
        "maxLength": 80,
        "minLength": 1,
        "description": "Call id (e.g. call_msp_002)."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "PBX Get Call"
}
pbx_dictionary_add 1 change
{
  "name": "pbx_dictionary_add",
  "description": "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.\n\nPOST /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.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "term",
      "alias"
    ],
    "properties": {
      "kind": {
        "enum": [
          "imei",
          "tarife",
          "oda",
          "oda_tipi",
          "klima",
          "check_out",
          "iade",
          "sku",
          "police",
          "hasar",
          "yenileme",
          "abone",
          "kesinti",
          "fatura",
          "kart",
          "iban",
          "sube",
          "other"
        ],
        "type": "string",
        "description": "Fact kind; inferred from seed term when omitted."
      },
      "term": {
        "type": "string",
        "maxLength": 64,
        "minLength": 2,
        "description": "Canonical term (e.g. AC, tariff). Plain Turkish preferred."
      },
      "alias": {
        "type": "string",
        "maxLength": 64,
        "minLength": 2,
        "description": "Synonym / alias to add (e.g. cooling, line package)."
      },
      "boost": {
        "type": "number",
        "maximum": 5,
        "minimum": 1,
        "description": "Search boost weight (default 2)."
      },
      "scope": {
        "enum": [
          "pbx",
          "global"
        ],
        "type": "string",
        "description": "pbx = scoped to x-temsor-pbx-key; global = demo-wide. Default: pbx if registered key, else global."
      },
      "domain": {
        "enum": [
          "hotel",
          "pbx_provider",
          "insurance",
          "finance",
          "energy",
          "automotive",
          "otel",
          "santral_firmasi",
          "sigorta",
          "finans",
          "enerji",
          "otomotiv",
          "msp"
        ],
        "type": "string",
        "default": "hotel",
        "description": "Domain: hotel | pbx_provider | insurance | finance | energy | automotive (legacy keys + msp accepted)."
      },
      "hint_en": {
        "type": "string",
        "maxLength": 160
      },
      "hint_tr": {
        "type": "string",
        "maxLength": 160
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "PBX Dictionary Add Alias"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.temsor/api"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.temsor/api"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.temsor%2Fapi.svg)](https://glimind.com/server/mcp-registry%2Fcom.temsor%2Fapi?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.temsor%2Fapi?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.temsor%2Fapi.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.temsor%2Fapi.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.temsor%2Fapi?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:c201cfa1a12e252a…, first seen 2026-10-17, included at leaf 4538 of 23,692. Version history · verify what your client received.

Tools (43)

Compare: most reliable email servers · most reliable data servers · most reliable other servers · most reliable communication servers · most reliable knowledge servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Temsor MCP server down right now?

As of 2026-10-18 22:56 UTC, the Temsor MCP server is up with a Glimind reliability score of 75/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 21 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Temsor MCP server provide?

Temsor MCP server advertises 43 tools, including email_verify, iban_validate, pbx_audio_chunk, pbx_calls, pbx_calls_get.

How do I install Temsor MCP server?

Point your MCP client at this streamable-http endpoint: https://api.temsor.com/mcp

Is the Temsor MCP server safe to connect to an AI agent?

Glimind scanned all 43 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Temsor MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve