_ registry / mcp http-sse · checked 2h ago

apished-checksum

https://apished.com

Registry code: 5d43c1e2b06f72be

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://apished.com/mcp/v1/checksum
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is apished-checksum live?
Yes — it answered the hub's last check (checked 2h ago). It answered 91% of checks over the last 30 days.
Is apished-checksum free to use?
Yes — the hub reached it with no key and no payment.
What tools does apished-checksum have?
6 tools: luhn_validate, isbn_validate, swiftbic_validate, vateu_validate, iban_validate, ean_validate.
Is apished-checksum safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
91.1%

90 days 80.8%· all time 80.8%

latency
235ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 271 checks · signed record
  • degraded → live
  • live → degraded· HTTP 502
  • retired → live
  • down → retired· HTTP 502
  • degraded → down· HTTP 502
_ what it is for
topic
developer tools
used for
  • count tokens for a model
  • validate an iban, email or barcode
  • convert csv to json
  • compute hashes and regex matches
takes → gives
text, data → data, text
tools
2 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 6 tools
6 never probed 0 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • luhn_validate unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "value"
  ],
  "properties": {
    "value": {
      "type": "string",
      "description": "identifier or value to check"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • isbn_validate unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "value"
  ],
  "properties": {
    "value": {
      "type": "string",
      "description": "identifier or value to check"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • swiftbic_validate unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "value"
  ],
  "properties": {
    "value": {
      "type": "string",
      "description": "identifier or value to check"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • vateu_validate unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "value"
  ],
  "properties": {
    "value": {
      "type": "string",
      "description": "identifier or value to check"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • iban_validate reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "value"
  ],
  "properties": {
    "value": {
      "type": "string",
      "description": "identifier or value to check"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • ean_validate reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "value"
  ],
  "properties": {
    "value": {
      "type": "string",
      "description": "identifier or value to check"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 5d43c1e2b06f72be.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/5d43c1e2b06f72be/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/5d43c1e2b06f72be/badge.svg)](https://brick.blue/agent/5d43c1e2b06f72be?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.