# Telofy (remote · api.telofy.app)

AI phone receptionist for small businesses: read calls, leads and booked appointments.

- Trust score: 82/100 (high trust)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.telofy.app`: 82/100 (this document), [markdown](https://verifymcp.io/servers/app-telofy-telofy/api.md), [page](https://verifymcp.io/servers/app-telofy-telofy/api)

## Channel facts

- Endpoint: `https://api.telofy.app/mcp`
- Transports: `streamable-http`
- Auth: `required`
- 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-11-05.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Telofy MCP server?

Telofy is a hosted endpoint at https://api.telofy.app/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.

### Claude

```bash
claude mcp add --transport http app-telofy-telofy 'https://api.telofy.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-telofy-telofy": {
      "url": "https://api.telofy.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-telofy-telofy": {
      "type": "http",
      "url": "https://api.telofy.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-telofy-telofy]
url = "https://api.telofy.app/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add app-telofy-telofy --url 'https://api.telofy.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-telofy-telofy:
    url: "https://api.telofy.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-telofy-telofy": {
      "Transport": "http",
      "Url": "https://api.telofy.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-telofy-telofy -t streamable-http -u 'https://api.telofy.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-telofy-telofy": {
      "type": "http",
      "url": "https://api.telofy.app/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-11-05 (score 82, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: pass → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-30 (score 82, +1)

- [security] Stability: 0.97 → pass

### 2026-10-28 (score 81, +1)

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

### 2026-10-26 (score 80, +1)

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

### 2026-10-24 (score 79, +1)

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

### 2026-10-22 (score 78, +1)

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

### 2026-10-20 (score 77, +1)

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

### 2026-10-17 (score 76, +1)

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

## MCP tools (3)

### `list_calls` (~71 tokens)

Listet die Anrufe dieses Tenants, neueste zuerst. Identisch zu GET /api/v1/calls.

Input parameters:

- `limit` (integer): Einträge pro Seite (Standard: 50, maximal 100).
- `page` (integer): 1-basierte Seitenzahl (Standard: 1).

### `list_outcomes` (~83 tokens)

Listet die erfassten Anruf-Ergebnisse (Leads/Tickets/Termine/Infos) dieses Tenants. Identisch zu GET /api/v1/outcomes.

Input parameters:

- `limit` (integer): Einträge pro Seite (Standard: 50, maximal 100).
- `page` (integer): 1-basierte Seitenzahl (Standard: 1).

### `list_appointments` (~74 tokens)

Listet die als Termin erfassten Anruf-Ergebnisse dieses Tenants. Identisch zu GET /api/v1/appointments.

Input parameters:

- `limit` (integer): Einträge pro Seite (Standard: 50, maximal 100).
- `page` (integer): 1-basierte Seitenzahl (Standard: 1).

## Diagnostics

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

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 82
- 2026-10-30: 82
- 2026-10-29: 81
- 2026-10-28: 81
- 2026-10-27: 80
- 2026-10-26: 80
- 2026-10-25: 79
- 2026-10-24: 79
- 2026-10-23: 78
- 2026-10-22: 78
- 2026-10-21: 77
- 2026-10-20: 77
- 2026-10-19: 76
- 2026-10-18: 76
- 2026-10-17: 76
- 2026-10-16: 75
- 2026-10-15: 75
- 2026-10-14: 74
- 2026-10-13: 74
- 2026-10-12: 73
- 2026-10-10: 72
- 2026-10-09: 72
- 2026-10-07: 71
- 2026-10-06: 70
- 2026-10-04: 69

## Common questions

### What is the Telofy MCP server?

Telofy is an MCP server listed in the public MCP registry as app.telofy/telofy. AI phone receptionist for small businesses: read calls, leads and booked appointments. This page covers its hosted endpoint (https://api.telofy.app/mcp).

### Is the Telofy MCP server safe to use?

Telofy scores 82 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 Telofy MCP server expose?

Telofy exposes 3 tools: list_calls, list_outcomes, list_appointments. Their descriptions and schemas cost roughly 228 tokens of context every time the server is loaded.

### Does the Telofy MCP server require authentication?

Its publisher declares that Telofy requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.

### Is the Telofy MCP server still maintained?

Telofy is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.telofy.app/mcp
- Authorisation metadata: https://api.telofy.app/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/RuJerome/telofy-mcp
- Website: https://telofy.de/
- Changelog RSS feed: https://verifymcp.io/servers/app-telofy-telofy/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-telofy-telofy/api.json
- HTML version of this page: https://verifymcp.io/servers/app-telofy-telofy/api