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

motif

https://api.motiftrace.com

Registry code: 897929cc4fd4bf8f

api record

Motif analytics for the authenticated account. Read-only. website_id takes the site's uuid or its domain (example.com), and can be left out when the account has one website; list_websites lists them. Date tools take period (7d, 28d, 30d, 90d, 365d, this_month, last_month and others) instead of from/to; prefer it over computing dates. Start with analytics_snapshot for visitors, signups, revenue by first-touch channel, and the recommendation. tracking_status answers whether tracking and signups still arrive and lists open alerts. insights is the weekly brief. journeys then journey_detail show…

endpoint
https://api.motiftrace.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 motif live?
Yes — it answered the hub's last check (checked 9h ago). It answered 100% of checks over the last 30 days.
Is motif 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 motif have?
14 tools: insights, money_leaks, website_readiness, list_websites, ai_crawlers, analytics_snapshot, answer_checks, impact_receipts, ….
Is motif 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
364ms

last good check

priced tools
0

of 14 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 14 tools
14 auth-required 14 of 14 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.

  • insights auth-required never probed

    Weekly briefs for one website, newest first: title, body, the one action, and the evidence it cites. On the free plan only the newest brief has a body; older ones are locked=true titles.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "description": "newest briefs to return, 1-12; default 4"
        },
        "website_id": {
          "type": "string",
          "description": "website id (uuid) or the site domain (example.com); omit when the account has one website"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • money_leaks auth-required never probed

    Revenue leaks for one website ranked by money at risk over the last 28 finalized Search Console days: weak snippets and positions against the CTR curve, keyword cannibalisation, checkouts started but not paid, and 404s getting search clicks. Each leak is lost visits x revenue per visit, with its basis (estimate, or upper_bound when it assumes every lost visit would have paid), confidence and one fix. Amounts are minor units of currency (cents for usd, whole yen for jpy).

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "description": "leaks to return, 1-50; default 20"
        },
        "currency": {
          "type": "string",
          "description": "lowercase ISO 4217 code; default the website's main currency"
        },
        "website_id": {
          "type": "string",
          "description": "website id (uuid) or the site domain (example.com); omit when the account has one website"
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • website_readiness auth-required never probed

    Setup readiness for one website: a 0-100 score and SEO, AI, and measurement checks, each with one fix. Not a visibility score. Last 28 UTC days.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "website_id": {
          "type": "string",
          "description": "website id (uuid) or the site domain (example.com); omit when the account has one website"
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • list_websites auth-required never probed

    List websites on the authenticated Motif account.

    mcp-tool

    {
      "type": "object",
      "additionalProperties": false
    }
    arguments 4 lines
  • ai_crawlers auth-required 9h ago

    Daily AI crawler requests (GPTBot, ClaudeBot, PerplexityBot and others, by self-reported User-Agent) seen by Motif's tracker and collector for one website. UTC days; default the last 28. Not a count of people or prompts.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "to": {
          "type": "string",
          "description": "inclusive UTC end YYYY-MM-DD; default today (UTC)"
        },
        "from": {
          "type": "string",
          "description": "inclusive UTC start YYYY-MM-DD; default last 28 days"
        },
        "period": {
          "type": "string",
          "description": "named window in UTC days instead of from/to: today, yesterday, 7d, 28d, 30d, 90d, 365d (each ends today), this_month, or last_month"
        },
        "website_id": {
          "type": "string",
          "description": "website id (uuid) or the site domain (example.com); omit when the account has one website"
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • analytics_snapshot auth-required 9h ago

    Analytics snapshot for one website: requested window, series, prior period, and the channel recommendation. from/to default to the last 60 days in time_zone (UTC if omitted).

    mcp-tool

    {
      "type": "object",
      "properties": {
        "to": {
          "type": "string",
          "description": "inclusive end YYYY-MM-DD; default today"
        },
        "from": {
          "type": "string",
          "description": "inclusive start YYYY-MM-DD; default last 60 days"
        },
        "period": {
          "type": "string",
          "description": "named window instead of from/to: today, yesterday, 7d, 28d, 30d, 90d, 365d (each ends today), this_month, or last_month"
        },
        "currency": {
          "type": "string",
          "description": "lowercase ISO 4217 code"
        },
        "time_zone": {
          "type": "string",
          "description": "IANA time zone; default UTC"
        },
        "website_id": {
          "type": "string",
          "description": "website id (uuid) or the site domain (example.com); omit when the account has one website"
        },
        "granularity": {
          "type": "string",
          "description": "day, week, or month; default day"
        }
      },
      "additionalProperties": false
    }
    arguments 34 lines
  • answer_checks auth-required 9h ago

    Answer checks for one website: whether search-backed assistants (ChatGPT, Perplexity) name or cite the site for its buyer questions, this week and the 8 before. An input, not a score. locked=true means the plan does not run checks.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "website_id": {
          "type": "string",
          "description": "website id (uuid) or the site domain (example.com); omit when the account has one website"
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • impact_receipts auth-required never probed

    Logged changes for one website (notes, releases from the deploy hook, Stripe price changes, Google click drops), newest first, the newest of them with a receipt (a long list leaves the oldest without one): revenue per currency, signups and visitors over the same number of days before vs after, the top mover, and a confidence label. status is waiting (under a day old), collecting (the after window is still open) or ready. Read-only.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "days": {
          "type": "integer",
          "description": "changes logged in the last N days, 1-366; default 90"
        },
        "website_id": {
          "type": "string",
          "description": "website id (uuid) or the site domain (example.com); omit when the account has one website"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • journey_detail auth-required never probed

    Full observed history of one pseudonymous journey (visits, signups, payments) in time order, so you can say how a customer found the site. Take journey_id from the journeys tool. Paginate with cursor.

    mcp-tool

    {
      "type": "object",
      "required": [
        "journey_id"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "description": "page size 1-100; default 50"
        },
        "cursor": {
          "type": "string",
          "description": "next_cursor from the previous page"
        },
        "journey_id": {
          "type": "string",
          "description": "journey_id from the journeys tool (64 lowercase hex characters)"
        },
        "website_id": {
          "type": "string",
          "description": "website id (uuid) or the site domain (example.com); omit when the account has one website"
        }
      },
      "additionalProperties": false
    }
    arguments 25 lines
  • journeys auth-required never probed

    Paginated observed journeys for one website. Filter by first-touch source and medium, lifecycle, sort, page, and limit.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "to": {
          "type": "string",
          "description": "inclusive end YYYY-MM-DD; default today"
        },
        "from": {
          "type": "string",
          "description": "inclusive start YYYY-MM-DD; default last 60 days"
        },
        "page": {
          "type": "integer",
          "description": "page number; default 1"
        },
        "sort": {
          "type": "string",
          "description": "newest, oldest, spent, or stage; default newest"
        },
        "limit": {
          "type": "integer",
          "description": "page size 1-100; default 25"
        },
        "medium": {
          "type": "string",
          "description": "first-touch medium; supply with source"
        },
        "period": {
          "type": "string",
          "description": "named window instead of from/to: today, yesterday, 7d, 28d, 30d, 90d, 365d (each ends today), this_month, or last_month"
        },
        "source": {
          "type": "string",
          "description": "first-touch source; supply with medium"
        },
        "currency": {
          "type": "string",
          "description": "lowercase ISO 4217 code"
        },
        "lifecycle": {
          "type": "string",
          "description": "lifecycle_state; same enum as GET /v1/analytics/journeys"
        },
        "time_zone": {
          "type": "string",
          "description": "IANA time zone; default UTC"
        },
        "website_id": {
          "type": "string",
          "description": "website id (uuid) or the site domain (example.com); omit when the account has one website"
        },
        "granularity": {
          "type": "string",
          "description": "day, week, or month; default day"
        }
      },
      "additionalProperties": false
    }
    arguments 58 lines
  • money_alerts auth-required never probed

    Money alerts for one website: the alert rules (metric, condition, threshold, last reading against its expected band, open or not), the alerts that fired lately with the revenue at stake, and the channels they go to (kind and name only). Breakage alerts are in tracking_status.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "website_id": {
          "type": "string",
          "description": "website id (uuid) or the site domain (example.com); omit when the account has one website"
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • revenue_moves auth-required never probed

    Why revenue moved for one website: the window against the same-length prior window, split into new and renewal revenue, the channels, landing pages, search queries and referrer hosts (any site, not only AI) that moved it (the top 5 per group; search_query is estimated from Search Console), and which sources over-index among new payers. Same from/to/time_zone/currency as analytics_snapshot. Quote summary and the movers; do not recompute them.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "to": {
          "type": "string",
          "description": "inclusive end YYYY-MM-DD; default today"
        },
        "from": {
          "type": "string",
          "description": "inclusive start YYYY-MM-DD; default last 60 days"
        },
        "period": {
          "type": "string",
          "description": "named window instead of from/to: today, yesterday, 7d, 28d, 30d, 90d, 365d (each ends today), this_month, or last_month"
        },
        "currency": {
          "type": "string",
          "description": "lowercase ISO 4217 code"
        },
        "time_zone": {
          "type": "string",
          "description": "IANA time zone; default UTC"
        },
        "website_id": {
          "type": "string",
          "description": "website id (uuid) or the site domain (example.com); omit when the account has one website"
        }
      },
      "additionalProperties": false
    }
    arguments 30 lines
  • search_console_evidence auth-required never probed

    Search Console evidence for one website: action, gates, and landing-page rows. Same from/to/time_zone/currency as analytics_snapshot.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "to": {
          "type": "string",
          "description": "inclusive end YYYY-MM-DD; default today"
        },
        "from": {
          "type": "string",
          "description": "inclusive start YYYY-MM-DD; default last 60 days"
        },
        "period": {
          "type": "string",
          "description": "named window instead of from/to: today, yesterday, 7d, 28d, 30d, 90d, 365d (each ends today), this_month, or last_month"
        },
        "currency": {
          "type": "string",
          "description": "lowercase ISO 4217 code"
        },
        "time_zone": {
          "type": "string",
          "description": "IANA time zone; default UTC"
        },
        "website_id": {
          "type": "string",
          "description": "website id (uuid) or the site domain (example.com); omit when the account has one website"
        },
        "granularity": {
          "type": "string",
          "description": "day, week, or month; default day"
        }
      },
      "additionalProperties": false
    }
    arguments 34 lines
  • tracking_status auth-required never probed

    Is Motif still seeing this website? Last tracker event, last identified visitor, backend signup feed health, and the breakage alerts Motif's hourly check has open (tracker silent, signups silent or unmatched, visits dropped, Stripe or Search Console disconnected). An alert opens only once that check has recorded it, so judge the tracker by live and last_event_at too; empty alerts alone does not prove nothing is broken.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "website_id": {
          "type": "string",
          "description": "website id (uuid) or the site domain (example.com); omit when the account has one website"
        }
      },
      "additionalProperties": false
    }
    arguments 10 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 897929cc4fd4bf8f.

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