Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Fineprint

OCI · GHCR.IO/FINEPRINTCORP/FINEPRINT-MCP

Scan terms of service for risk. Returns 0-100 score, verdict, agent-friendliness, verbatim quotes.

+3 this week 44 Trust /100

Last scanned (5 hours ago)

Scores higher than 62% of OCI servers

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency32
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1169 tokens (~83/item across 14 items; 14 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
  • Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed oci/ghcr.io/fineprintcorp/fineprint-mcp@1.0.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 14 exposed · ~1,169 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
batch_scan_terms ~78

Scan up to 20 vendor ToS URLs in one call; each scan costs one quota unit. Returns a ranking (riskiest first) with scores, verdicts, and top clause categories per vendor. Use this for vendor shortlists and bake-offs.

NameTypeReqDescription
policy_id–––
urlsarrayyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

check_agent_access ~119

Pre-flight check: can an AI agent use this service at all, and on what terms? Answers from Fineprint's published leaderboard WITHOUT a scan and without spending quota — call this BEFORE scan_terms_of_service or before signing a principal up for anything. Returns the structured decision (automated access, account delegation, AI-agent terms, official-channels requirement) plus the overall friendliness verdict. If the service is unknown, run scan_terms_of_service on its terms URL.

NameTypeReqDescription
servicestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

check_quota ~25

Show the API key's tier, remaining monthly scans, and overage status.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

compare_scans ~49

Compare 2-20 previous scans: vendor ranking plus a category-by-category matrix of worst severity per vendor. Free — uses already-paid-for scans.

NameTypeReqDescription
scan_idsarrayyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

create_policy ~127

Create a custom ToS risk policy owned by your API key — your principal's own dealbreakers. block_categories veto a vendor (verdict BLOCK); flag_categories mark findings for review (verdict FLAG). Categories come from the 21-category taxonomy, e.g. binding_arbitration, data_training_use, data_sharing_resale, auto_renewal, unilateral_price_change. Use list_policies to see ids.

NameTypeReqDescription
block_categories–––
descriptionstring––
flag_categories–––
namestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_negotiation_playbook ~84

Negotiation playbook for a previous scan: for each flagged clause, what to ask the vendor for, an acceptable fallback, your leverage, and the walk-away signal. Use this when procurement or legal needs to push back on a vendor's terms. Negotiation guidance, not legal advice.

NameTypeReqDescription
scan_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_scan_report ~32

Retrieve a previous scan report as JSON (all clauses, quotes, scores).

NameTypeReqDescription
scan_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_tos_leaderboard ~74

Public ranking of services by ToS risk score. No API key needed. Use it to compare vendors BEFORE spending a scan. Scores are Fineprint's automated assessment as of the published date — informational only, not legal advice.

NameTypeReqDescription
limitinteger––
query–––
NameTypeReqDescription
resultstringyes–

No examples provided.

list_monitors ~24

List watched ToS URLs: baseline scores, last check time, limits.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

list_policies ~69

List the ToS risk policies available to you: the built-in system policies (standard, strict, procurement) plus any custom policies you have created. Pass a policy id as policy_id to any scan tool to judge vendors by your principal's rules instead of the default.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

scan_terms_of_service ~100

Scan a terms-of-service / privacy-policy URL for risky clauses. Call this BEFORE the agent accepts terms, creates an account, or grants a vendor access to the principal's data. Returns a risk score (0-100), a pass/flag/block verdict, and the top clauses with verbatim quotes. Informational assessment only — not legal advice.

NameTypeReqDescription
policy_id–––
urlstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

scan_terms_text ~67

Scan pasted terms text (when no URL is available). Same contract as scan_terms_of_service: risk score, verdict, quoted clauses. Informational assessment only — not legal advice.

NameTypeReqDescription
policy_id–––
source_url–––
textstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

terms_check ~185

Get a signed Act-Time Terms Receipt BEFORE acting on a service: what its terms said at this moment (risk score, agent-friendliness verdict, the verbatim clauses behind it), pinned to the terms document's hash and signed so anyone can verify it later — the evidence record for 'the agent checked before it acted'. Pass `service` for a published leaderboard service (e.g. 'discord') or `url` for any terms document. `action` optionally records what the agent was about to do (stored as caller-asserted; it is never witnessed). A receipt served from the board/cache costs no scan unit (monthly allowance); one that triggers a fresh scan consumes one.

NameTypeReqDescription
actionstring––
servicestring––
urlstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

watch_terms ~136

Watch a terms-of-service URL for changes. Establishes a quoted, scored baseline NOW, then every check compares the live document to it: unchanged checks are free, changed documents are re-scanned and diffed, and material changes (score jump, new high/critical clause, worsened verdict) raise an alert, POSTed to webhook_url when set. Use this when the principal depends on a vendor long-term: the agent should know when the terms it agreed to change underneath it.

NameTypeReqDescription
interval_daysinteger––
urlstringyes–
webhook_url–––
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the Fineprint MCP server?

Fineprint runs locally as a container image, launched with docker run --rm -i -e FINEPRINT_API_KEY -e FINEPRINT_API_URL ghcr.io/fineprintcorp/fineprint-mcp:1.0.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/fineprintcorp/fineprint-mcp

# add to Claude Code
claude mcp add fineprintcorp-fineprint -- docker run --rm -i -e FINEPRINT_API_KEY -e FINEPRINT_API_URL ghcr.io/fineprintcorp/fineprint-mcp:1.0.1

This image reads FINEPRINT_API_KEY and FINEPRINT_API_URL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

Common questions

What is the Fineprint MCP server?

Fineprint is an MCP server listed in the public MCP registry as io.github.fineprintcorp/fineprint. Scan terms of service for risk. Returns 0-100 score, verdict, agent-friendliness, verbatim quotes. This page covers its container image (ghcr.io/fineprintcorp/fineprint-mcp).

Is the Fineprint MCP server safe to use?

Fineprint scores 44 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Fineprint MCP server expose?

Fineprint exposes 14 tools: scan_terms_of_service, scan_terms_text, get_scan_report, get_tos_leaderboard, check_agent_access, and 9 more. Their descriptions and schemas cost roughly 1,169 tokens of context every time the server is loaded.

Is the Fineprint MCP server still maintained?

Fineprint is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.