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

measure-events

https://lets.measure.events

Registry code: fdab3b14c51ea50e

api record

Measure: privacy-first web analytics for people and AI agents. No cookies, no IPs stored. Use list_sites to find a site_key, then get_site_summary, get_site_analytics, get_agents, get_breakdown, get_insights or get_agent_report. track_event and log_checkin record activity. Without an account, signup creates one (14-day trial; the billing contact gets a claim link). Support: [email protected].

endpoint
https://lets.measure.events/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 measure-events live?
Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
Is measure-events free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does measure-events have?
13 tools: get_breakdown, get_live, track_event, log_checkin, signup, get_llms_txt, create_site, get_site_analytics, ….
Is measure-events 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.2%

90 days 99.5%· all time 99.5%

latency
101ms

last good check

priced tools
0

of 13 tools

_ answered our checks, 90 days 400 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
data & analytics analytics & metrics
used for
  • get website analytics
  • get site traffic insights
  • track a pageview event
  • create a site for tracking
  • log an agent check-in
takes → gives
text → data
tools
3 reads3 changes data
_ 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 13 tools
13 auth-required 13 of 13 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_breakdown auth-required 17h ago

    Top values of one dimension: path, referrer, source, channel, country, device, browser, os, utm_source, utm_medium, utm_campaign or agent.

    mcp-tool

    {
  "type": "object",
  "required": [
    "site_key",
    "dim"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "End date, YYYY-MM-DD (UTC, inclusive)."
    },
    "dim": {
      "enum": [
        "path",
        "referrer",
        "source",
        "channel",
        "country",
        "device",
        "browser",
        "os",
        "utm_source",
        "utm_medium",
        "utm_campaign",
        "agent"
      ],
      "type": "string"
    },
    "from": {
      "type": "string",
      "description": "Start date, YYYY-MM-DD (UTC, inclusive)."
    },
    "limit": {
      "type": "integer",
      "maximum": 1000,
      "minimum": 1
    },
    "period": {
      "enum": [
        "24h",
        "7d",
        "30d",
        "90d",
        "year",
        "day",
        "week",
        "month"
      ],
      "type": "string",
      "description": "Time period. Ignored when from and to are given."
    },
    "traffic": {
      "enum": [
        "all",
        "humans",
        "agents",
        "bots"
      ],
      "type": "string",
      "description": "Which traffic to count (default all)."
    },
    "site_key": {
      "type": "string",
      "description": "The site's tracking ID (site_key), from list_sites."
    }
  }
}
    arguments 67 lines
  • get_live auth-required 17h ago

    Visitors on the site now and the latest requests.

    mcp-tool

    {
  "type": "object",
  "required": [
    "site_key"
  ],
  "properties": {
    "site_key": {
      "type": "string",
      "description": "The site's tracking ID (site_key), from list_sites."
    }
  }
}
    arguments 12 lines
  • track_event changes data auth-required never probed

    Record a pageview: an agent's own visit, or a request your server forwards. Pass user_agent to classify a forwarded request; otherwise it counts as an AI agent visit under `agent` (default: the API key's name).

    mcp-tool

    {
  "type": "object",
  "required": [
    "site_key",
    "path"
  ],
  "properties": {
    "path": {
      "type": "string",
      "description": "Page path, e.g. /about."
    },
    "agent": {
      "type": "string",
      "description": "Agent name for attribution."
    },
    "referrer": {
      "type": "string",
      "description": "Referring URL (only the host is kept)."
    },
    "site_key": {
      "type": "string",
      "description": "The site's tracking ID (site_key), from list_sites."
    },
    "user_agent": {
      "type": "string",
      "description": "User agent of a forwarded request (classified, never stored)."
    },
    "utm_medium": {
      "type": "string"
    },
    "utm_source": {
      "type": "string"
    },
    "utm_campaign": {
      "type": "string"
    }
  }
}
    arguments 38 lines
  • log_checkin changes data auth-required never probed

    Record something you did to the site (published a post, deployed, changed a page) so it shows beside the traffic it caused.

    mcp-tool

    {
  "type": "object",
  "required": [
    "site_key",
    "action"
  ],
  "properties": {
    "note": {
      "type": "string"
    },
    "agent": {
      "type": "string",
      "description": "Agent name (default: the API key's name)."
    },
    "action": {
      "type": "string",
      "description": "What you did, e.g. 'published /blog/launch'."
    },
    "site_key": {
      "type": "string",
      "description": "The site's tracking ID (site_key), from list_sites."
    },
    "timestamp": {
      "type": "string",
      "description": "ISO 8601; default now."
    }
  }
}
    arguments 28 lines
  • signup auth-required never probed

    Create a Measure account without a human. Starts a 14-day trial and returns an API key and tracking script; the billing contact is emailed a link to claim the account and add a card. No API key needed.

    mcp-tool

    {
  "type": "object",
  "required": [
    "billing_contact_email",
    "site",
    "agent"
  ],
  "properties": {
    "site": {
      "type": "object",
      "required": [
        "domain"
      ],
      "properties": {
        "name": {
          "type": "string"
        },
        "domain": {
          "type": "string"
        }
      }
    },
    "agent": {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Your display name, e.g. Claude."
        },
        "identifier": {
          "type": "string",
          "description": "Stable identifier, e.g. anthropic/claude."
        }
      }
    },
    "billing_contact_name": {
      "type": "string"
    },
    "billing_contact_email": {
      "type": "string",
      "description": "Email of the person who will pay. Receives the claim link."
    }
  }
}
    arguments 47 lines
  • get_llms_txt auth-required 17h ago

    The last 30 days as a short Markdown document, for context windows.

    mcp-tool

    {
  "type": "object",
  "required": [
    "site_key"
  ],
  "properties": {
    "site_key": {
      "type": "string",
      "description": "The site's tracking ID (site_key), from list_sites."
    }
  }
}
    arguments 12 lines
  • create_site changes data auth-required never probed

    Add a site. Returns its site_key and tracking script.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Display name (defaults to the domain)."
    },
    "domain": {
      "type": "string",
      "description": "The site's domain, e.g. example.com."
    }
  }
}
    arguments 16 lines
  • get_site_analytics reads auth-required 6h ago

    Pageviews, visitors (humans), AI agent and bot requests, top pages and referrers for a period.

    mcp-tool

    {
  "type": "object",
  "required": [
    "site_key"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "End date, YYYY-MM-DD (UTC, inclusive)."
    },
    "from": {
      "type": "string",
      "description": "Start date, YYYY-MM-DD (UTC, inclusive)."
    },
    "period": {
      "enum": [
        "24h",
        "7d",
        "30d",
        "90d",
        "year",
        "day",
        "week",
        "month"
      ],
      "type": "string",
      "description": "Time period. Ignored when from and to are given."
    },
    "site_key": {
      "type": "string",
      "description": "The site's tracking ID (site_key), from list_sites."
    }
  }
}
    arguments 34 lines
  • list_sites auth-required 25h ago

    List your sites with their site_key, tracking script and last-7-day pageviews.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • get_insights reads auth-required 6h ago

    Anomalies and trends: page spikes, new referrers, new AI agents, traffic drops, weekly trend.

    mcp-tool

    {
  "type": "object",
  "required": [
    "site_key"
  ],
  "properties": {
    "site_key": {
      "type": "string",
      "description": "The site's tracking ID (site_key), from list_sites."
    }
  }
}
    arguments 12 lines
  • get_agents auth-required 25h ago

    Every AI agent that fetched the site: operator, purpose (assistant, training, search), requests, top page.

    mcp-tool

    {
  "type": "object",
  "required": [
    "site_key"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "End date, YYYY-MM-DD (UTC, inclusive)."
    },
    "from": {
      "type": "string",
      "description": "Start date, YYYY-MM-DD (UTC, inclusive)."
    },
    "period": {
      "enum": [
        "24h",
        "7d",
        "30d",
        "90d",
        "year",
        "day",
        "week",
        "month"
      ],
      "type": "string",
      "description": "Time period. Ignored when from and to are given."
    },
    "site_key": {
      "type": "string",
      "description": "The site's tracking ID (site_key), from list_sites."
    }
  }
}
    arguments 34 lines
  • get_site_summary reads auth-required 6h ago

    A plain-language summary of the last 7 days with week-over-week change and highlights.

    mcp-tool

    {
  "type": "object",
  "required": [
    "site_key"
  ],
  "properties": {
    "site_key": {
      "type": "string",
      "description": "The site's tracking ID (site_key), from list_sites."
    }
  }
}
    arguments 12 lines
  • get_agent_report auth-required 25h ago

    Everything in one call: 7- and 30-day traffic, daily series, pages, referrers, channels, agents, insights, check-ins and recommended actions.

    mcp-tool

    {
  "type": "object",
  "required": [
    "site_key"
  ],
  "properties": {
    "site_key": {
      "type": "string",
      "description": "The site's tracking ID (site_key), from list_sites."
    }
  }
}
    arguments 12 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 fdab3b14c51ea50e.

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

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.