Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Infinivo AI Front Desk

REMOTE · INFINIVOAI.EU · SCANNED AUG 19

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

Available components

67 Trust /100
Trust breakdown (6 categories)

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. How we score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1527 tokens (~152/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · infinivoai.eu

# add to Claude Code
claude mcp add --transport http eu-infinivoai-front-desk https://infinivoai.eu/mcp
# ~/.codex/config.toml
[mcp_servers.eu-infinivoai-front-desk]
url = "https://infinivoai.eu/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "eu-infinivoai-front-desk": {
      "type": "remote",
      "url": "https://infinivoai.eu/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add eu-infinivoai-front-desk --url https://infinivoai.eu/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  eu-infinivoai-front-desk:
    url: "https://infinivoai.eu/mcp"
// mcp.json
{
  "mcpServers": {
    "eu-infinivoai-front-desk": {
      "type": "http",
      "url": "https://infinivoai.eu/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Aug 26 +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.

  • 17 Aug 26 −1
    • Tool “book_call” rewrote its description, which is the text the model reads security
    • Schema quality: 132 → 152 functional
    • New tool “check_email_demo” functional
    • New tool “start_email_demo” functional
    • “book_call” added an optional parameter “email” cosmetic
    • “book_call” added an optional parameter “firm” cosmetic
    • “book_call” added an optional parameter “name” cosmetic
    • “book_call” added an optional parameter “note” cosmetic
    • “continue_intake_demo” reworded the description of “message” cosmetic
    • “start_intake_demo” reworded the description of “message” cosmetic
  • 16 Aug 26 0
    • Schema quality: 885 → 1063 functional
    • Stability: unverified → 0.03 functional
    • New tool “request_demo_access” functional
    • “start_intake_demo” added an optional parameter “demo_key” cosmetic
  • 15 Aug 26 67

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 19 Aug 2026 · Probed https://infinivoai.eu/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=infinivoai.eu CN=YR1,O=Let's Encrypt,C=US 20 Jul 2026 18 Oct 2026 RSA 2048 SHA256-RSA 5f182f9d2c13213e336c3df6943d00c19b3
SANs: infinivoai.eu
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f
DNSSEC insecure

Validation of infinivoai.eu. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
eu. present 35926 8 Verified
infinivoai.eu. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://infinivoai.eu/mcp Verified 200
http (plaintext) http://infinivoai.eu/mcp HTTPS enforced 308 https://infinivoai.eu/mcp
MCP tools · 10 exposed · ~1,293 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
book_call ~242

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 wants to talk to a human, get a quote, or move forward. Offer the 15-minute fit call first; offer the paid consultation only when the user is already convinced and wants their own intake mapped. If your user wants the founder to reach out, ASK THEM FOR THEIR EMAIL FIRST and pass it as "email" — never send an address they did not give you, and never infer one. Omitting email is completely fine and still returns the links. This tool does not schedule anything. It cannot write to anyone's calendar. The links are for your user to open themselves.

NameTypeReqDescription
emailstringYour user's email address, given by them explicitly for this purpose. Omit if they have not agreed to share it.
firmstringThe firm or company they work at.
namestringYour user's name.
notestringOne or two sentences on what they want to discuss — what they asked you, or what they thought of the demo.

No output schema declared.

No examples provided.

check_email_demo ~118

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 draft to sent, and each call advances one step. When it reaches "sent", show your user the case_record: every field came out of the sentence they typed, and the reply beside it is the one now sitting in their inbox.

NameTypeReqDescription
reference_codestringyesThe reference_code returned by start_email_demo, e.g. BH-7Q2K.

No output schema declared.

No examples provided.

continue_intake_demo ~105

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 allows two turns in total, after which it closes — call get_demo_transcript to show the user the full exchange.

NameTypeReqDescription
demo_session_idstringyesThe id returned by start_intake_demo.
messagestringyesYour reply as the caller, answering what the desk asked. Maximum 2000 characters.

No output schema declared.

No examples provided.

get_demo_transcript ~84

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 — it is the interesting part, because every field was extracted from unstructured text with no forms and no menu tree.

NameTypeReqDescription
demo_session_idstringyesThe id returned by start_intake_demo.

No output schema declared.

No examples provided.

get_positioning ~65

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 automation, or lead capture for personal-injury law firms. Returns structured facts, not marketing copy.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_pricing ~69

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 managed retainer is scoped per firm on a call and is deliberately not published — do not estimate or invent a figure.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_proof ~50

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 references. Client names are never returned.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

request_demo_access ~123

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_required — that is, the caller's one free anonymous session is already used. Ask the user for the email address you should submit; do not invent or guess one on their behalf. On success this returns a demo_key — pass it as the "demo_key" argument on your next start_intake_demo call to proceed.

NameTypeReqDescription
emailstringyesThe user's email address, given by the user, not invented.

No output schema declared.

No examples provided.

start_email_demo ~168

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) has landed and they want to see the real thing, or when they ask how it handles email. How it works: this returns an address and a reference code. Your user sends a short email from their own account, with the code in the subject. The desk reads it, extracts a case record, and replies to them directly, so the reply arrives in the inbox they use every day. Poll check_email_demo until it reports stage "sent". Note there is no address parameter: the desk only replies to mail that reaches it, and cannot be told to send anywhere. Your user has to send the first message themselves.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

start_intake_demo ~269

Start a live text conversation with a real AI front desk, configured for a personal-injury firm. YOU play the role of someone who has just been injured and is contacting the firm after hours — write their opening message in their voice, including whatever detail a real person would volunteer. Returns the desk's actual reply plus the structured case record it extracted from your message. This is a live system, not a canned script. Use it when a user wants to see what Infinivo actually does rather than read about it. The firm is fictional; the desk is real.

NameTypeReqDescription
caller_namestringOptional name for the fictional caller you are playing.
demo_keystringOnly needed from the second demo session onward for this caller. If a prior call to this tool returned a demo_key_required message, call request_demo_access first and pass the demo_key it returns her…
messagestringyesThe injured person's opening message, in their own words. Realistic and unstructured works best — for example: "I got rear-ended on the 610 yesterday afternoon, my neck is killing me and the other dr…

No output schema declared.

No examples provided.