io.github.usamahz/cpu-perf

What it mainly works on, as our AI model read its tool descriptions: nothing outside itself: it only answers questions.

None of its 13 tools are described as changing anything.

• askon 54 other serversreads or searches

  “Gather the evidence to answer a CPU performance question from the user's own work: the best passages from the linked papers, manuals and docs (with page numbers), the list's own entries and reasons, …”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  5 inputs, 1 required

  • questionstringrequired“The user's question, in their words plus the technical terms the sources are likely to use (e.g.”
  • contextstring or null“Optional pasted output to analyse with the question: perf stat (plain, -x, or -j), perf stat --topdown or -M TopdownL1, toplev, gcc -fopt-info / clang -Rpass r…”
  • detailstring“brief (default): trimmed passages, benchmark and editorial record only when relevant.”
  • sectioninteger or null“Restrict to one README section number (1-16).”
  • max_passagesinteger or null“How many source passages (default 5 brief, 8 full).”
• lookupon 16 other serversreads or searches

  “Ranked lookup over the reading list, its editorial record, notes and benchmark code, or over the full text of the linked sources (scope='sources').”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  4 inputs, 1 required

  • querystringrequired“Words to look for; British and American spellings both work.”
  • scopestring“list (entries, subsections, benchmarks), entries, sections, benchmarks, record (rejected, claims, link notes), rejected, claims, link_notes, notes, code, watch…”
  • sectioninteger or null“Restrict to one README section number.”
  • limitinteger
• searchon 763 other serversreads or searches

  “Find documents to read: the list's entries, sections, benchmarks and editorial record, and passages from the linked sources.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  1 input, 1 required

  • querystringrequired“What to look for, in plain words or exact identifiers.”
• fetchon 432 other serversreads or searches

  “The full text of one document found by search, with its citable URL.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  1 input, 1 required

  • idstringrequired“A document id returned by search, e.g.”
• get_sectionon 13 other serversreads or searches

  “The map of the list (no argument), or one section with its preamble, its entries in dependency order, its 'Reproduce it' benchmarks and, for the watchlist, what would promote each item.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  1 input

  • sectionstring or null“Omit for the table of contents.”
• get_entryon 14 other serversreads or searches

  “One listed source with everything around it: why it is listed, what to read before and after it, other places the same URL is listed, its benchmark, the numbers the list examined in it, alternatives …”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  1 input, 1 required

  • refstringrequired“An entry id (4.3.5; Start here uses 1.7), the source URL, or its title.”
• reading_pathreads or searches

  “What to read, in dependency order, to learn a topic from the list, ending with the benchmark that reproduces it.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  2 inputs

  • topicstring or null“Omit for the list's own path (Start here).”
  • max_stepsinteger
• get_benchmarkon 17 other serversreads or searches

  “The repository's runnable benchmarks: the claim each reproduces, the seven-field machine description, results tables, analysis, limits, source code and raw output.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  4 inputs

  • slugstring or null“Omit to list all.”
  • partsarray or null“Which parts to return; default claim, machine, results, analysis.”
  • offsetinteger
  • max_charsinteger
• editorial_recordreads or searches

  “Why something is or is not in the list: candidates that were considered and left out (with the rule each failed), every performance number examined against the seven fields (with its verdict), and li…”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  6 inputs

  • refstring or null“A URL, a title, a phrase, or a record id (r9.14, c9.5, l9.2).”
  • sectioninteger or null
  • kindstring“Which part of the record.”
  • rulestring or null“Rejections that failed a rule: '1'..'7', or a category: no_rule_failed, trimmed, size, cap, scope, left_to, duplicate, leaderboard, other.”
  • verdictstring or null“Claims with this verdict.”
  • limitinteger
• check_evidence

  “Audit a performance claim against the list's rule: a number counts only with CPU model and microarchitecture, core count, frequency with turbo and SMT state, compiler and flags, workload, baseline an…”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  2 inputs, 1 required

  • claimstringrequired“A performance claim with its number and whatever context it gives.”
  • source_urlstring or null“Where the claim comes from, if known.”
• read_sourceon 4 other serversreads or searches

  “The text of one linked source, from the local library, or fetched now and stored if it is not indexed yet.”

  Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

  6 inputs, 1 required

  • refstringrequired“An entry id, title or URL of a source the repository links.”
  • querystring or null“Return only the passages of this source that match this text.”
  • pageinteger or null“For PDFs: start at this page (pages past the indexed cap are read live).”
  • passageinteger or null“A passage id from ask or search: that passage in full, with the passages either side.”
  • offsetinteger
  • max_charsinteger
• read_fileon 35 other serversreads or searches

  “Any file of the repository the server knows: README, notes, section drafts, benchmark sources, build and run scripts, raw results, the checkers.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  3 inputs

  • pathstring or null“Repository-relative path, e.g.”
  • offsetinteger
  • max_charsinteger

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.