_ registry / mcp streamable-http · checked 1h ago

profanity-api

https://profanity-api.mike-tusa.workers.dev

Registry code: 163b43648271d4f4

api record

CussCheck finds English swear words in text and returns their positions and a censored copy. It is a word-list filter (obscenity englishDataset) with leetspeak, look-alike character, repeated-letter, dotted/spaced-letter and hidden-character handling; it is not AI moderation and does not understand context. Use check_profanity with "text" (at most 10240 UTF-8 bytes). Optional "allow" and "deny" word lists (up to 50 words each). Positions are UTF-16 indices into your original text (start inclusive, end exclusive). The text is checked in memory and never stored or logged. Anonymous use: about…

endpoint
https://profanity-api.mike-tusa.workers.dev/mcp
protocol
streamable-http ·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 profanity-api live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is profanity-api free to use?
Yes — the hub reached it with no key and no payment.
What tools does profanity-api have?
1 tool: check_profanity.
Is profanity-api 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
100%

90 days 100%· all time 100%

latency
192ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 1 tools
1 never probed 0 of 1 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.

  • check_profanity unknown 1h ago

    Detect English profanity in text (word list with leetspeak, look-alike letters, repeated letters, dotted/spaced letters and hidden characters handled) and return the matched terms, their positions (UTF-16 start/end in your text) and, unless censor is false, a censored copy of the same length. Common innocent words (Scunthorpe, cockpit, Shiite, cumin) are whitelisted; it does not understand context and is English only. Text up to 10240 UTF-8 bytes; it is not stored or logged. matches is capped at 50 here (match_count is the full total). Read-only. Same engine, keys and limits as POST /v1/check.

    mcp-tool

    {
  "type": "object",
  "required": [
    "text"
  ],
  "properties": {
    "deny": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 40,
        "minLength": 1
      },
      "maxItems": 50,
      "description": "Extra words to flag on word boundaries, e.g. [\"jerk\"]."
    },
    "text": {
      "type": "string",
      "maxLength": 10240,
      "description": "The text to check, at most 10240 UTF-8 bytes."
    },
    "allow": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 40,
        "minLength": 1
      },
      "maxItems": 50,
      "description": "Words never to flag, e.g. [\"hell\", \"damn\"]. Allow wins over deny."
    },
    "censor": {
      "type": "boolean",
      "description": "Return a censored copy (default true)."
    }
  },
  "additionalProperties": false
}
    arguments 38 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 163b43648271d4f4.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/163b43648271d4f4/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/163b43648271d4f4/badge.svg)](https://brick.blue/agent/163b43648271d4f4?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
50%

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.