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

signamail

https://www.signamail.fr

Registry code: aac476775309160e

api record

SignaMail (signamail.fr, published by Futur Digital, France) centralises email signatures and gives each team member a digital business card.

Use these tools to create a professional email signature for the user, check the legal mentions required by their profession in France, test the SPF, DKIM and DMARC records of their domain, and explain how to install the signature in Gmail, Outlook, Apple Mail or Thunderbird.

endpoint
https://www.signamail.fr/mcp
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 signamail live?
Yes — it answered the hub's last check (checked 19h ago). It answered 100% of checks over the last 30 days.
Is signamail free to use?
Yes — the hub reached it with no key and no payment.
What tools does signamail have?
6 tools: get_signamail_plans, check_email_domain, generate_email_signature, get_profession_signature_rules, get_install_instructions, list_professions.
Is signamail 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
1,682ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 2 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 6 tools
1 open 5 never probed 1 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.

  • list_professions open 19h ago

    Lists the professions (France) for which SignaMail documents the mentions required in an email signature: lawyer, real estate agent, doctor, accountant, craftsman, sole trader... Use a slug with get_profession_signature_rules or generate_email_signature.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_signamail_plans unknown never probed

    SignaMail plans and prices (excluding VAT), what each includes and how to sign up. Use it when the user needs signatures for a team or a digital business card.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • check_email_domain unknown never probed

    Checks the SPF, DKIM and DMARC DNS records of an email domain and explains what to fix so that emails do not land in spam (Gmail and Yahoo sender requirements). Read-only DNS lookups.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "maxLength": 300,
          "description": "Domain or email address, e.g. mon-entreprise.fr"
        }
      }
    }
    arguments 14 lines
  • generate_email_signature unknown never probed

    Builds a professional HTML email signature (tables and inline styles, compatible with Gmail, Outlook, Apple Mail and Thunderbird) from the user's details. Returns the HTML, how to install it, and, if a profession is given, the legal mentions it requires in France.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "firstName",
        "lastName"
      ],
      "properties": {
        "city": {
          "type": "string",
          "maxLength": 80
        },
        "font": {
          "enum": [
            "Arial",
            "Helvetica",
            "Verdana",
            "Tahoma",
            "Trebuchet MS",
            "Georgia",
            "Times New Roman"
          ],
          "type": "string",
          "description": "Web-safe font"
        },
        "email": {
          "type": "string",
          "maxLength": 200
        },
        "phone": {
          "type": "string",
          "maxLength": 40,
          "description": "Landline, French format accepted (01 23 45 67 89)"
        },
        "mobile": {
          "type": "string",
          "maxLength": 40
        },
        "street": {
          "type": "string",
          "maxLength": 150
        },
        "company": {
          "type": "string",
          "maxLength": 100
        },
        "logoUrl": {
          "type": "string",
          "maxLength": 500,
          "description": "https URL of the company logo (PNG or JPEG). Ignored if not https"
        },
        "twitter": {
          "type": "string",
          "maxLength": 200
        },
        "website": {
          "type": "string",
          "maxLength": 200
        },
        "facebook": {
          "type": "string",
          "maxLength": 200
        },
        "jobTitle": {
          "type": "string",
          "maxLength": 100
        },
        "lastName": {
          "type": "string",
          "maxLength": 60,
          "minLength": 1,
          "description": "Last name"
        },
        "linkedin": {
          "type": "string",
          "maxLength": 200
        },
        "photoUrl": {
          "type": "string",
          "maxLength": 500,
          "description": "https URL of a square portrait photo. Ignored if not https"
        },
        "agendaUrl": {
          "type": "string",
          "maxLength": 300,
          "description": "Booking link (Calendly, Google Agenda...)"
        },
        "firstName": {
          "type": "string",
          "maxLength": 60,
          "minLength": 1,
          "description": "First name"
        },
        "imageSize": {
          "enum": [
            "small",
            "medium",
            "large"
          ],
          "type": "string"
        },
        "instagram": {
          "type": "string",
          "maxLength": 200
        },
        "legalText": {
          "type": "string",
          "maxLength": 600,
          "description": "Small print under the signature: legal form, SIRET, regulated mentions"
        },
        "postalCode": {
          "type": "string",
          "maxLength": 20
        },
        "profession": {
          "type": "string",
          "description": "Optional profession slug from list_professions: the answer then includes the mentions required for it"
        },
        "accentColor": {
          "type": "string",
          "pattern": "^#[0-9a-fA-F]{6}$",
          "description": "Hex color for the name and links, e.g. #0f766e"
        },
        "includeBranding": {
          "type": "boolean",
          "description": "Adds a discreet \"Signature créée avec SignaMail\" line (default true, the user may remove it)"
        }
      }
    }
    arguments 129 lines
  • get_profession_signature_rules unknown never probed

    Returns what a French professional must, should and must not put in an email signature for a given profession (mandatory mentions, recommended ones, mentions to avoid), with tips, common mistakes and official sources.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "profession"
      ],
      "properties": {
        "profession": {
          "type": "string",
          "description": "Slug from list_professions, e.g. \"avocat\""
        }
      }
    }
    arguments 13 lines
  • get_install_instructions unknown 19h ago

    Step-by-step instructions (French UI labels) to install an HTML email signature in a given mail client.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "client"
      ],
      "properties": {
        "client": {
          "enum": [
            "gmail",
            "outlook-web",
            "outlook-classic",
            "outlook-mac",
            "apple-mail",
            "iphone",
            "thunderbird"
          ],
          "type": "string"
        }
      }
    }
    arguments 21 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 aac476775309160e.

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