# Go-To Local Missed-Call Calculator (remote · gotolocalai.com)

Estimate what missed calls cost a local service business each month, with the formula shown.

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `gotolocalai.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/com-gotolocalai-missed-call-calculator/gotolocalai.md), [page](https://verifymcp.io/servers/com-gotolocalai-missed-call-calculator/gotolocalai)

## Channel facts

- Endpoint: `https://gotolocalai.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-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 486 tokens (~243/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Go-To Local Missed-Call Calculator MCP server?

Go-To Local Missed-Call Calculator is a hosted endpoint at https://gotolocalai.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.

### Claude

```bash
claude mcp add --transport http com-gotolocalai-missed-call-calculator 'https://gotolocalai.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-gotolocalai-missed-call-calculator": {
      "url": "https://gotolocalai.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-gotolocalai-missed-call-calculator": {
      "type": "http",
      "url": "https://gotolocalai.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-gotolocalai-missed-call-calculator]
url = "https://gotolocalai.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-gotolocalai-missed-call-calculator": {
      "type": "remote",
      "url": "https://gotolocalai.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-gotolocalai-missed-call-calculator --url 'https://gotolocalai.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-gotolocalai-missed-call-calculator:
    url: "https://gotolocalai.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-gotolocalai-missed-call-calculator": {
      "Transport": "http",
      "Url": "https://gotolocalai.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-gotolocalai-missed-call-calculator -t streamable-http -u 'https://gotolocalai.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-gotolocalai-missed-call-calculator": {
      "type": "http",
      "url": "https://gotolocalai.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-11-21 (score 77, +1)

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

### 2026-11-19 (score 76, +1)

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

### 2026-11-17 (score 75, +1)

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

### 2026-11-14 (score 74, +1)

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

### 2026-11-12 (score 73, +1)

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

### 2026-11-11 (score 72, 0)

- [security] Tool “what_is_an_ai_employee” rewrote its description, which is the text the model reads

### 2026-11-10 (score 72, +1)

- [security] Tool “what_is_an_ai_employee” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03

### 2026-11-09 (score 71)

First indexed and scored.

## MCP tools (2)

### `missed_call_cost` (~251 tokens)

Missed-call cost estimate

Estimates what missed calls may be costing a local service business each month, using the same formula as the free calculator at https://gotolocalai.com/missed-call-calculator: missed calls a week x 4.33 weeks a month x (share of answered calls that become jobs / 100) x average job value. It is plain arithmetic on the three numbers you give it, so there is no data to go stale, and the result is a rough estimate, not a forecast. Inputs: missed_calls_per_week, avg_job_value (US dollars) and close_rate (a percent: 40 means 40%). Source: Go-To Local, https://gotolocalai.com.

Input parameters:

- `avg_job_value` (number, required): What a typical job pays the business, in US dollars. A number from 0 to 10000000.
- `close_rate` (number, required): Percent of answered calls that become jobs, written as a percent: 40 means 40%. A number from 0 to 100.
- `missed_calls_per_week` (number, required): Calls the business misses in a typical week, voicemails and unanswered rings included. A number from 0 to 10000.

### `what_is_an_ai_employee` (~138 tokens)

What is an AI employee?

Explains what an AI employee is at Go-To Local, a Denver company that builds and runs AI employees for local service businesses in Colorado, North Carolina and South Carolina: the five employees, the two jobs they fall under (answer every customer, and reach out to new customers) and where each stands today, the founding pilot price, what the company says it will not do, and that an AI employee tells callers at the start that it is an AI assistant. The text is taken from the Go-To Local website (https://gotolocalai.com/employees) and reflects the site as of its last deploy. No input.

## Diagnostics

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

## Score history

- 2026-11-21: 77
- 2026-11-20: 76
- 2026-11-19: 76
- 2026-11-18: 75
- 2026-11-17: 75
- 2026-11-16: 74
- 2026-11-15: 74
- 2026-11-14: 74
- 2026-11-13: 73
- 2026-11-12: 73
- 2026-11-11: 72
- 2026-11-10: 72
- 2026-11-09: 71

## Common questions

### What is the Go-To Local Missed-Call Calculator MCP server?

Go-To Local Missed-Call Calculator is an MCP server listed in the public MCP registry as com.gotolocalai/missed-call-calculator. Estimate what missed calls cost a local service business each month, with the formula shown. This page covers its hosted endpoint (https://gotolocalai.com/mcp).

### Is the Go-To Local Missed-Call Calculator MCP server safe to use?

Go-To Local Missed-Call Calculator scores 77 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 Go-To Local Missed-Call Calculator MCP server expose?

Go-To Local Missed-Call Calculator exposes 2 tools: missed_call_cost, what_is_an_ai_employee. Their descriptions and schemas cost roughly 389 tokens of context every time the server is loaded.

### Does the Go-To Local Missed-Call Calculator MCP server require authentication?

No. We connected to Go-To Local Missed-Call Calculator without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Go-To Local Missed-Call Calculator MCP server still maintained?

Go-To Local Missed-Call Calculator 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 Go-To Local Missed-Call Calculator MCP server?

VerifyMCP ran 13 checks on Go-To Local Missed-Call Calculator, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.

## Links

- Remote endpoint: https://gotolocalai.com/mcp
- Website: https://gotolocalai.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-gotolocalai-missed-call-calculator/gotolocalai.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-gotolocalai-missed-call-calculator/gotolocalai/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-gotolocalai-missed-call-calculator/gotolocalai.json
- HTML version of this page: https://verifymcp.io/servers/com-gotolocalai-missed-call-calculator/gotolocalai
