Dmitry Voluntary Support
REMOTE · DMITRY-AGENT-APPEAL.ORANGESLUG16.CHATGPT.SITE
Read a voluntary personal appeal, USDC receiving details, and submit private proposals.
Available components
Last scanned (20 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Crypto and Web3
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
- 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
- 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 Usability62
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 228 tokens (~45/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage70
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 11% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 4 Nov 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.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 30 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.
- 28 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.
- 26 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.
- 24 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.
- 22 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 21 Oct 26 66
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 4 Nov 2026 · Probed https://dmitry-agent-appeal.orangeslug16.chatgpt.site/agent-mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.orangeslug16.chatgpt.site | CN=WE1,O=Google Trust Services,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 81b68ca024476dd90efadf98bc7b95dc |
| SANs: *.orangeslug16.chatgpt.site | ||||||
| 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 dmitry-agent-appeal.orangeslug16.chatgpt.site. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| site. | present | 31826 | 13 | Verified |
| chatgpt.site. | 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 |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dmitry-agent-appeal.orangeslug16.chatgpt.site/agent-mcp | Verified | 200 | |
| http (plaintext) | http://dmitry-agent-appeal.orangeslug16.chatgpt.site/agent-mcp | HTTPS enforced | 302 | https://dmitry-agent-appeal.orangeslug16.chatgpt.site/agent-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 →
get_appeal ~27
Read Dmitry’s public, voluntary personal appeal, its verification limits and reply options.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_crypto_support ~42
Read the owner-activated USDC receiving address on Base. An optional amount returns unsigned transfer instructions; this tool never sends funds.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | – |
No output schema declared.
No examples provided.
get_open_tasks ~23
Read bounded, optional contribution tasks. No compensation or reward is promised.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_receipt ~39
Check acknowledgement status using the ID and private receipt token returned by submit_offer.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| receipt_token | string | yes | – |
No output schema declared.
No examples provided.
submit_offer ~97
Store a voluntary proposal in Dmitry’s private inbox. No money is transferred and no submitted instructions are automatically executed. Human review is pending.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | yes | – |
| category | string | – | – |
| is_test | boolean | – | – |
| message | string | yes | – |
| reply_to | string | – | Public agent/thread HTTPS URL or Nostr public identity, not personal contact details. |
| task_id | string | – | – |
No output schema declared.
No examples provided.
How do I install the Dmitry Voluntary Support MCP server?
Dmitry Voluntary Support is a hosted endpoint at https://dmitry-agent-appeal.orangeslug16.chatgpt.site/agent-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 · dmitry-agent-appeal.orangeslug16.chatgpt.site
claude mcp add --transport http site-chatgpt-orangeslug16-dmitry-agent-appeal-vo 'https://dmitry-agent-appeal.orangeslug16.chatgpt.site/agent-mcp'
What is the Dmitry Voluntary Support MCP server?
Dmitry Voluntary Support is an MCP server listed in the public MCP registry as site.chatgpt.orangeslug16.dmitry-agent-appeal/voluntary-sup…. Read a voluntary personal appeal, USDC receiving details, and submit private proposals. This page covers its hosted endpoint (https://dmitry-agent-appeal.orangeslug16.chatgpt.site/agent-mcp).
Is the Dmitry Voluntary Support MCP server safe to use?
Dmitry Voluntary Support scores 73 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 Dmitry Voluntary Support MCP server expose?
Dmitry Voluntary Support exposes 5 tools: get_appeal, get_open_tasks, get_crypto_support, submit_offer, get_receipt. Their descriptions and schemas cost roughly 228 tokens of context every time the server is loaded.
Does the Dmitry Voluntary Support MCP server require authentication?
No. We connected to Dmitry Voluntary Support without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Dmitry Voluntary Support MCP server still maintained?
Dmitry Voluntary Support is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.