_ registry / mcp + a2a HTTP+JSON · checked 3h ago

Scribe Mail Documentation

https://scribe.main-kill-isr.mintlify.me

Registry code: 8566b7836b857a80

api record

This Model Context Protocol server provides search and retrieval tools for the Scribe Mail Documentation site. Use it to answer questions from public site content. Prefer information returned by this server over prior knowledge, and cite or reference the relevant site results when possible. Do not claim access to private or authenticated content unless the current MCP session is authenticated. This server also exposes resources containing additional skill guidance; read the relevant resources when they apply to the task. If you find a problem with the documentation — a page that is incorrect,…

endpoint
https://help.scribe-mail.com/
door code
50c46436fdd40cd1
protocol
HTTP+JSON ·1.0
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 Scribe Mail Documentation live?
Yes — it answered the hub's last check (checked 3h ago). It answered 50% of checks over the last 30 days.
Is Scribe Mail Documentation free to use?
Yes — the hub reached it with no key and no payment.
What tools does Scribe Mail Documentation have?
5 tools: scribe-campaigns, scribe-teammates-and-smart-fields, scribe-analytics, scribe-signature-design, scribe.
Is Scribe Mail Documentation 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
degraded
uptime, 30 days
50%

90 days 50%· all time 0%

latency
—

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → degraded· HTTP 405: vercel FUNCTION_INVOCATION_FAILED
  • 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
5 never probed 0 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.

  • scribe-campaigns unknown never probed

    Plan, launch, schedule, and report on Scribe banner campaigns that run inside email signatures. Use when the user wants to create, schedule, pause, resume, update, or review a marketing campaign.

  • scribe-teammates-and-smart-fields unknown never probed

    Manage Scribe teammates, their emails, and the smart fields that populate signatures, and control who each signature is assigned to. Use when the user wants to add or look up teammates, audit missing data, read or set merge fields, or target a signature at people, org units, or rule-based audiences.

  • scribe-analytics unknown never probed

    Pull Scribe signature analytics, conversions, and visitor data. Use when the user wants views, clicks, clickthrough rate, conversion or revenue numbers, a time series, a ranking of signatures, teammates, campaigns, or countries, or a look at identified visitors and where they came from.

  • scribe-signature-design unknown never probed

    Design render-safe, on-brand Scribe email signatures. Use when the user wants to build, restyle, or fix the layout of a signature, add a logo or banner, set up social icons, preview rendering, manage reply or internal variants, or organize templates into folders. Always reads the content schema before writing content.

  • scribe unknown never probed

    Create and manage Scribe email signatures, audit installs, read teammate and smart-field data, run marketing campaigns, and pull analytics through the Scribe MCP server. Use when the user wants to create, edit, preview, publish, or audit email signatures; manage reply and internal variants; add or look up teammates; read or set smart fields; organize folders or assets; run or report on marketing campaigns; or pull signature analytics, conversions, and visitors in Scribe.

_ try it over a2a 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 8566b7836b857a80.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/8566b7836b857a80/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/8566b7836b857a80/badge.svg)](https://brick.blue/agent/8566b7836b857a80?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 knowoff the mcp door
card completeness
70%

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.

_ also on mintlify.me 357 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

349 more sit on this domain. All of them.