Is the Telofy MCP server down?

mcp-registry/app.telofy/telofy · v1.0.0

healthy
Last checked 2026-10-24 15:52 UTC · handshake 212ms

As of 2026-10-24 15:52 UTC, the Telofy MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
3,614
outages (90d)
0
tools
3

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

Install Telofy MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http telofy-mcp-server https://api.telofy.app/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

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

Agent-readiness: B (85/100)

B (85/100): 0 error(s), 1 warning(s) across 3 tool(s); ~356 tokens of tool definitions.
Scores higher than 46% of 15,643 MCP servers Glimind has audited.
Its tool list costs an agent ~356 tokens per session — lighter than 95% of servers.
84 → 85 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (2)

3 of 3 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: list_appointments, list_calls, list_outcomes

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: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fapp.telofy%2Ftelofy/fixes

list_appointments 1 change
{
  "name": "list_appointments",
  "description": "Listet die als Termin erfassten Anruf-Ergebnisse dieses Tenants. Identisch zu GET /api/v1/appointments.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "page": {
        "type": "integer",
        "minimum": 1,
        "description": "1-basierte Seitenzahl (Standard: 1)."
      },
      "limit": {
        "type": "integer",
        "maximum": 100,
        "minimum": 1,
        "description": "Einträge pro Seite (Standard: 50, maximal 100)."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
list_calls 1 change
{
  "name": "list_calls",
  "description": "Listet die Anrufe dieses Tenants, neueste zuerst. Identisch zu GET /api/v1/calls.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "page": {
        "type": "integer",
        "minimum": 1,
        "description": "1-basierte Seitenzahl (Standard: 1)."
      },
      "limit": {
        "type": "integer",
        "maximum": 100,
        "minimum": 1,
        "description": "Einträge pro Seite (Standard: 50, maximal 100)."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
list_outcomes 1 change
{
  "name": "list_outcomes",
  "description": "Listet die erfassten Anruf-Ergebnisse (Leads/Tickets/Termine/Infos) dieses Tenants. Identisch zu GET /api/v1/outcomes.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "page": {
        "type": "integer",
        "minimum": 1,
        "description": "1-basierte Seitenzahl (Standard: 1)."
      },
      "limit": {
        "type": "integer",
        "maximum": 100,
        "minimum": 1,
        "description": "Einträge pro Seite (Standard: 50, maximal 100)."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

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/app.telofy/telofy"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/app.telofy/telofy"}) 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%2Fapp.telofy%2Ftelofy.svg)](https://glimind.com/server/mcp-registry%2Fapp.telofy%2Ftelofy?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fapp.telofy%2Ftelofy?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.telofy%2Ftelofy.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.telofy%2Ftelofy.svg
   :target: https://glimind.com/server/mcp-registry%2Fapp.telofy%2Ftelofy?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:a78a77891bf83a93…, first seen 2026-10-17, included at leaf 3989 of 59,663. Version history · verify what your client received.

Tools (3)

Compare: most reliable data servers · most reliable communication 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 Telofy MCP server down right now?

As of 2026-10-24 15:52 UTC, the Telofy MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Telofy MCP server provide?

Telofy MCP server advertises 3 tools, including list_appointments, list_calls, list_outcomes.

How do I install Telofy MCP server?

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

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

Glimind scanned all 3 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 Telofy 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