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

prosignature

https://prosignature.co

Registry code: da5a0255a8b3b5f4

api record

ProSignature builds email signatures for Gmail and Google Workspace teams. Every tool here works without an account and changes nothing: create_signature returns the free plan's email-safe HTML (it carries a small "Created with ProSignature" credit line) plus an edit_url that opens the generator prefilled; quote_price computes list prices from https://prosignature.co/pricing.json; get_install_steps and get_facts answer honestly, including when ProSignature is not the right choice. Installing, logos, Pro and Teams start with the human signing up at https://prosignature.co/app — never create an…

endpoint
https://prosignature.co/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 prosignature live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is prosignature free to use?
Yes — the hub reached it with no key and no payment.
What tools does prosignature have?
5 tools: create_signature, quote_price, get_install_steps, list_layouts, get_facts.
Is prosignature 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
534ms

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
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
2 open 3 never probed 2 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.

  • list_layouts open 2h ago

    The four signature layouts (id, name, what it looks like) and the six accent colours the generator offers.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_facts open 2h ago

    What ProSignature is, the free plan and its credit line, Pro and Teams prices (verified 2026-10-18), how Gmail and Google Workspace installs work per person, personal links for employees, what the product is NOT (no mail-flow enforcement, no Microsoft 365 sync, no analytics), and where the docs, OpenAPI and pricing.json are.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • create_signature unknown never probed

    Builds the email-safe HTML signature (table + inline styles, the same bytes as prosignature.co/email-signature-generator) for one person. Returns html, a plain-text version, an edit_url that opens the generator prefilled, and install steps for Gmail, Outlook and Apple Mail. The output is the free plan: four layouts, six accent colours, no logo or photo, and a small clickable "Created with ProSignature" credit line under the signature (Pro removes it). Nothing is installed or stored.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 120,
          "description": "Full name (required)"
        },
        "email": {
          "type": "string",
          "maxLength": 120,
          "description": "Email address"
        },
        "phone": {
          "type": "string",
          "maxLength": 120,
          "description": "Phone, as it should read; the tel: link keeps digits and +"
        },
        "title": {
          "type": "string",
          "maxLength": 120,
          "description": "Job title"
        },
        "colour": {
          "type": "string",
          "pattern": "^#[0-9a-fA-F]{6}$",
          "description": "Accent colour #rrggbb (default #E8604C); the page offers #E8604C, #2B6CB0, #2F855A, #6B46C1, #2B2620, #B7791F"
        },
        "layout": {
          "enum": [
            "classic",
            "stacked",
            "minimal",
            "card"
          ],
          "type": "string",
          "description": "Layout id (default classic)"
        },
        "company": {
          "type": "string",
          "maxLength": 120,
          "description": "Company or business name"
        },
        "website": {
          "type": "string",
          "maxLength": 200,
          "description": "Website: bare domain (https:// is added) or an http(s) URL"
        }
      },
      "additionalProperties": false
    }
    arguments 54 lines
  • quote_price unknown never probed

    List price for Pro (one person) or Teams (per person, 5-person minimum, no platform fee) for a number of people, billed yearly or monthly, computed from the rules in https://prosignature.co/pricing.json (verified 2026-10-18). The admin counts as one of the people. Free plan: $0, credit line. This is a quote, not a checkout: the human pays in the app after signing up.

    mcp-tool

    {
      "type": "object",
      "required": [
        "plan"
      ],
      "properties": {
        "plan": {
          "enum": [
            "pro",
            "teams"
          ],
          "type": "string",
          "description": "pro = one person; teams = a company (admin + employees)"
        },
        "people": {
          "type": "integer",
          "maximum": 10000,
          "minimum": 1,
          "description": "How many people, admin included (default 1)"
        },
        "billing": {
          "enum": [
            "yearly",
            "monthly"
          ],
          "type": "string",
          "description": "Billing period (default yearly)"
        }
      },
      "additionalProperties": false
    }
    arguments 31 lines
  • get_install_steps unknown 2h ago

    How a signature from create_signature gets into a mail client, honestly: Gmail web (paste, or the sendAs PATCH with gmail.settings.basic — new mail only), Gmail mobile, Outlook (copy-paste only, no directory sync), Apple Mail, iPhone. The free Chrome extension (auto-updates, covers replies) needs the human to sign up first.

    mcp-tool

    {
      "type": "object",
      "required": [
        "client"
      ],
      "properties": {
        "client": {
          "enum": [
            "gmail",
            "gmail_mobile",
            "outlook",
            "apple_mail",
            "iphone"
          ],
          "type": "string",
          "description": "Which mail client"
        }
      },
      "additionalProperties": false
    }
    arguments 20 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 da5a0255a8b3b5f4.

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