Call Desk
REMOTE · MCP.MODERNMUSTARDSEED.COM
US and Canada calling rules: number checks, calling hours, recording consent, AI voice disclosure.
Available components
Last scanned (16 hours ago)
Scores higher than 71% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Communication
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1365 tokens (~273/item across 5 items; 5 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 Management33
- Stability observed for 10 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +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.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 72
First indexed and scored.
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 22 Oct 2026 · Probed https://mcp.modernmustardseed.com/call-desk
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.modernmustardseed.com | CN=YR2,O=Let's Encrypt,C=US | 11 Oct 2026 | 9 Jan 2027 | RSA 2048 | SHA256-RSA | 5037aab1b1b95f22d0713db17fad3a7354f |
| SANs: mcp.modernmustardseed.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.modernmustardseed.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| modernmustardseed.com. | 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 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.modernmustardseed.com/call-desk | Verified | 200 | |
| http (plaintext) | http://mcp.modernmustardseed.com/call-desk | HTTPS enforced | 308 | https://mcp.modernmustardseed.com/call-desk |
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 →
ai_voice_disclosure_rules AI voice disclosure rules ~203
List the laws that require a caller or conversational agent to disclose that it is AI, a bot, or an artificial or prerecorded voice, for a US state, Canadian province or phone number, or for every jurisdiction. Covers the FCC ruling that AI-generated voices are artificial voices under the TCPA (so AI voice calls need prior express consent), the federal rule that prerecorded messages identify the caller at the start, state AI and chatbot disclosure laws, and state rules on identifying automated messages. Each rule gives what must be disclosed, when, who it applies to, effective and sunset dates, whether it is in force today, the citation, a verbatim quote, the source URL and as-of date. Informational, not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| phone_number | string | – | Instead of a state: a phone number; its area code gives the state. |
| state | string | – | A US state, DC, territory or Canadian province, as a code or name. |
No output schema declared.
No examples provided.
can_i_call_now Can I call now ~416
Decide whether a call to a phone number, or to someone in a given state or province, is allowed right now or at a given time under calling-hours law: the FCC TCPA rule and FTC Telemarketing Sales Rule (8 a.m. to 9 p.m. called party's local time), every stricter state rule we verified (for example Florida, Oklahoma, Maryland, Washington and Wyoming stop at 8 p.m.; Texas Sundays start at noon; Pennsylvania bans Sundays from 2026-10-18; Kentucky starts at 10 a.m.; Maine allows automated solicitation weekdays 9 to 5 only), and in Canada the CRTC rules and British Columbia's holiday ban. Checks every time zone the number could be in, state holiday bans and future effective dates. Returns allowed or not, the reason, the window today, the next allowed time, and every rule applied with its citation, verbatim quote, source URL and as-of date. Choose call_type: sales_automated covers AI voice agents, prerecorded and autodialed sales calls. Informational, not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| at | string | – | Check a time other than now: ISO 8601 with an offset, for example 2026-10-19T09:30:00-05:00. |
| call_type | string | – | sales_automated (default): a sales call by AI voice, prerecorded message or autodialer. sales_live: a sales call by a person. automated_non_sales: an automated or AI-voice call that sells nothing (re… |
| phone_number | string | – | The number to be called. Its area code and exchange give the state and time zones. |
| state | string | – | Instead of a number: the called person's US state, DC, US territory or Canadian province, as a code (TX) or name (Texas). States with several time zones are checked in all of them. |
No output schema declared.
No examples provided.
check_phone_number Check a phone number ~245
Check a US, Canadian or other North American (+1) phone number before calling or texting it. Returns whether it can be a working number (N11 codes and unassigned area codes fail; 555-0100 to 0199, reserved for fiction, is flagged as fictional_range and still resolves), the E.164 form, where the area code rings (US state or territory, Canadian province, or another country on the +1 plan), whether the area code is in service, its overlays, every time zone the exchange covers with the current local time there, and a toll-fraud risk grade (block, high, medium, low) with reasons: Caribbean and Bermuda +1 codes that bill as international calls, 900 premium numbers, Pacific territory codes, non-geographic codes and the 976 exchange. Area code data from NANPA, time zones from libphonenumber; no network access. Informational, not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| phone_number | string | yes | The number in any common format: (406) 555-0123, +1 406 555 0123, 1-800-FLOWERS, or with an extension. |
No output schema declared.
No examples provided.
list_state_calling_rules List state calling rules ~161
Show every calling rule Call Desk holds for one US state, DC, territory or Canadian province: its time zones and area codes, federal and state calling-hours rules with windows, holidays and per-day call caps, recording consent, AI disclosure and automated message rules, each with citation, quote, source URL and as-of date, plus any rule we looked for and could not verify. With no state, returns a table of every jurisdiction with hours stricter than federal, the states with no stricter rule, and the all-party recording states. Informational, not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | – | A US state, DC, territory or Canadian province, as a code (OK) or name (Oklahoma). Leave out for the overview. |
No output schema declared.
No examples provided.
recording_consent_rules Recording consent rules ~200
Look up whether a phone call may be recorded with one party's consent or needs every party's consent, for one or more US states, DC or Canadian provinces, by state or by the phone numbers on the call. Returns each jurisdiction's rule (one-party, all-party or mixed, such as Oregon, Connecticut, Nevada or Michigan, with the case law that decides it), the statute, a verbatim quote, the source URL and as-of date, the federal rule (18 U.S.C. 2511(2)(d)), and a bottom line for calls that cross state lines. With no input, returns the lists of all-party, mixed and one-party states. Informational, not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| phone_numbers | array | – | Phone numbers of the people on the call; each maps to its area code's state. |
| states | array | – | States or provinces of the people on the call, as codes or names. |
No output schema declared.
No examples provided.
How do I install the Call Desk MCP server?
Call Desk is a hosted endpoint at https://mcp.modernmustardseed.com/call-desk, 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 · mcp.modernmustardseed.com
claude mcp add --transport http com-modernmustardseed-call-desk 'https://mcp.modernmustardseed.com/call-desk'
What is the Call Desk MCP server?
Call Desk is an MCP server listed in the public MCP registry as com.modernmustardseed/call-desk. US and Canada calling rules: number checks, calling hours, recording consent, AI voice disclosure. This page covers its hosted endpoint (https://mcp.modernmustardseed.com/call-desk).
Is the Call Desk MCP server safe to use?
Call Desk scores 76 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 Call Desk MCP server expose?
Call Desk exposes 5 tools: check_phone_number, can_i_call_now, recording_consent_rules, ai_voice_disclosure_rules, list_state_calling_rules. Their descriptions and schemas cost roughly 1,225 tokens of context every time the server is loaded.
Does the Call Desk MCP server require authentication?
No. We connected to Call Desk without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Call Desk MCP server still maintained?
Call Desk is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.