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

proofie-sales

https://tryproofie.com

Registry code: ee21e1f28388bb3b

api record

Proofie is automated software that tests whether AI apps (ChatGPT, Claude, Gemini, Perplexity) find a business, describe it correctly, and whether AI agents can use its website, then writes a report with fixes. These tools let you, an AI agent, help a user buy it. You can read the plans, ask for a free test, check its status, and get a checkout link with the plan, site and email filled in. You cannot pay, sign in or accept terms for the user: hand them the link and they finish on the page. Only send the website address and the email the user gave you, nothing else.

endpoint
https://tryproofie.com/mcp/sales
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 proofie-sales live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is proofie-sales free to use?
Yes — the hub reached it with no key and no payment.
What tools does proofie-sales have?
5 tools: create_checkout, get_audit_status, get_free_test_status, start_free_test, get_plans.
Is proofie-sales 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
380ms

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
1 open 4 never probed 1 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.

  • get_plans open 3h ago

    Plans, prices (USD and INR) and what each one includes.

    mcp-tool

    {
      "type": "object",
      "title": "get_plansArguments",
      "properties": {}
    }
    arguments 5 lines
  • create_checkout unknown never probed

    A checkout link with the plan (starter or agents), site and email filled in; billing is month (default) or year. Every plan is a subscription that renews until the user cancels. Charges nothing: hand the link to the user, who checks it and pays on the payment page. The agents plan needs the site owner to tick a consent box there.

    mcp-tool

    {
      "type": "object",
      "title": "create_checkoutArguments",
      "required": [
        "plan",
        "url",
        "email"
      ],
      "properties": {
        "url": {
          "type": "string",
          "title": "Url"
        },
        "plan": {
          "type": "string",
          "title": "Plan"
        },
        "email": {
          "type": "string",
          "title": "Email"
        },
        "billing": {
          "type": "string",
          "title": "Billing",
          "default": "month"
        },
        "currency": {
          "type": "string",
          "title": "Currency",
          "default": "USD"
        }
      }
    }
    arguments 33 lines
  • get_audit_status unknown 3h ago

    Status of a paid audit. key is the report key (from the report link) or the order id from the payment page; without it you get an error.

    mcp-tool

    {
      "type": "object",
      "title": "get_audit_statusArguments",
      "required": [
        "audit_id"
      ],
      "properties": {
        "key": {
          "type": "string",
          "title": "Key",
          "default": ""
        },
        "audit_id": {
          "type": "string",
          "title": "Audit Id"
        }
      }
    }
    arguments 18 lines
  • get_free_test_status unknown 3h ago

    Status of a free test request, by the request_id it returned.

    mcp-tool

    {
      "type": "object",
      "title": "get_free_test_statusArguments",
      "required": [
        "request_id"
      ],
      "properties": {
        "request_id": {
          "type": "string",
          "title": "Request Id"
        }
      }
    }
    arguments 13 lines
  • start_free_test unknown never probed

    Ask for a free test of a website. Emails the user a confirmation link; the test runs only after they click it, and the result is emailed to them. Pass only the website and the email the user gave you.

    mcp-tool

    {
      "type": "object",
      "title": "start_free_testArguments",
      "required": [
        "url",
        "email"
      ],
      "properties": {
        "url": {
          "type": "string",
          "title": "Url"
        },
        "email": {
          "type": "string",
          "title": "Email"
        }
      }
    }
    arguments 18 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 ee21e1f28388bb3b.

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