Skip to content

Imagine AI Benchmark

by useimagine.ai · remote · no sign-in to list tools · v0.1.0 · published by ai.useimagine

LinkedIn content benchmark for 900+ B2B companies and their teams, with an open scoring method.

Changes · 4

5 tools: 4 change things and 1 only read.

Scanned Oct 21, 2026

2 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http benchmark https://benchmark.useimagine.ai/api/mcp

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The description contains "every other tool", wording about other tools or servers.

    Matched text

    description: "...y, or tracking. Returns ids you pass to every other tool."

    What this check looks for
  • The server marks "category_breakdown" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The description's first verb is "post": a word for a change.

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

5 tools

Changes things 4Claude Code: ask
  • category_breakdownPost counts and engagement per content category (product update, hiring, personal story, industry insight, ...) for companies or people.1 finding

    Why it is in this group

    • The description's first verb is "post": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "category_breakdown" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The description's first verb is "post": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Post counts and engagement per content category (product update, hiring, personal story, industry insight, ...) for companies or people.

    Annotations the server declares

    • readOnlyHint: true
  • company_fit_summaryA company's page fit plus the distribution of its people's geometric means (median, baseline band), top people and who is under the 18-post floor.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    A company's page fit plus the distribution of its people's geometric means (median, baseline band), top people and who is under the 18-post floor. Company typical post = median over up to 5 counted fitted people plus the company page: founders, CEO and C-suite who posted in the last 90 days first, then the most active fitted people (by original posts in that window). With exactly one fitted account (a person or the page) the company ranks on that account's own fit, flagged "1 account"; it is held back while teammates still await their history pull. people.counted / countedPersonIds say who is in. Use for 'how is X doing on LinkedIn'.

    Annotations the server declares

    • readOnlyHint: true
  • industry_landscapeEvery account in an industry (or a custom company set): per-company rollup (page fit + people median over the 5 most active fitted people (peopleCounted), preliminary = "Few posts"…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Every account in an industry (or a custom company set): per-company rollup (page fit + people median over the 5 most active fitted people (peopleCounted), preliminary = "Few posts" under 40 team posts, solo = "1 account" when one fitted account carries the company), population vs the research baseline, and category lift with the author effect removed (which post types beat each author's own typical post). Public callers get bands and pooled lifts, the same as Discover. Use for "what works in fintech" or "where does X sit in its market".

    Annotations the server declares

    • readOnlyHint: true
  • methodologyImagine AI research rules (log-normal engagement, geometric means, research baseline 49/77/130).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Imagine AI research rules (log-normal engagement, geometric means, research baseline 49/77/130). Call once before interpreting any numbers.

    Annotations the server declares

    • readOnlyHint: true
Only reads 1Claude Code: allow
  • list_companiesList companies in the benchmark catalog (customers, competitors, industry peers).1 finding

    Why it is in this group

    • The name "list_companies" says "list": a word for reading.

    Findings

    • Warn

      The description contains "every other tool", wording about other tools or servers.

      Matched text

      description: "...y, or tracking. Returns ids you pass to every other tool."

      What this check looks for
    Description, as the server wrote it
    List companies in the benchmark catalog (customers, competitors, industry peers). Filter by name substring, industry, or tracking. Returns ids you pass to every other tool.

    Annotations the server declares

    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http benchmark https://benchmark.useimagine.ai/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__benchmark__list_companies"
    ],
    "ask": [
      "mcp__benchmark__company_fit_summary",
      "mcp__benchmark__industry_landscape",
      "mcp__benchmark__methodology",
      "mcp__benchmark__category_breakdown"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as benchmark. Review it before you use it.