_ registry / mcp + a2a streamable-http · checked 1h ago

unlocksaas-mcp

https://unlocksaas.com

Registry code: d3aaf39aee5121e1

api record

Playbook engine: non-dev founders land first paying customer in 60 days or refund

from a public catalogue that lists it, not from the operator

endpoint
https://unlocksaas.com/api/mcp
door code
1c712e7e31c406fc
protocol
streamable-http ·2024-11-05
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 unlocksaas-mcp live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is unlocksaas-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does unlocksaas-mcp have?
3 tools: project_revenue, get_ltv, get_churn_cost.
Is unlocksaas-mcp 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
99.6%

90 days 99.2%· all time 99.1%

latency
298ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 904 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
productivity & business
used for
  • calculate churn cost
  • calculate customer lifetime value
  • project saas revenue
takes → gives
data → data
tools
3 reads
_ 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 3 tools
2 open 1 never probed 2 of 3 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.

  • get_ltv reads open 1h ago

    Calculate customer lifetime value (LTV) for a SaaS business from ARPU, gross margin, and monthly churn. Uses the canonical David Skok formula.

    mcp-tool

    {
  "type": "object",
  "required": [
    "arpu",
    "gross_margin",
    "monthly_churn"
  ],
  "properties": {
    "arpu": {
      "type": "number",
      "description": "Average revenue per user per month (USD)."
    },
    "gross_margin": {
      "type": "number",
      "description": "Gross margin as a decimal (0.85 = 85%)."
    },
    "monthly_churn": {
      "type": "number",
      "description": "Monthly churn rate as a decimal (0.05 = 5%)."
    }
  }
}
    arguments 22 lines
  • get_churn_cost reads open 1h ago

    Calculate the monthly revenue cost of SaaS churn from MRR, churn rate, and customer count. Returns the dollar value leaking out each month.

    mcp-tool

    {
  "type": "object",
  "required": [
    "mrr",
    "churn_rate"
  ],
  "properties": {
    "mrr": {
      "type": "number",
      "description": "Monthly recurring revenue (USD)."
    },
    "customers": {
      "type": "number",
      "description": "Active customer count (optional, for per-customer view)."
    },
    "churn_rate": {
      "type": "number",
      "description": "Monthly churn rate as a decimal (0.05 = 5%)."
    }
  }
}
    arguments 21 lines
  • project_revenue reads unknown never probed

    Project SaaS revenue 12 months forward from current MRR and a monthly growth assumption. Returns month-by-month MRR.

    mcp-tool

    {
  "type": "object",
  "required": [
    "current_mrr",
    "monthly_growth"
  ],
  "properties": {
    "months": {
      "type": "number",
      "description": "Projection horizon in months (default 12)."
    },
    "current_mrr": {
      "type": "number",
      "description": "Starting monthly recurring revenue (USD)."
    },
    "monthly_growth": {
      "type": "number",
      "description": "Net monthly growth rate as a decimal (0.08 = 8%/month)."
    }
  }
}
    arguments 21 lines
_ try it over mcp 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 d3aaf39aee5121e1.

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