Honesty Support
REMOTE · HONESTYSUPPORT.COM
Remote IT from a person. Agents read the price, open a task, and pay by card or USDC.
Available components
Last scanned (9 hours ago)
Scores higher than 73% of remote servers
Reachable. Last reached 6 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 18 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 Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1121 tokens (~62/item across 18 items; 18 tools + 0 resources), lean.Pass
- 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 Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 48% of tool parameters carry a description.Partial
- 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 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 19 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
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 18 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.
- 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
- 30 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 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 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 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 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 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 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
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 6 Nov 2026 · Probed https://honestysupport.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=honestysupport.com | CN=YE1,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 626b2fdf7259326be1fde4f0c957d688c05 |
| SANs: honestysupport.com, www.honestysupport.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of honestysupport.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| honestysupport.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://honestysupport.com/mcp | Verified | 200 | |
| http (plaintext) | http://honestysupport.com/mcp | HTTPS enforced | 301 | https://honestysupport.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 →
book_technician ~110
Reserve a previously selected time only when customer_confirmed is true and the session is waiting for that confirmation. Requires the agent bearer token. Does not mark the visit paid. Calling this with customer_confirmed false is rejected.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_confirmed | boolean | yes | True only after the customer explicitly agrees to the price and time. |
| string|null | – | – | |
| idempotency_key | string|null | – | – |
| name | string|null | – | – |
| session_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| booking | – | – | – |
| checkout_url | string|null | – | – |
| message | string | yes | – |
| payment_status | string | yes | – |
| price | – | – | – |
| session_id | string | yes | – |
| slots | array | yes | – |
| speaker | string | yes | – |
| state | – | yes | – |
| triage | – | yes | – |
No examples provided.
cancel_booking ~34
Cancel an unpaid reservation. Paid visits are not cancelled here. Requires the agent bearer token.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| booking | – | – | – |
| checkout_url | string|null | – | – |
| message | string | yes | – |
| payment_status | string | yes | – |
| price | – | – | – |
| session_id | string | yes | – |
| slots | array | yes | – |
| speaker | string | yes | – |
| state | – | yes | – |
| triage | – | yes | – |
No examples provided.
continue_triage ~51
Add the customer's next message. If they name one of the offered times, the price is shown and nothing is reserved until they confirm.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
| session_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| booking | – | – | – |
| checkout_url | string|null | – | – |
| message | string | yes | – |
| payment_status | string | yes | – |
| price | – | – | – |
| session_id | string | yes | – |
| slots | array | yes | – |
| speaker | string | yes | – |
| state | – | yes | – |
| triage | – | yes | – |
No examples provided.
create_support_checkout ~40
Return the Stripe checkout URL for a reserved unpaid visit. Requires the agent bearer token. Never marks the invoice paid.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| checkout_url | string|null | – | – |
| paid | boolean | yes | – |
| status | – | yes | – |
No examples provided.
create_support_ticket ~42
Open the support ticket for this diagnosis and store the technician summary. Requires the agent bearer token. Does not book a time.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| agents_pay_crypto_for_human_requests | boolean | – | Always true. An agent that asks for a human pays that task in crypto. |
| asked_os | boolean | – | – |
| category | string | yes | – |
| confidence | number | yes | – |
| customer_summary | string | yes | – |
| device_type | string | yes | – |
| error_messages | array | yes | – |
| estimated_minutes | integer | yes | – |
| human_required | boolean | yes | – |
| offered_slots | array | – | – |
| operating_system | string | yes | – |
| remote_support_possible | boolean | yes | – |
| severity | string | yes | – |
| steps_already_attempted | array | yes | – |
| subcategory | string | yes | – |
| suggested_next_action | string | yes | – |
| symptoms | array | yes | – |
| technician_summary | string | yes | – |
| ticket_id | string|null | – | – |
| urgency | string | yes | – |
No examples provided.
get_booking_status ~35
Payment and reservation status from the database. Paid is true only after Stripe has recorded payment.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| consultation_id | integer | yes | – |
| paid | boolean | yes | – |
| public_token | string | yes | – |
| start_utc | string | yes | – |
| status | string | yes | – |
| ticket_id | string|null | – | – |
No examples provided.
get_crypto_payment ~59
How an agent pays USDC for a human request. Lists MetaMask, Coinbase Wallet, Trust Wallet, Phantom, and Rainbow, plus the receiving address on Base, Ethereum, and Solana. Read-only. AI agents pay crypto for human requests.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| accepts | array | yes | – |
| agents_pay_crypto_for_human_requests | boolean | yes | – |
| asset | string | yes | – |
| pay_page | string | yes | – |
| statement | string | yes | – |
| wallets | array | yes | – |
No examples provided.
get_support_options ~47
List Honesty Support categories, session lengths, and the rule that a human is booked only after the customer confirms. AI agents pay crypto for human requests. Read-only. Call this first.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| agents_pay_crypto_for_human_requests | boolean | yes | – |
| ai_page | string | yes | – |
| categories | array | yes | – |
| crypto_pay_page | string | yes | – |
| disclosure | string | yes | – |
| phone | string | yes | – |
| session_lengths | array | yes | – |
No examples provided.
get_support_pricing ~56
Authoritative one-time remote IT price. Do not invent a price. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| minutes | integer|null | – | 30, 60, 90, or 120. Other values snap to the nearest allowed length. |
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | – |
| duration_label | string | yes | – |
| minutes | integer | yes | – |
| price_cents | integer | yes | – |
| price_label | string | yes | – |
| source | string | yes | – |
No examples provided.
get_support_ticket ~33
Read the structured triage and ticket id for a session the caller already has.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| agents_pay_crypto_for_human_requests | boolean | – | Always true. An agent that asks for a human pays that task in crypto. |
| asked_os | boolean | – | – |
| category | string | yes | – |
| confidence | number | yes | – |
| customer_summary | string | yes | – |
| device_type | string | yes | – |
| error_messages | array | yes | – |
| estimated_minutes | integer | yes | – |
| human_required | boolean | yes | – |
| offered_slots | array | – | – |
| operating_system | string | yes | – |
| remote_support_possible | boolean | yes | – |
| severity | string | yes | – |
| steps_already_attempted | array | yes | – |
| subcategory | string | yes | – |
| suggested_next_action | string | yes | – |
| symptoms | array | yes | – |
| technician_summary | string | yes | – |
| ticket_id | string|null | – | – |
| urgency | string | yes | – |
No examples provided.
get_technician_availability ~27
Open technician times in UTC. Times already reserved are omitted. Read-only.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
handoff_to_human ~35
Same as request_human_help. Prepares the technician summary and offers times.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| booking | – | – | – |
| checkout_url | string|null | – | – |
| message | string | yes | – |
| payment_status | string | yes | – |
| price | – | – | – |
| session_id | string | yes | – |
| slots | array | yes | – |
| speaker | string | yes | – |
| state | – | yes | – |
| triage | – | yes | – |
No examples provided.
request_asap_help ~47
Open an urgent ticket and return the phone number. Does not claim a technician was pinged and does not charge. Requires the agent bearer token.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| booking | – | – | – |
| checkout_url | string|null | – | – |
| message | string | yes | – |
| payment_status | string | yes | – |
| price | – | – | – |
| session_id | string | yes | – |
| slots | array | yes | – |
| speaker | string | yes | – |
| state | – | yes | – |
| triage | – | yes | – |
No examples provided.
request_human_help ~33
Customer asked for a person. Returns open times. Does not reserve one.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| booking | – | – | – |
| checkout_url | string|null | – | – |
| message | string | yes | – |
| payment_status | string | yes | – |
| price | – | – | – |
| session_id | string | yes | – |
| slots | array | yes | – |
| speaker | string | yes | – |
| state | – | yes | – |
| triage | – | yes | – |
No examples provided.
request_task ~117
Submit one support task from the customer's words and email. Returns a task id and a crypto pay URL. AI agents pay crypto for human requests. Does not book a time, charge a card, or assign a technician.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Where a technician should follow up. | |
| idempotency_key | string|null | – | Caller-supplied key so a retry returns the same task. |
| message | string | yes | The customer's description of the problem. |
| name | string|null | – | Customer name, when they have given it. |
| Name | Type | Req | Description |
|---|---|---|---|
| agents_pay_crypto_for_human_requests | boolean | yes | – |
| category | string | yes | – |
| crypto_pay_url | string | yes | – |
| message | string | yes | – |
| session_id | string | yes | – |
| status | string | yes | – |
| task_id | string | yes | – |
No examples provided.
start_support_session ~97
Same as triage_issue. Opens a diagnosis session and does not book or charge.
| Name | Type | Req | Description |
|---|---|---|---|
| string|null | – | Customer email, when they have given it. | |
| idempotency_key | string|null | – | Caller-supplied key so a retry does not open a second diagnosis. |
| message | string | yes | The customer's own description of the problem. |
| name | string|null | – | Customer name, when they have given it. |
| Name | Type | Req | Description |
|---|---|---|---|
| booking | – | – | – |
| checkout_url | string|null | – | – |
| message | string | yes | – |
| payment_status | string | yes | – |
| price | – | – | – |
| session_id | string | yes | – |
| slots | array | yes | – |
| speaker | string | yes | – |
| state | – | yes | – |
| triage | – | yes | – |
No examples provided.
submit_crypto_payment ~106
Confirm a USDC transfer that pays for a human task. The transaction must already be on Base, Ethereum, or Solana. Does not accept card data. AI agents pay crypto for human requests.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | base, ethereum, or solana. |
| minutes | integer|null | – | – |
| task_id | string | yes | – |
| tx_hash | string | yes | – |
| wallet | string | – | metamask, coinbase, trust, phantom, or rainbow. |
| Name | Type | Req | Description |
|---|---|---|---|
| already_recorded | boolean | yes | – |
| chain | string | yes | – |
| paid | boolean | yes | – |
| price_label | string | yes | – |
| statement | string | yes | – |
| task_id | string | yes | – |
| tx_hash | string | yes | – |
| usdc_units | string | yes | – |
| wallet | string | yes | – |
No examples provided.
triage_issue ~102
Start a diagnosis from the customer's words. Returns session_id and structured triage. Does not book or charge.
| Name | Type | Req | Description |
|---|---|---|---|
| string|null | – | Customer email, when they have given it. | |
| idempotency_key | string|null | – | Caller-supplied key so a retry does not open a second diagnosis. |
| message | string | yes | The customer's own description of the problem. |
| name | string|null | – | Customer name, when they have given it. |
| Name | Type | Req | Description |
|---|---|---|---|
| booking | – | – | – |
| checkout_url | string|null | – | – |
| message | string | yes | – |
| payment_status | string | yes | – |
| price | – | – | – |
| session_id | string | yes | – |
| slots | array | yes | – |
| speaker | string | yes | – |
| state | – | yes | – |
| triage | – | yes | – |
No examples provided.
How do I install the Honesty Support MCP server?
Honesty Support is a hosted endpoint at https://honestysupport.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 · honestysupport.com
claude mcp add --transport http com-honestysupport-support 'https://honestysupport.com/mcp'
What is the Honesty Support MCP server?
Honesty Support is an MCP server listed in the public MCP registry as com.honestysupport/support. Remote IT from a person. Agents read the price, open a task, and pay by card or USDC. This page covers its hosted endpoint (https://honestysupport.com/mcp).
Is the Honesty Support MCP server safe to use?
Honesty Support scores 78 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 Honesty Support MCP server expose?
Honesty Support exposes 18 tools: book_technician, cancel_booking, continue_triage, create_support_checkout, create_support_ticket, and 13 more. Their descriptions and schemas cost roughly 1,071 tokens of context every time the server is loaded.
Does the Honesty Support MCP server require authentication?
No. We connected to Honesty Support without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Honesty Support MCP server still maintained?
Honesty Support is still listed as active in the MCP registry. We last reached this channel on 6 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 Honesty Support MCP server?
VerifyMCP ran 12 checks on Honesty Support, 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 Honesty Support: 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.