com.comparecallanswering/site
REMOTE · COMPARECALLANSWERING.COM
Compare Call Answering: the site's own MCP server — compare, enquiry (enquiry = a human handoff,...
Available components
Last scanned (18 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 810 tokens (~135/item across 6 items; 6 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 13 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “submit_enquiry” rewrote its description, which is the text the model reads security
- Schema quality: excellent → good functional
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Oct 26 0
- Stability: 0.93 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 21 Nov 2026 · Probed https://comparecallanswering.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=comparecallanswering.com | CN=WE1,O=Google Trust Services,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 8133627d0cf1dab513de0747ffbf423e |
| SANs: comparecallanswering.com, *.comparecallanswering.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of comparecallanswering.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| comparecallanswering.com. | No DS | 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://comparecallanswering.com/mcp | Verified | 200 | |
| http (plaintext) | http://comparecallanswering.com/mcp | HTTPS enforced | 301 | https://comparecallanswering.com/mcp |
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 →
compare_criteria What is compared ~28
The criteria and any filters of the Four call answering models, compared on what actually differs comparison.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
compare_options The options ~57
The options in the Four call answering models, compared on what actually differs comparison (name, what it is best for, tags), optionally filtered by a tag value.
| Name | Type | Req | Description |
|---|---|---|---|
| filterKey | string | – | – |
| filterValue | string | – | – |
No output schema declared.
No examples provided.
compare_table The comparison table ~47
Each option's value on every criterion of the Four call answering models, compared on what actually differs comparison — the full table.
| Name | Type | Req | Description |
|---|---|---|---|
| option | string | – | one option's name, else all |
No output schema declared.
No examples provided.
enquiry_describe What you get: an ENQUIRY with a human (not a purchase, not a guaranteed quote) ~70
Read first. States plainly what submit_enquiry does on Compare Call Answering: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the details, the consent wording, and how the person confirms.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
enquiry_fields The questions the enquiry asks ~49
Every field of the Compare Call Answering enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
submit_enquiry Submit an ENQUIRY to human providers (two steps; not a purchase) ~280
Submits an enquiry to Compare Call Answering: NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token; show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "Send my contact details to up to three call answering providers, chosen by Compare Call Answering, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | yes | the person's answers, keyed by field key |
| confirmation | string | – | the confirmation token from step 1, after the person has approved the summary |
| consent | boolean | yes | true only when the person has agreed to: Send my contact details to up to three call answering providers, chosen by Compare Call Answering, who'll contact me directly. I'll be emailed each firm's nam… |
No output schema declared.
No examples provided.
How do I install the com.comparecallanswering/site MCP server?
com.comparecallanswering/site is a hosted endpoint at https://comparecallanswering.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.
remote · comparecallanswering.com
claude mcp add --transport http com-comparecallanswering-site 'https://comparecallanswering.com/mcp'
What is the com.comparecallanswering/site MCP server?
com.comparecallanswering/site is an MCP server listed in the public MCP registry as com.comparecallanswering/site. Compare Call Answering: the site's own MCP server, compare, enquiry (enquiry = a human handoff,... This page covers its hosted endpoint (https://comparecallanswering.com/mcp).
Is the com.comparecallanswering/site MCP server safe to use?
com.comparecallanswering/site 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 com.comparecallanswering/site MCP server expose?
com.comparecallanswering/site exposes 6 tools: compare_criteria, compare_options, compare_table, enquiry_describe, enquiry_fields, submit_enquiry. Their descriptions and schemas cost roughly 531 tokens of context every time the server is loaded.
Does the com.comparecallanswering/site MCP server require authentication?
No. We connected to com.comparecallanswering/site without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.comparecallanswering/site MCP server still maintained?
com.comparecallanswering/site 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 com.comparecallanswering/site MCP server?
VerifyMCP ran 12 checks on com.comparecallanswering/site, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about com.comparecallanswering/site: Authorization. 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.