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

smartflow-verify-mcp

https://verify.smartflowproai.com

Registry code: 4777b6696e124360

api record
endpoint
https://verify.smartflowproai.com/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 smartflow-verify-mcp live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is smartflow-verify-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does smartflow-verify-mcp have?
3 tools: order_endpoint_audit, get_audit_order_status, get_network_decomposition.
Is smartflow-verify-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
100%

90 days 100%· all time 100%

latency
182ms

last good check

priced tools
0

of 3 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 3 tools
1 open 2 never probed 1 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_network_decomposition open 1h ago

    FREE, read-only. Integrity-sealed decomposition of x402 payment growth on Base from SmartFlow Observatory's independent ledger of USDC micro-transfers: how much of the headline volume is wash / self-dealing / clone-fleet activity vs bundler plumbing vs the organic clean core. Returns the full dataset plus `seal_verified` (this client recomputes the SHA-256 seal locally, recipe included in the response) and `data_age_hours`. Use this BEFORE trusting any headline x402 volume figure. Caveats: data refreshes roughly daily (check `data_age_hours`); figures reflect the observatory's ingest time, so the most recent ~1h of activity may be under-represented.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • order_endpoint_audit unknown never probed

    Creates a PAYABLE ORDER for a $199 signed, human-reviewed audit of an x402 endpoint or receiving wallet (wash-share, payer concentration, demand dispersion, attribution), delivered by email within 24h of payment. COST: calling this tool is free and moves NO funds. It returns an x402 `exact`-scheme payment challenge (HTTP 402) with a per-order UNIQUE USDC amount on Base, plus plain-language payment instructions and the order id. The purchase only happens if you (or your operator) then pay the EXACT quoted amount to the quoted address; do not round it. This is a real $199 purchase; confirm with your operator if your spend policy requires it. Unpaid orders are harmless and expire on their own within 24h. After paying, poll get_audit_order_status with the order id; if a payment submission times out, poll status BEFORE paying again. Never pay the same order twice.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "target",
        "email"
      ],
      "properties": {
        "email": {
          "type": "string",
          "format": "email",
          "pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
          "maxLength": 254,
          "description": "Email address to deliver the signed audit report to."
        },
        "target": {
          "type": "string",
          "maxLength": 500,
          "minLength": 3,
          "description": "What to audit: an x402 endpoint URL (https://...) or a receiving wallet address (0x...)."
        }
      }
    }
    arguments 23 lines
  • get_audit_order_status unknown never probed

    FREE, read-only. Poll the status of an audit order created with order_endpoint_audit. Status `pending_payment` means the exact-amount USDC payment has not been detected yet; `paid: true` confirms your x402 payment was matched; a delivered state means the signed report was emailed. Caveats: payment detection reads Base USDC transfer logs and can lag a few minutes behind the chain. If you just paid the exact amount, wait 2-5 minutes and poll again before assuming a problem. Unpaid orders expire within 24h.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "order_id"
      ],
      "properties": {
        "order_id": {
          "type": "string",
          "pattern": "^aud_[0-9a-f]{16}$",
          "description": "The order id returned by order_endpoint_audit, e.g. aud_2e4270db0cc840c3."
        }
      }
    }
    arguments 14 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 4777b6696e124360.

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

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.