com.tokenofesteem/token-of-esteem
REMOTE · MCP.TOKENOFESTEEM.COM · SCANNED SEP 20
A press your agent can commission: a funny, personalized printed booklet, mailed as a gift.
Available components
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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 Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1055 tokens (~87/item across 12 items; 12 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 Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the com.tokenofesteem/token-of-esteem MCP server?
com.tokenofesteem/token-of-esteem is a hosted endpoint at https://mcp.tokenofesteem.com/v1/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 · mcp.tokenofesteem.com
claude mcp add --transport http com-tokenofesteem-token-of-esteem 'https://mcp.tokenofesteem.com/v1/mcp'
{
"mcpServers": {
"com-tokenofesteem-token-of-esteem": {
"url": "https://mcp.tokenofesteem.com/v1/mcp"
}
}
} {
"servers": {
"com-tokenofesteem-token-of-esteem": {
"type": "http",
"url": "https://mcp.tokenofesteem.com/v1/mcp"
}
}
} [mcp_servers.com-tokenofesteem-token-of-esteem] url = "https://mcp.tokenofesteem.com/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-tokenofesteem-token-of-esteem": {
"type": "remote",
"url": "https://mcp.tokenofesteem.com/v1/mcp",
"enabled": true
}
}
} openclaw mcp add com-tokenofesteem-token-of-esteem --url 'https://mcp.tokenofesteem.com/v1/mcp' --transport streamable-http
mcp_servers:
com-tokenofesteem-token-of-esteem:
url: "https://mcp.tokenofesteem.com/v1/mcp" {
"McpServers": {
"com-tokenofesteem-token-of-esteem": {
"Transport": "http",
"Url": "https://mcp.tokenofesteem.com/v1/mcp"
}
}
} assistant mcp add com-tokenofesteem-token-of-esteem -t streamable-http -u 'https://mcp.tokenofesteem.com/v1/mcp'
{
"mcpServers": {
"com-tokenofesteem-token-of-esteem": {
"type": "http",
"url": "https://mcp.tokenofesteem.com/v1/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 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
- 31 Jul 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 Jul 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
- 27 Jul 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
- 26 Jul 26 0
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 20 Sept 2026 · Probed https://mcp.tokenofesteem.com/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.tokenofesteem.com | CN=YE2,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 5d32694a868a0ff1b689e912b94e7f5c9e4 |
| SANs: mcp.tokenofesteem.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 mcp.tokenofesteem.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| tokenofesteem.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'none'; base-uri 'none'; object-src 'none'; frame-ancestors 'none'; form-action 'none'; img-src 'self' data:; style-src 'unsafe-inline' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.tokenofesteem.com/v1/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.tokenofesteem.com/v1/mcp | HTTPS enforced | 301 | https://mcp.tokenofesteem.com/v1/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 →
cancel_gift ~101
Cancel an in-flight gift and receive the refund amount. Free. Only possible before the booklet goes to print; once printing has started it fails with cancel_too_late. Pass the gift_id from create_gift and an optional reason for your records.
| Name | Type | Req | Description |
|---|---|---|---|
| gift_id | string | yes | The gift_id returned by create_gift, identifying the order to cancel. |
| reason | string | – | Optional human-readable reason for the cancellation, recorded on the order. |
No output schema declared.
No examples provided.
create_gift ~281
Place the order: write, print, and mail the booklet. CHARGES the buyer. The recipient is whoever you name in recipient, which may be your own user. Idempotent on idempotency_key for 24 hours. Pass shared_payment_token to pay tokenlessly, or omit it to charge the account's saved card.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_note | string | – | Optional note from the agent, stored with the order for support. Never printed in the booklet. |
| brief | object | yes | Structured brief about the recipient: what to celebrate, what to tease gently, and the inside jokes worth knowing. |
| format | string | – | Booklet format. Only manual_v1, a 16-page booklet, is supported today. |
| idempotency_key | string | yes | Caller-chosen key that makes this order idempotent for 24 hours. Reuse the same key to retry safely without charging twice. |
| preview_before_print | boolean | – | If true, the gift pauses for buyer review before printing instead of printing automatically. |
| recipient | – | yes | Who receives the booklet and where to mail it. Pass an inline recipient with a US ship_to, or a saved recipient_id. |
| shared_payment_token | string | – | Single-use Stripe Shared Payment Token (spt_...) to pay without a stored card. Omit to charge the account default. |
No output schema declared.
No examples provided.
create_setup_link ~51
Return a hosted Stripe link for the buyer to save a card or wallet to the account. After that, create_gift without a shared_payment_token charges the saved card.
| Name | Type | Req | Description |
|---|---|---|---|
| return_url | string | – | – |
No output schema declared.
No examples provided.
get_account ~32
Return this account's spending caps and month-to-date spend. Free. Use it to confirm budget before create_gift.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_gift ~107
Fetch a gift by gift_id and return its full resource: status, voice, format, pricing, the recipient, and fulfillment (Lulu job id, carrier, tracking URL, estimated delivery). Free and read-only. Use it to poll progress after create_gift: status advances through the pipeline to shipped then delivered, or ends at held, refused, cancelled, or failed.
| Name | Type | Req | Description |
|---|---|---|---|
| gift_id | string | yes | The gift_id returned by create_gift, identifying the order to fetch. |
No output schema declared.
No examples provided.
get_pricing ~140
Compute the exact total for a hypothetical gift (format, voice, image model, ship_to) before you commit. Free, no order is created. Call before create_gift so you know the charge.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Booklet format to price. Only manual_v1 is supported today. |
| image_model | string | – | Optional cover image model id. Some models add a small per-call cost. |
| ship_to | object | yes | Destination address. US is supported; the total and tax depend on the destination. |
| voice | string | – | Optional comedic voice. It does not change the price; accepted for parity with create_gift. |
No output schema declared.
No examples provided.
list_formats ~34
List supported booklet formats. There is one today: manual_v1, a 16-page booklet. Free, no side effects.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_gifts ~111
Paginated list of gifts on the account, with optional status and date filters. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque pagination cursor from a previous list_gifts response. |
| limit | integer | – | Maximum number of gifts to return, 1 to 100. Defaults to 50. |
| since | string | – | Only return gifts created at or after this ISO 8601 timestamp. |
| status | string | – | Only return gifts in this status, for example shipped, delivered, or cancelled. |
No output schema declared.
No examples provided.
list_image_models ~26
List supported cover image models and their per-call cost. Free, no side effects.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_recipients ~39
Return the account's saved recipients (address book). Free. Reuse a recipient_id in create_gift instead of re-entering an address.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_voices ~51
List the three comedic voices (Hype Man, Best Friend Roast, Conspiracy Theorist) and the cover image model each prefers. Free, no side effects. Call this first to pick a voice.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
validate_brief ~82
Run the content policy on a brief without charging or ordering. Free. Call before create_gift so a refusal surfaces early. A booklet that would wound the recipient is refused here, not at charge time.
| Name | Type | Req | Description |
|---|---|---|---|
| brief | object | yes | The same brief you would pass to create_gift. It is checked against the content policy, free, with no order created. |
No output schema declared.
No examples provided.
What is the com.tokenofesteem/token-of-esteem MCP server?
com.tokenofesteem/token-of-esteem is an MCP server listed in the public MCP registry as com.tokenofesteem/token-of-esteem. A press your agent can commission: a funny, personalized printed booklet, mailed as a gift. This page covers its hosted endpoint (https://mcp.tokenofesteem.com/v1/mcp).
Is the com.tokenofesteem/token-of-esteem MCP server safe to use?
com.tokenofesteem/token-of-esteem scores 88 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.tokenofesteem/token-of-esteem MCP server expose?
com.tokenofesteem/token-of-esteem exposes 12 tools: list_voices, list_formats, list_image_models, get_pricing, validate_brief, and 7 more. Their descriptions and schemas cost roughly 1,055 tokens of context every time the server is loaded.
Does the com.tokenofesteem/token-of-esteem MCP server require authentication?
Yes. com.tokenofesteem/token-of-esteem asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the com.tokenofesteem/token-of-esteem MCP server still maintained?
com.tokenofesteem/token-of-esteem is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.