APIShed

REMOTE · APISHED.COM · SCANNED AUG 20

Validates PESEL/NIP/REGON/IBAN/Luhn/ISBN/EAN/SWIFT-BIC/VAT; RPN calc, date math, hashing, tokens

Available components

65 65 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

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 29 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass

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 2220 tokens (~76/item across 29 items; 29 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 Coverage91

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
69% 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

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http com-apished-apished https://apished.com/mcp

# ~/.codex/config.toml

[mcp_servers.com-apished-apished]
url = "https://apished.com/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-apished-apished": {
      "type": "remote",
      "url": "https://apished.com/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add com-apished-apished --url https://apished.com/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  com-apished-apished:
    url: "https://apished.com/mcp"

// mcp.json

{
  "mcpServers": {
    "com-apished-apished": {
      "type": "http",
      "url": "https://apished.com/mcp"
    }
  }
}

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 64

First indexed and scored.

Show 2 earlier entries Hide earlier entries

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

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	Verified	200
http (plaintext)	http://apished.com/mcp	HTTPS enforced	301	https://apished.com/mcp

MCP tools · 29 exposed · ~2,220 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

datemath_add ~108

Adds years/months/days to date. years/months are applied together with end-of-month clamping — e.g. 2026-01-31 + 1 month = 2026-02-28, not an overflowed 2026-03-03. days is then applied as plain calendar-day arithmetic.

Input Output Examples

Name	Type	Req	Description
date	string	yes	YYYY-MM-DD
days	integer	–	–
months	integer	–	–
years	integer	–	–

Structured output declared, but exposes no named fields.

No examples provided.

datemath_age ~77

Age in whole years as of asOf (optional, defaults to the current UTC date). A Feb-29 birthDate is treated as falling on March 1 in a non-leap asOf year.

Input Output Examples

Name	Type	Req	Description
asOf	string	–	YYYY-MM-DD, defaults to today
birthDate	string	yes	YYYY-MM-DD

Structured output declared, but exposes no named fields.

No examples provided.

datemath_businessdays ~104

Counts days in [from, to] (inclusive on both ends) whose weekday is in weekdays (default mon-fri) and which aren't in holidays.

Input Output Examples

Name	Type	Req	Description
from	string	yes	YYYY-MM-DD
holidays	null\|array	–	YYYY-MM-DD dates to exclude
to	string	yes	YYYY-MM-DD
weekdays	null\|array	–	sun/mon/tue/wed/thu/fri/sat, default mon-fri

Structured output declared, but exposes no named fields.

No examples provided.

datemath_dayofweek ~50

Day of the week for date: both the weekday name and its ISO 8601 weekday number (1=Monday..7=Sunday).

Input Output Examples

Name	Type	Req	Description
date	string	yes	YYYY-MM-DD

Name	Type	Req	Description
dayOfWeek	string	yes	–
isoWeekday	integer	yes	–

No examples provided.

datemath_diff ~54

Day difference between two YYYY-MM-DD dates: to minus from, in whole days. Negative if to is before from.

Input Output Examples

Name	Type	Req	Description
from	string	yes	YYYY-MM-DD
to	string	yes	YYYY-MM-DD

Structured output declared, but exposes no named fields.

No examples provided.

datemath_leapyear ~31

Checks whether year is a leap year in the Gregorian calendar.

Input Output Examples

Name	Type	Req	Description
year	integer	yes	–

Structured output declared, but exposes no named fields.

No examples provided.

ean_validate ~86

Validates an 8-digit (EAN-8), 12-digit (UPC-A), 13-digit (EAN-13), or 14-digit (GTIN-14) barcode checksum: alternating weights 1 3 applied right-to-left, check digit is (10 - sum mod 10) mod 10.

Input Output Examples

Name	Type	Req	Description
value	string	yes	identifier or value to check

Name	Type	Req	Description
reason	string	–	–
valid	boolean	yes	–

No examples provided.

email_validate ~64

Checks value is a single, bare RFC 5322 email address — syntax only, not a deliverability check. user@localhost is valid (no TLD required). "Name <email>" display syntax is rejected.

Input Output Examples

Name	Type	Req	Description
value	string	yes	identifier or value to check

Name	Type	Req	Description
reason	string	–	–
valid	boolean	yes	–

No examples provided.

hash_digest ~110

Computes a hash digest of input (decoded per encoding: "text" default, "base64", or "hex") using algo: md5, sha1, sha256, sha512, or crc32. Returns the digest as lowercase hex.

Input Output Examples

Name	Type	Req	Description
algo	string	yes	md5, sha1, sha256, sha512, or crc32
encoding	string	–	text (default), base64, or hex
input	string	yes	data to hash, encoded per encoding

Structured output declared, but exposes no named fields.

No examples provided.

iban_validate ~66

Validates an IBAN's length for its issuing country (per the SWIFT IBAN registry) and its mod-97 checksum. Does not decompose the BBAN into a bank code/account number or resolve a BIC.

Input Output Examples

Name	Type	Req	Description
value	string	yes	identifier or value to check

Name	Type	Req	Description
reason	string	–	–
valid	boolean	yes	–

No examples provided.

isbn_validate ~77

Validates a 10- or 13-character ISBN. ISBN-10 uses weights 10..1 over 10 characters (last may be X, worth 10), sum mod 11 must be 0. ISBN-13 uses the same GTIN checksum as barcodes.

Input Output Examples

Name	Type	Req	Description
value	string	yes	identifier or value to check

Name	Type	Req	Description
reason	string	–	–
valid	boolean	yes	–

No examples provided.

jsonschema_validate ~69

Validates document against schema (JSON Schema draft-07 or 2020-12). Reports one specific violation per call, not an aggregated list.

Input Output Examples

Name	Type	Req	Description
document	–	yes	the JSON value to validate against schema
schema	–	yes	a JSON Schema (draft-07 or 2020-12)

Name	Type	Req	Description
reason	string	–	–
valid	boolean	yes	–

No examples provided.

luhn_validate ~49

Validates a numeric string against the Luhn (mod-10) checksum — payment card numbers, IMEI numbers, and similar identifiers.

Input Output Examples

Name	Type	Req	Description
value	string	yes	identifier or value to check

Name	Type	Req	Description
reason	string	–	–
valid	boolean	yes	–

No examples provided.

nip_validate ~96

Validates the checksum of a 10-digit Polish tax identification number (NIP). Checksum uses weights 6 5 7 2 3 4 5 6 7 over the first 9 digits; sum mod 11 must equal the 10th digit. A sum mod 11 of 10 is itself invalid.

Input Output Examples

Name	Type	Req	Description
value	string	yes	digits-only identifier to validate (no spaces or dashes)

Name	Type	Req	Description
reason	string	–	–
valid	boolean	yes	–

No examples provided.

pesel_validate ~128

Validates the checksum of an 11-digit Polish national identification number (PESEL). Checksum uses weights 1 3 7 9 1 3 7 9 1 3 over the first 10 digits; control digit is (10 - sum mod 10) mod 10. On success also decodes the date of birth and sex embedded in the number; a checksum-valid number with an impossible calendar date (e.g. Feb 30) is still reported invalid.

Input Output Examples

Name	Type	Req	Description
value	string	yes	digits-only identifier to validate (no spaces or dashes)

Name	Type	Req	Description
birthDate	string	–	–
reason	string	–	–
sex	string	–	–
valid	boolean	yes	–

No examples provided.

regex_match ~71

Tests input against pattern (Go's regexp package: RE2 syntax, not PCRE — no backreferences or lookaround; use inline flags like (?i) for case-insensitive matching). Returns the full match and captured groups.

Input Output Examples

Name	Type	Req	Description
input	string	yes	–
pattern	string	yes	RE2 syntax

Name	Type	Req	Description
groups	null\|array	–	–
match	string	–	–
matches	boolean	yes	–

No examples provided.

regon_validate ~170

Validates the checksum of a 9- or 14-digit Polish business registry number (REGON). 9-digit: weights 8 9 2 3 4 5 6 7 over the first 8 digits, sum mod 11 (10 mapped to 0) must equal the 9th digit. 14-digit: the first 9 digits must themselves be a valid 9-digit REGON, and weights 2 4 8 5 0 9 7 3 6 1 2 4 8 over the first 13 digits (sum mod 11, 10 mapped to 0) must equal the 14th digit.

Input Output Examples

Name	Type	Req	Description
value	string	yes	digits-only identifier to validate (no spaces or dashes)

Name	Type	Req	Description
reason	string	–	–
valid	boolean	yes	–

No examples provided.

rpncalc_eval ~120

Evaluates a Reverse Polish Notation (postfix) expression: whitespace-separated tokens, each a number or an operator/function that pops its operands off a stack and pushes the result. Supports arithmetic, exponentiation/modulo, roots, trigonometry, logarithms, rounding, bitwise ops, and constants (pi, e, phi). Always returns the decimal result — for hex/bin/oct rendering, convert the returned number yourself.

Input Output Examples

Name	Type	Req	Description
expr	string	yes	space-separated RPN expression, e.g. "3 4 + 2 *"

Structured output declared, but exposes no named fields.

No examples provided.

swiftbic_validate ~82

Structural format validation only for a SWIFT/BIC code: 8 or 11 characters (4 letters bank code + 2 letters country code + 2 alphanumeric location code + optional 3 alphanumeric branch code). The country code is not cross-checked against ISO 3166-1.

Input Output Examples

Name	Type	Req	Description
value	string	yes	identifier or value to check

Name	Type	Req	Description
reason	string	–	–
valid	boolean	yes	–

No examples provided.

text_charat ~43

Returns the 0-indexed character (rune) at index in text.

Input Output Examples

Name	Type	Req	Description
index	integer	yes	0-indexed
text	string	yes	–

Structured output declared, but exposes no named fields.

No examples provided.

text_count ~44

Counts non-overlapping occurrences of substring in text (rune-safe, not byte-based).

Input Output Examples

Name	Type	Req	Description
substring	string	yes	must be non-empty
text	string	yes	–

Structured output declared, but exposes no named fields.

No examples provided.

text_palindrome ~81

Checks whether text reads the same forwards and backwards. ignoreCase/ignoreNonAlnum default false (strict, literal comparison); set both true for phrase-style palindromes like "A man, a plan, a canal: Panama".

Input Output Examples

Name	Type	Req	Description
ignoreCase	boolean	–	–
ignoreNonAlnum	boolean	–	–
text	string	yes	–

Structured output declared, but exposes no named fields.

No examples provided.

text_reverse ~32

Reverses text by Unicode code point (rune), not grapheme cluster.

Input Output Examples

Name	Type	Req	Description
text	string	yes	–

Structured output declared, but exposes no named fields.

No examples provided.

text_sort ~70

Sorts text's characters or words alphabetically. by: "chars" (default, sorts runes, no separator) or "words" (splits on whitespace, rejoins with a single space).

Input Output Examples

Name	Type	Req	Description
by	string	–	chars (default) or words
text	string	yes	–

Structured output declared, but exposes no named fields.

No examples provided.

text_stats ~78

Descriptive statistics for text: rune/byte/word/line counts, a unique-rune count, a letters/digits/spaces/punctuation/other breakdown, an exact per-character frequency table, and word-length min/max/average plus the actual shortest/longest word (ties resolve to the first occurrence).

Input Output Examples

Name	Type	Req	Description
text	string	yes	–

Name	Type	Req	Description
bytes	integer	yes	–
charFrequency	object	yes	–
charTypes	object	yes	–
lines	integer	yes	–
runes	integer	yes	–
uniqueRunes	integer	yes	–
wordLengths	object	yes	–
words	integer	yes	–

No examples provided.

text_wordcount ~24

Counts whitespace-delimited words in text.

Input Output Examples

Name	Type	Req	Description
text	string	yes	–

Structured output declared, but exposes no named fields.

No examples provided.

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.

Input Output Examples

Name	Type	Req	Description
encoding	string	–	o200k_base or cl100k_base; exactly one of model/encoding
model	string	–	e.g. gpt-4o; exactly one of model/encoding
text	string	yes	–

Name	Type	Req	Description
encoding	string	–	–
tokens	integer	yes	–

No examples provided.

url_validate ~48

Checks value is a well-formed absolute URL (has both a scheme and a host) — syntax only, not a reachability check.

Input Output Examples

Name	Type	Req	Description
value	string	yes	identifier or value to check

Name	Type	Req	Description
reason	string	–	–
valid	boolean	yes	–

No examples provided.

vateu_validate ~76

Format validation only (no VIES lookup) for an EU VAT number: checks the 2-letter member-state prefix (EL for Greece, XI for Northern Ireland) against that country's digit/letter pattern. A format-valid result does not mean the number is actually registered.

Input Output Examples

Name	Type	Req	Description
value	string	yes	identifier or value to check

Name	Type	Req	Description
reason	string	–	–
valid	boolean	yes	–

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

18 Aug 20 Aug