Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Token Counter

REMOTE · APISHED.COM · SCANNED AUG 20

Counts tokens under OpenAI-compatible (tiktoken) encodings, by model or encoding name.

Available components

64 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security60
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 112 tokens (~112/item across 1 items; 1 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
  • 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · apished.com

# add to Claude Code
claude mcp add --transport http com-apished-token-counter https://apished.com/mcp/v1/tokens
# ~/.codex/config.toml
[mcp_servers.com-apished-token-counter]
url = "https://apished.com/mcp/v1/tokens"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-apished-token-counter": {
      "type": "remote",
      "url": "https://apished.com/mcp/v1/tokens",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-apished-token-counter --url https://apished.com/mcp/v1/tokens --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-apished-token-counter:
    url: "https://apished.com/mcp/v1/tokens"
// mcp.json
{
  "mcpServers": {
    "com-apished-token-counter": {
      "type": "http",
      "url": "https://apished.com/mcp/v1/tokens"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 20 Aug 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.

  • 19 Aug 26 0
    • Stability: unverified → 0.03 functional
  • 18 Aug 26 63

    First indexed and scored.

Diagnostics

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 Aug 2026 · Probed https://apished.com/mcp/v1/tokens

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=apished.com CN=YR2,O=Let's Encrypt,C=US 17 Aug 2026 15 Nov 2026 RSA 4096 SHA256-RSA 5f4dfa5fcafb280b9204690908ddbca6b5c
SANs: apished.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
DNSSEC secure

Validation of apished.com. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
apished.com. present 38629 8 Verified
apished.com. Verified address RRset verified with the apex keys
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
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://apished.com/mcp/v1/tokens Verified 200
http (plaintext) http://apished.com/mcp/v1/tokens HTTPS enforced 301 https://apished.com/mcp/v1/tokens
MCP tools · 1 exposed · ~112 tokens

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.

Tool Tokens
tokens_count ~112

Counts tokens under an OpenAI-compatible (tiktoken) encoding. Provide exactly one of model (e.g. "gpt-4o") or encoding ("o200k_base" or "cl100k_base"). No Claude/Anthropic tokenizer.

NameTypeReqDescription
encodingstringo200k_base or cl100k_base; exactly one of model/encoding
modelstringe.g. gpt-4o; exactly one of model/encoding
textstringyes
NameTypeReqDescription
encodingstring
tokensintegeryes

No examples provided.