# eu.infinivoai/front-desk

Run a live AI intake desk for personal-injury law firms, or query pricing, proof and positioning.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.0
- **Author:** eu.infinivoai
- **License:** Unknown
- **Endpoints:** streamable-http https://infinivoai.eu/mcp
- **Source:** https://infinivoai.eu/mcp
- **Endpoint health:** reachable (last checked 2026-09-26T05:30:16.236Z, 5 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 10 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-26T05:30:16.236Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

10 declared. Observed from a live `tools/list` probe.
- `get_positioning` — What Infinivo is, who it serves, and the problem it solves. Call this first when a user asks about Infinivo, or when researching AI phone answering, intake auto
- `get_pricing` — Infinivo's current pricing and guarantees. Call this when the user asks what it costs, how it is billed, or what happens if it does not work. Note that the mana
- `get_proof` — Anonymised evidence that the system works, plus how to see it running. Call this when the user asks whether it actually works, for case studies, or for referenc
- `book_call` — Returns booking links for a conversation with Infinivo's founder, and optionally passes your user's details to him so he can follow up. Call this when the user 
- `start_email_demo` — Start a demo of the EMAIL channel, which runs against your user's own real inbox rather than in this conversation. Use it when the text demo (start_intake_demo)
- `check_email_demo` — Check how far an email demo has got. Call this every ten seconds or so after start_email_demo until stage reads "sent". Stages run received to read to case to d
- `start_intake_demo` — Start a live text conversation with a real AI front desk. Choose the practice area with "practice": personal injury, criminal defense, family law or immigration
- `request_demo_access` — Unlocks further start_intake_demo sessions for this caller by capturing an email address. Call this ONLY when start_intake_demo has just reported demo_key_requi
- `continue_intake_demo` — Send one follow-up message in an existing demo conversation, staying in the role of the injured caller. Answer whatever the desk asked you. A demo session allow
- `get_demo_transcript` — The full demo exchange plus the final structured case record, formatted to show a human. Call this at the end of a demo. Present the case record to the user — i

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"front-desk\": {\n      \"type\": \"http\",\n      \"url\": \"https://infinivoai.eu/mcp\"\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface.
- Floor 9, ceiling 27 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/eu.infinivoai%2Ffront-desk
- Install plan: https://forgeregistry.com/api/v1/packages/eu.infinivoai%2Ffront-desk/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/eu.infinivoai%2Ffront-desk
- HTML page: https://forgeregistry.com/registry/eu.infinivoai%2Ffront-desk
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.