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.

Everyday Software Voice Demo

REMOTE · EVERYDAYSOFTWARE.AI

Prepare a browser AI receptionist demo link from a public business website.

+3 this week 80 Trust /100

Last scanned (7 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 5 Nov 2026.

Category AI and Machine Learning

Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 167 tokens (~167/item across 1 items; 1 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
  • Stability observed for 19 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 4 Nov 26 +1

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

  • 2 Nov 26 +1

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

  • 31 Oct 26 +1

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

  • 29 Oct 26 +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.

  • 27 Oct 26 +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.

  • 25 Oct 26 +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.

  • 23 Oct 26 +1

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

  • 20 Oct 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.

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 5 Nov 2026 · Probed https://everydaysoftware.ai/mcp/voice-demo

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=everydaysoftware.ai CN=WR3,O=Google Trust Services,C=US 27 Oct 2026 25 Jan 2027 RSA 2048 SHA256-RSA f180503caeca39e512bc467af7107a18
SANs: everydaysoftware.ai
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of everydaysoftware.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
everydaysoftware.ai. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://everydaysoftware.ai/mcp/voice-demo Verified 200
http (plaintext) http://everydaysoftware.ai/mcp/voice-demo HTTPS enforced 302 https://everydaysoftware.ai/mcp/voice-demo
MCP tools · 1 exposed · ~104 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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
prepare_voice_demo_link ~104

Use when the user wants to try a free AI receptionist demo based on a public business website. Returns a link with the website prefilled. Does not fetch the site, start a voice call, send a message, create a phone number, or deploy an agent. The user builds and starts the demo in their browser.

NameTypeReqDescription
website_urlstringyesPublic business homepage, for example https://example.com. No account pages or credentials. Paths and queries are removed.
NameTypeReqDescription
demo_urlstringyes–
limitsstringyes–
next_stepsarrayyes–
source_websitestringyes–
statusstringyes–

No examples provided.

Install

How do I install the Everyday Software Voice Demo MCP server?

Everyday Software Voice Demo is a hosted endpoint at https://everydaysoftware.ai/mcp/voice-demo, 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.

remote · everydaysoftware.ai

# add to Claude Code
claude mcp add --transport http ppineapple-everydaysoftware-voice-demo 'https://everydaysoftware.ai/mcp/voice-demo'
Common questions

What is the Everyday Software Voice Demo MCP server?

Everyday Software Voice Demo is an MCP server listed in the public MCP registry as io.github.PpiNeaPpLe/everydaysoftware-voice-demo. Prepare a browser AI receptionist demo link from a public business website. This page covers its hosted endpoint (https://everydaysoftware.ai/mcp/voice-demo).

Is the Everyday Software Voice Demo MCP server safe to use?

Everyday Software Voice Demo scores 80 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 Everyday Software Voice Demo MCP server expose?

Everyday Software Voice Demo exposes 1 tool: prepare_voice_demo_link. Their descriptions and schemas cost roughly 104 tokens of context every time the server is loaded.

Does the Everyday Software Voice Demo MCP server require authentication?

No. We connected to Everyday Software Voice Demo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Everyday Software Voice Demo MCP server still maintained?

Everyday Software Voice Demo is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.