ldm-delivery
https://api.live-direct-marketing.online
Registry code: 601aea7ab727c65f
Registers a new workspace on LDM.delivery, a direct-marketing delivery service, after showing its user agreement, and checks the API's health.
- endpoint
- https://api.live-direct-marketing.online/mcp
- door code
- d137f4e1fdf2a534
- 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 ldm-delivery live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 98% of checks over the last 30 days.
- Is ldm-delivery free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does ldm-delivery have?
- 3 tools: ldm_terms, ldm_register, ldm_health.
- Is ldm-delivery 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.
90 days 98.2%· all time 98.6%
last good check
of 3 tools
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- register a new direct-marketing workspace
- get the user agreement
- check api health
- takes → gives
- data → text, data
- tools
- 2 reads1 changes data
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.
through this hub
successful
what callers paid
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.
ldm_health reads open 5h ago
Check LDM.delivery API health. No auth required.
{ "type": "object", "properties": {} }arguments 4 linesldm_terms reads unknown never probed
Fetch the LDM user agreement text (plain). Show it to the user before calling ldm_register. No auth required.
{ "type": "object", "properties": {} }arguments 4 linesldm_register changes data unknown never probed
Bootstrap a new LDM workspace for the user (no API key needed). Requires the user to have read the agreement (ldm_terms) and accept it. Creates a PENDING account, emails a confirmation link to `email`, and returns an ldm_* API key with read + safe-draft scopes (sending email needs the owner to expand scopes after activation). Reconnect your MCP client with the returned key. Rate-limited per IP. Pass `website` (company site on the email domain) to get automatic activation; without it the signup needs a questionnaire and an admin approval.
{ "type": "object", "required": [ "email", "termsAccepted" ], "properties": { "org": { "type": "string", "description": "Optional: company / organisation name." }, "email": { "type": "string", "description": "The user's email — the confirmation link is sent here." }, "website": { "type": "string", "description": "Optional but decisive: the company website on the SAME domain as `email` (e.g. https://acme.com for [email protected]). With it, a corporate signup activates automatically once the email is confirmed. Without it — or with a freemail address — the signup goes to a short questionnaire and waits for an admin." }, "use_case": { "type": "string", "description": "Optional: what the user wants to do (one line)." }, "firstName": { "type": "string", "description": "Optional: first name." }, "termsAccepted": { "type": "boolean", "description": "Must be true; the user accepted the agreement from ldm_terms." } } }arguments 33 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id601aea7ab727c65f.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/601aea7ab727c65f/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/601aea7ab727c65f?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.
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.
- check.live-direct-marketing.online inbox-check-guest
- developers.live-direct-marketing.online LDM.delivery
- live-direct-marketing.online LDM.delivery