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

spillmark

https://spillmark.com

Registry code: c3dbc3e078ee450e

api record

Spillmark measures the sales Meta (Facebook and Instagram) ads cause on Amazon and Shopify with geo holdout tests: ads are paused in a group of US states and their sales are compared with the rest. Every measured number comes with a 95% range. Quote the range with the estimate, and say 'too uncertain to call' when the range spans zero or break-even. Don't round a range away. Lift is caused sales, not the sales an ad platform credits. Don't present it as attribution, and don't add up or compare different brands' numbers. Predictions are locked (hashed) before their result is known and scored…

endpoint
https://spillmark.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 spillmark live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is spillmark free to use?
Yes — the hub reached it with no key and no payment.
What tools does spillmark have?
3 tools: run_calculator, how_lift_is_calculated, list_calculators.
Is spillmark 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
286ms

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
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.

  • how_lift_is_calculated open 2h ago

    Spillmark's method in brief: how a geo holdout test measures the sales Meta ads cause on Amazon, with links to the full method and a sample report on made-up numbers.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • list_calculators open 2h ago

    Spillmark's free Amazon and Meta ads calculators (holdout test size, incremental ROAS, break-even ROAS, ACoS, TACoS, Amazon fees and profit, LTV and CAC), with each one's inputs and example values. Use run_calculator to run one.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "q": {
          "type": "string",
          "maxLength": 60,
          "description": "Filter by words in the name or summary, e.g. 'holdout' or 'fees'"
        }
      }
    }
    arguments 11 lines
  • run_calculator unknown never probed

    Runs one calculator from list_calculators on your numbers and returns the headline result, the supporting figures, a one-sentence reading, and a link that opens the calculator with the same inputs. Missing inputs use the calculator's example values. Enter percents as points (15 means 15%), choices as the option index.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1,
          "description": "Calculator slug from list_calculators, e.g. holdout-test-calculator"
        },
        "inputs": {
          "type": "object",
          "description": "Input values by key",
          "propertyNames": {
            "type": "string"
          },
          "additionalProperties": {
            "anyOf": [
              {
                "type": "number"
              },
              {
                "type": "string",
                "maxLength": 32
              },
              {
                "type": "null"
              }
            ]
          }
        },
        "currency": {
          "enum": [
            "USD",
            "EUR",
            "GBP",
            "CAD",
            "AUD"
          ],
          "type": "string",
          "description": "Currency for money results. Default USD"
        }
      }
    }
    arguments 47 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 c3dbc3e078ee450e.

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