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

digitaltrust

https://digitaltrust.pt

Registry code: db016a4c83b43f9a

api record

Tools for checking SSL/TLS servers, decoding certificates and CSRs, searching Certificate Transparency, checking and generating CAA records, checking email security (SPF, DKIM, DMARC, BIMI, MTA-STS) and listing SSL certificate prices from DigitalTrust. Results are factual data; messages may be in Portuguese. Never send private keys. To buy, give the user the order_url; orders are confirmed by a person.

endpoint
https://digitaltrust.pt/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 digitaltrust live?
Yes — it answered the hub's last check (checked 9h ago). It answered 100% of checks over the last 30 days.
Is digitaltrust free to use?
Yes — the hub reached it with no key and no payment.
What tools does digitaltrust have?
10 tools: check_caa, match_public_keys, check_ssl, decode_certificate, decode_csr, search_certificate_transparency, generate_caa, check_email_security, ….
Is digitaltrust 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
210ms

last good check

priced tools
0

of 10 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

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

  • list_ssl_products open 9h ago

    Lists the SSL/TLS certificates sold by DigitalTrust (DV, OV, EV, QWAC, QWAC PSD2), with yearly prices in euros without VAT, coverage options, issuance time and the order page for each.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • check_caa unknown 9h ago

    Reads the CAA records that apply to a domain (walking up to the parent domain) and says which certificate authorities (Actalis, Certum, DigiCert, GlobalSign, HARICA, Let's Encrypt, Sectigo) may issue normal and wildcard certificates.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "description": "Domain, e.g. example.pt"
        }
      }
    }
    arguments 12 lines
  • match_public_keys unknown 9h ago

    Compares the SHA-256 fingerprints of the public keys in a certificate and a CSR. Private keys are never accepted by this API: compare them locally with "openssl pkey -in key.pem -pubout | openssl sha256".

    mcp-tool

    {
      "type": "object",
      "properties": {
        "csr": {
          "type": "string",
          "description": "PEM CSR"
        },
        "certificate": {
          "type": "string",
          "description": "PEM certificate"
        }
      }
    }
    arguments 13 lines
  • check_ssl unknown never probed

    Connects to a public host and returns the certificate, chain, trust status, hostname match, days to expiry, negotiated protocol and supported TLS versions (1.0 to 1.3).

    mcp-tool

    {
      "type": "object",
      "required": [
        "host"
      ],
      "properties": {
        "host": {
          "type": "string",
          "description": "Hostname, e.g. example.pt or mail.example.pt"
        },
        "port": {
          "enum": [
            443,
            8443,
            465,
            993,
            995,
            636,
            853,
            4443,
            5061,
            6697
          ],
          "type": "integer",
          "default": 443,
          "description": "TLS port"
        }
      }
    }
    arguments 29 lines
  • decode_certificate unknown never probed

    Decodes one or more PEM certificates (a full chain is accepted) and returns subject, SANs, issuer, validity, validation type (DV, OV, EV, QWAC), key, fingerprints and OCSP URL.

    mcp-tool

    {
      "type": "object",
      "required": [
        "certificate"
      ],
      "properties": {
        "certificate": {
          "type": "string",
          "description": "PEM certificate(s), starting with -----BEGIN CERTIFICATE-----"
        }
      }
    }
    arguments 12 lines
  • decode_csr unknown never probed

    Decodes a PEM CSR and returns subject, SANs, key type and size, signature algorithm, signature validity, public key fingerprint and warnings that would make a CA reject it.

    mcp-tool

    {
      "type": "object",
      "required": [
        "csr"
      ],
      "properties": {
        "csr": {
          "type": "string",
          "description": "PEM CSR, starting with -----BEGIN CERTIFICATE REQUEST-----"
        }
      }
    }
    arguments 12 lines
  • search_certificate_transparency unknown never probed

    Searches public Certificate Transparency logs (Cert Spotter, with crt.sh as fallback) and returns the certificates still valid for a domain and, optionally, its subdomains: names, issuer, validity, days left and revocation.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "description": "Domain, e.g. example.pt"
        },
        "include_subdomains": {
          "type": "boolean",
          "default": true,
          "description": "Include subdomains"
        }
      }
    }
    arguments 17 lines
  • generate_caa unknown never probed

    Builds CAA records, in structured form and as zone-file lines, that authorise the chosen certificate authorities to issue for a domain.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain",
        "cas"
      ],
      "properties": {
        "cas": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Certificate authorities to authorise: actalis, certum, digicert, globalsign, harica, letsencrypt, sectigo, or a CAA identifier such as letsencrypt.org"
        },
        "iodef": {
          "type": "string",
          "description": "Email address for CA incident reports"
        },
        "domain": {
          "type": "string",
          "description": "Domain, e.g. example.pt"
        },
        "wildcard": {
          "enum": [
            "same",
            "none"
          ],
          "type": "string",
          "default": "same",
          "description": "\"same\" lets the same CAs issue wildcards; \"none\" forbids wildcard certificates"
        }
      }
    }
    arguments 33 lines
  • check_email_security unknown never probed

    Returns MX, SPF, DKIM (when a selector is given), DMARC with its parsed tags, BIMI, MTA-STS (record and published policy) and TLS-RPT for a domain.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "description": "Domain, e.g. example.pt"
        },
        "dkim_selector": {
          "type": "string",
          "description": "DKIM selector to test, e.g. default, google, selector1"
        }
      }
    }
    arguments 16 lines
  • build_order_url unknown never probed

    Returns the price and a link to the DigitalTrust order page with the certificate already chosen. Orders are confirmed by a person on that page; this API does not place orders.

    mcp-tool

    {
      "type": "object",
      "required": [
        "type"
      ],
      "properties": {
        "type": {
          "enum": [
            "dv",
            "ov",
            "ev",
            "qwac",
            "psd2"
          ],
          "type": "string",
          "description": "Certificate type"
        },
        "years": {
          "enum": [
            1,
            2,
            3,
            4,
            5
          ],
          "type": "integer",
          "default": 1,
          "description": "Subscription length in years, paid upfront (discounts: 2y 15%, 3y 17%, 4y 20%, 5y 25%)"
        },
        "coverage": {
          "enum": [
            "unico",
            "multi",
            "wildcard"
          ],
          "type": "string",
          "default": "unico",
          "description": "Coverage"
        }
      }
    }
    arguments 41 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 db016a4c83b43f9a.

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