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

stillrelevant-fax

https://stillrelevant.uk

Registry code: 20752ad3baacb085

api record

Sends faxes to fax numbers worldwide, from £2.49 each (within the UK and to most of Europe, the US and Canada; some countries cost more, and the price is in the send_fax result), charged only on delivery. Call send_fax, then give the user the pay_url. Check progress with fax_status.

endpoint
https://stillrelevant.uk/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 stillrelevant-fax live?
Yes — it answered the hub's last check (checked 15h ago). It answered 100% of checks over the last 30 days.
Is stillrelevant-fax free to use?
Yes — the hub reached it with no key and no payment.
What tools does stillrelevant-fax have?
2 tools: fax_status, send_fax.
Is stillrelevant-fax 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
492ms

last good check

priced tools
0

of 2 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 2 tools
2 never probed 0 of 2 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.

  • fax_status unknown 15h ago

    Check whether a fax has been paid for, is sending, was delivered (charged) or failed (not charged).

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "The id returned by send_fax."
        }
      }
    }
    arguments 12 lines
  • send_fax unknown never probed

    Prepare a fax to a fax number anywhere in the world and get a payment link for the user. £2.49 per fax within the UK and to most of Europe, the US and Canada (up to 25 pages); some countries cost more and the exact price comes back in the result. Charged only if the fax is delivered. Accepts almost any document: PDF, Word, images, text, Markdown, spreadsheets, slides. Give the file as a public https URL (file_url) or base64 (file_base64 with filename). Returns pay_url (the user must open it and pay; nothing is sent before that) and status_url. Do not open pay_url yourself.

    mcp-tool

    {
      "type": "object",
      "required": [
        "to"
      ],
      "properties": {
        "to": {
          "type": "string",
          "description": "Fax number. Include the country code (\"+44 20 7946 0000\") or give country. UK numbers like \"020 7946 0000\" work without it."
        },
        "cover": {
          "type": "object",
          "properties": {
            "to": {
              "type": "string"
            },
            "from": {
              "type": "string"
            },
            "note": {
              "type": "string"
            }
          },
          "description": "Optional cover page."
        },
        "country": {
          "type": "string",
          "description": "Two-letter country code of the fax number, if it has no + code. Default GB."
        },
        "file_url": {
          "type": "string",
          "description": "Public https URL of the document."
        },
        "filename": {
          "type": "string",
          "description": "File name with extension, e.g. \"letter.docx\". Needed with file_base64."
        },
        "file_base64": {
          "type": "string",
          "description": "The document as base64, if there is no URL."
        }
      }
    }
    arguments 43 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 20752ad3baacb085.

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

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.