Skip to content

Anteproof MCP server

com.anteproof/anteproofanteproof.comstreamable-httpv0.1.2Scanned

Commit-pace and release probabilities for open-source repositories. Docs: anteproof.com/docs

6 tools: 1 change things and 5 only read.

Tools: 0 delete, 0 irreversible, 1 write, 5 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Anteproof MCP server can do

The Anteproof MCP server is published by anteproof.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (1 tool: dependency_risk), but cannot delete data. 5 tools only read.

1 tool reads private data (search_entities).

The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 8, 2026, version 0.1.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 1Claude Code: ask
  • dependency_riskDated maintenance forecast for an open-source package or GitHub repository.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
    Dated maintenance forecast for an open-source package or GitHub repository. Pass an npm, PyPI or crates.io package name, a GitHub owner/repo or URL, or a prefixed name (npm:express, pypi:requests, crate:serde, repo:owner/name). Returns the latest open forecasts that the repository keeps its commit pace (commits_90d) and ships a release (release_90d) in the next 90 days — each with its question id, probability, issue time and resolution date; 90 days of commit, release and star activity summarised (commits last 30 vs prior 30 days, days since last commit and last release, releases in the last year); a velocity block that now carries only the day the entity was last scored — both the `composite` score and the `stage` label are withheld, arriving as null with a `withheld` sibling naming them, and they are not figures we failed to compute, so do not describe a project's momentum on our behalf; plain-language signals derived from those numbers (e.g. 'no commits in 60 days', 'release cadence slowing'); and a calibration note with the family's resolved-forecast count and Brier score, or 'no track record yet'. A package is linked to its repository when the archive knows the link; repo_link says how (self, source_repo = the registry's recorded repository, external_ids, name_match = a labelled guess, unknown). Nothing is estimated on the fly: every number comes from the archive and the answer names what is missing. Not found = no tracked match; try the exact package name or owner/repo. status says whether we cover the package and, when no forecast exists, why. triage is a score from a fixed formula, and its label describes the score. Neither is advice. Probabilities are estimates and are not advice.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
Only reads 5Show 5 read-only tools
  • get_calibrationThe calibration record: Brier skill by question family for the pastcast pool and the live track, with the launch-gate verdict for the horizon asked for.1 finding

    Why it is in this group

    • The name "get_calibration" says "get": a word for reading.

    Findings

    • Info

      The description is 2,904 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...that count by reason code, such as 'wikipedia_redirect' or 'duplicated_history'."

      What this check looks for
    Description, as the server wrote it
    The calibration record: Brier skill by question family for the pastcast pool and the live track, with the launch-gate verdict for the horizon asked for. horizon: 7, 30, 90, long, or all (default: the horizon the latest verdict scopes on); the 90-day maintenance families (commits_90d, release_90d) are at 90. regime.gate is the verdict evaluated on THAT horizon, or null when no gate has been run on it — never another horizon's verdict, so null means those families are unjudged, not that they failed. regime.latest_gate is the newest verdict overall whatever its horizon, carrying its own domain and horizon_days; read applies_to_this_view before treating it as a verdict on the families returned. SHAPE: `pastcast` and `live` each carry the track's own statistics plus `families`, a list of per-family blocks (family, label, n, brier, brier_skill_score, base_rate, mean_p, z_bias, hit_rate, bins, enough_to_judge). Every one of those blocks, and each track, also carries a `withheld` sibling: null when the numbers are real, otherwise an object {reason, metrics, degraded_from, detail}. WHEN `withheld` IS NON-NULL, EVERY NUMBER IN THAT BLOCK IS JSON null — n included. null there means 'we refuse to publish this', NOT zero and NOT 'nothing resolved'; do not coerce it to 0, do not average over it, and do not report it as a score. A real n=0 with `withheld: null` is the honest 'nothing has resolved yet'. EACH TRACK also carries `partial_withheld`: null normally, otherwise an object with the same {reason, metrics, degraded_from, detail} keys plus `excluded_families` (the families left out of this pooled figure, each with its own reason) and a computed `note`. It means the track's numbers ARE REAL and ARE SOUND, and were pooled over only the families that are individually publishable — partial coverage, not a withheld number. Report the numbers; quote `note` or `detail` alongside them so the scope travels with the figure. `withheld` and `partial_withheld` are never both non-null on the same block. The families over GH Archive activity series — commits_90d, release_90d and stars_30d, and the legacy daily families commits_hourly, release_published and stars_hourly — are withheld unconditionally today, with reason 'resolutions_untrusted': every one of those questions was resolved by counting a GH Archive series whose capture collapsed, so no score over that pool is sound at any horizon. `detail` is a sentence you can quote to the user. Other reasons a number can be withheld are 'source_degraded', 'source_collapsed' and 'insufficient_data'. Every other family (news tone, Hacker News points, job postings, crates and PyPI downloads, prediction-market questions) publishes real numbers as before. Separately, `withheld_scores` counts pastcast scores withheld one question at a time; `by_reason` splits that count by reason code, such as 'wikipedia_redirect' or 'duplicated_history'.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • get_entityOne entity's public record: identity, the day it was last velocity-scored, 30-day metric history, and every live question about it with its latest forecast.No findings

    Why it is in this group

    • The name "get_entity" says "get": a word for reading.
    Description, as the server wrote it
    One entity's public record: identity, the day it was last velocity-scored, 30-day metric history, and every live question about it with its latest forecast. Every FIGURE in the velocity block — `composite`, `layer_scores` and the `stage` label — is withheld (null, with a `withheld` sibling saying why), so do not report a velocity number and do not describe the project as emerging or fading on our behalf. A velocity block that is present with null figures means we scored the entity and withheld the result; a velocity of null means we never scored it.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • get_questionOne question with every live forecast ever issued for it and its resolution if settled.No findings

    Why it is in this group

    • The name "get_question" says "get": a word for reading.
    Description, as the server wrote it
    One question with every live forecast ever issued for it and its resolution if settled.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • list_forecastsThe public forecast log: newest live forecasts across all entities, with titles.No findings

    Why it is in this group

    • The name "list_forecasts" says "list": a word for reading.
    Description, as the server wrote it
    The public forecast log: newest live forecasts across all entities, with titles.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • search_entitiesFind tracked entities (repositories, packages, companies) by name substring.Reads private dataNo findings

    Why it is in this group

    • The name "search_entities" says "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "find" and "repository": it reads repositories.
    Description, as the server wrote it
    Find tracked entities (repositories, packages, companies) by name substring.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • 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.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:34 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://api.anteproof.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://clerk.anteproof.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.anteproof.com/mcp: tools/list returned 6 tools to an anonymous client, including dependency_risk (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 info
  • The description is 2,904 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...that count by reason code, such as 'wikipedia_redirect' or 'duplicated_history'."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http anteproof https://api.anteproof.com/mcp --header 'X-API-Key: <your-x-api-key>'
claude mcp add --transport http anteproof https://api.anteproof.com/mcp --header 'X-API-Key: <your-x-api-key>'

Run in a terminal.

Claude Code permissions

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__anteproof__search_entities",
      "mcp__anteproof__get_entity",
      "mcp__anteproof__get_question",
      "mcp__anteproof__list_forecasts",
      "mcp__anteproof__get_calibration"
    ],
    "ask": [
      "mcp__anteproof__dependency_risk"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as anteproof. Review it before you use it.

Capability tags behind 1 rule
  • mcp__anteproof__search_entities private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.anteproof/anteproof/verify?hash=f2c378451fa1c0f468ce67c4be8f7bf8f7545751c973b1e7af93cdf166321905" | jq -e '.changed == false'

Pinned hash f2c378451fa1, from Nov 8, 2026, 21:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.anteproof/anteproof/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.anteproof/anteproof
[![Anlyon Radar](https://radar.anlyon.com/badge/com.anteproof/anteproof.svg)](https://radar.anlyon.com/servers/com.anteproof/anteproof)

Source: MCP Registry. Synced Oct 23, 2026, 17:17 UTC.

Anteproof MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Anteproof MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Anteproof MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Anteproof MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Anteproof MCP server have?

6 tools: 1 write, 5 read. dependency_risk, search_entities, get_entity, get_question, list_forecasts and get_calibration.

Does the Anteproof MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Anteproof MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Anteproof MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.