_ registry / mcp streamable-http · checked 43m ago

couryo-free-tools

https://mcp.couryo.com

Registry code: 60d2b83eaaf7c6d2

api record

Free, no login: verify an email address, check SPF/DKIM/DMARC, explain SMTP errors, build SPF/DMARC.

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

endpoint
https://mcp.couryo.com/tools
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 couryo-free-tools live?
Yes — it answered the hub's last check (checked 43m ago). It answered 100% of checks over the last 30 days.
Is couryo-free-tools free to use?
Yes — the hub reached it with no key and no payment.
What tools does couryo-free-tools have?
5 tools: check_domain_dns, verify_email, generate_dmarc, explain_smtp_error, generate_spf.
Is couryo-free-tools 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
294ms

last good check

priced tools
0

of 5 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
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
1 open 4 never probed 1 of 5 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.

  • generate_spf open 43m ago

    Builds one SPF record (TXT at the domain) from the services that send for it: includes, IPv4 and IPv6, mx and a. Starts with ~all (softfail), the safe choice; use policy fail (-all) once every sender is listed. Remember the limit of 10 DNS lookups (each include costs at least one). Free, no network. / Monta o registro SPF a partir dos serviços que enviam pelo domínio.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "a": {
          "type": "boolean",
          "description": "The domain's own address may send"
        },
        "mx": {
          "type": "boolean",
          "description": "Servers in the domain's MX may send"
        },
        "ip4": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "ip6": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "policy": {
          "enum": [
            "softfail",
            "fail",
            "neutral"
          ],
          "type": "string"
        },
        "includes": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "include: hosts, e.g. [\"_spf.google.com\"]"
        }
      }
    }
    arguments 41 lines
  • check_domain_dns unknown 43m ago

    Checks the email setup of any domain: SPF (one record, ending, the 10 DNS lookup limit), DKIM on the common selectors (or dkim_selector), DMARC policy and reports, MX and mailbox provider, MTA-STS, TLS-RPT and BIMI. Answers a 0 to 100 score, a grade, the fix for each problem in plain words and records ready to copy. Free, read only. / Confere SPF, DKIM, DMARC e MX de qualquer domínio, com nota e a correção de cada problema.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "description": "e.g. \"example.com\" (a URL or an address also works)"
        },
        "dkim_selector": {
          "type": "string",
          "description": "A DKIM selector to look up besides the common ones (the s= of the DKIM-Signature header)"
        }
      }
    }
    arguments 17 lines
  • verify_email unknown never probed

    Checks one email address without sending anything: format, typo in big providers ("gmail.com.br" → "gmail.com", "hotmial.com"), disposable inbox, shared mailbox (contato@, sales@) and whether the domain receives email (MX). Verdict valid, risky or invalid, with did_you_mean. The mailbox itself is never probed. Free, read only. / Confere um endereço sem enviar nada: formato, erro de digitação, e-mail temporário, caixa compartilhada e se o domínio recebe e-mail.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "email"
      ],
      "properties": {
        "email": {
          "type": "string",
          "description": "The address to check"
        }
      }
    }
    arguments 13 lines
  • generate_dmarc unknown never probed

    Builds one DMARC record (TXT at _dmarc.<domain>). Start with policy none and a report address (rua), read the reports, then move to quarantine and reject once every legitimate sender passes SPF or DKIM aligned. Free, no network. / Monta o registro DMARC; comece com p=none e suba para quarantine e reject.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "domain",
        "policy"
      ],
      "properties": {
        "pct": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1
        },
        "rua": {
          "type": "string",
          "description": "Address for the aggregate reports"
        },
        "domain": {
          "type": "string",
          "description": "The domain, to name the record"
        },
        "policy": {
          "enum": [
            "none",
            "quarantine",
            "reject"
          ],
          "type": "string"
        },
        "subdomain_policy": {
          "enum": [
            "none",
            "quarantine",
            "reject"
          ],
          "type": "string"
        }
      }
    }
    arguments 39 lines
  • explain_smtp_error unknown 43m ago

    Explains a bounce or SMTP error text ("550 5.7.515 Access denied", "452 4.2.2 mailbox full") in plain words: hard (the address does not work), soft (temporary) or policy (a provider rule, not the address), the provider and the next step. Free, read only. / Explica uma devolução ou erro SMTP em linguagem simples, com o próximo passo.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "message"
      ],
      "properties": {
        "message": {
          "type": "string",
          "maxLength": 4000,
          "description": "The error or bounce text, as it came"
        }
      }
    }
    arguments 14 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 60d2b83eaaf7c6d2.

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

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
1
ok
1
failed
0
success rate
100%
median latency
539ms
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
—

1 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.