Skip to content

FactStamp MCP server

au.com.alpineai/factstampalpineai.com.austreamable-httpv0.1.4Scanned

Verify a company, figure or citation before you rely on it. Card or crypto; signed receipt.

18 tools: 16 change things and 2 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

16 tools here change things. Govern them.

  • 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 FactStamp MCP server can do

The FactStamp MCP server is published by alpineai.com.au, a domain the MCP Registry verified. It has 18 tools. It can create or change data (16 tools: route_claim, buy_card_package, check_figure, check_entity and 12 more), but cannot delete data. 2 tools only read.

17 tools bring in text other people can write (list_series, route_claim, buy_card_package and 14 more); 2 tools can send data out of your system (watch_add and watch_portfolio).

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

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 10, 2026, version 0.1.4.

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.

18 tools

Changes things 16Claude Code: ask
  • audit_claimsAudit what an agent believes about companies.Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Audit what an agent believes about companies. Send up to 10 claims ({subject:{identifier|name|jurisdiction}, field, value}) and get, claim by claim: supported (the register says this), contradicted (it says something else, shown), stale (the register records it as FORMER, with the date it changed) or not_checkable (we could not check it, and why). Every verdict carries the register's own date and a citation, and the whole batch gets ONE receipt. field is a name from the published vocabulary (legal_name, previous_name, identifier, status, legal_form, registration_date, dissolution_date, registered_address, activity_code), never open text: a field outside it is not_checkable, not a guess. US$0.20 on this rail for up to 10 claims; longer audits go to POST /audit, which prices the body at US$0.02 a claim with a US$0.20 floor. Comes with an Ed25519-signed receipt covering the question, the verdict, the sources and the time, checkable offline against the published key at /.well-known/factstamp-issuer.json — so the check itself can be audited later by someone who was not here.

    Annotations the server declares

    • title: Audit claims against the registers
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • buy_card_packageIncluded.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Included. Opens a Stripe Checkout Session for one card package and returns its payment link and its session id. This tool charges nothing and produces no artefact: on the card rail the thing that taps is a human. The package's work runs only at its redeem path, after Stripe's own record says that session is paid.

    Annotations the server declares

    • title: Open a card package payment link
    • readOnlyHint: false
    • idempotentHint: false
    • openWorldHint: true
  • check_documentA whole document in one call: the claims that can be verified against a primary source, each answered by the door that owns it with its own signed receipt, plus one receipt over th…Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    A whole document in one call: the claims that can be verified against a primary source, each answered by the door that owns it with its own signed receipt, plus one receipt over the document. Extraction is mechanical, so the claim list and the count are reproducible from your document alone — nothing is inferred. This rail answers the first 5 claims for a flat US$0.25 (5 cents a claim); a better-funded document goes to the pack-funded HTTP door (POST /document, up to 25 claims at the same 5 cents a claim), whose included preview lists the claims and the price before anything is charged — use it first if you are unsure the document holds anything checkable. This door reads PROSE: to check a bare list of references or package versions, use verify_bulk, and a single claim belongs to check_figure, check_entity, verify_citation or verify_package. Comes with an Ed25519-signed receipt covering the question, the verdict, the sources and the time, checkable offline against the published key at /.well-known/factstamp-issuer.json — so the check itself can be audited later by someone who was not here.

    Annotations the server declares

    • title: Check a whole document
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • check_entityVerify a legal entity: does this company exist, under which identifier and jurisdiction, and is its registration current?Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Verify a legal entity: does this company exist, under which identifier and jurisdiction, and is its registration current? Cited to open primary registers (the GLEIF LEI index and US SEC EDGAR). Returns found, ambiguous, not_found or unknown; a near name match is never reported as a match. Not advice, not a credit check, not a sanction screen. Comes with an Ed25519-signed receipt covering the question, the verdict, the sources and the time, checkable offline against the published key at /.well-known/factstamp-issuer.json — so the check itself can be audited later by someone who was not here.

    Annotations the server declares

    • title: Verify a legal entity
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • check_entity_fileThe entity file: ONE paid answer holding everything we hold about one company: the whole picture in ONE call rather than four separate facts stitched together, at the point of sign…Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    The entity file: ONE paid answer holding everything we hold about one company: the whole picture in ONE call rather than four separate facts stitched together, at the point of signing, onboarding, paying or acquiring a counterparty. It holds identity and standing, the registered office, SIC activity and previous names, the filing position, a sanctions screen across our six lists, and the ownership the registers publish (the persons with significant control where a register publishes them, and the declared parent relationships where a company has an LEI, with beneficial ownership stated as not public in nearly every country we cover) — each cited to the register it came from with its retrieval time — plus ONE coverage block naming every register consulted and every one NOT consulted. Returns found, ambiguous, not_found or unknown for the company itself; a register that was not read is named as not read, never guessed. 33p UK-facing, settled in USDC at the dated rate. Not advice, not a credit check. Comes with an Ed25519-signed receipt covering the question, the verdict, the sources and the time, checkable offline against the published key at /.well-known/factstamp-issuer.json — so the check itself can be audited later by someone who was not here.

    Annotations the server declares

    • title: The entity file: everything we hold about one company
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • check_entity_file_caCanadian company lookup and Canadian federal corporation register check by nine-digit Business Number (BN) only: corporation number, BN, governing legislation, every registered nam…Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Canadian company lookup and Canadian federal corporation register check by nine-digit Business Number (BN) only: corporation number, BN, governing legislation, every registered name with type, current flag and effective date, the register's own status, the registered address, the MINIMUM and MAXIMUM NUMBER of directors as a count rather than the people, and the annual-return history with dated incorporation and other activities, in six sections from one live read of Corporations Canada, with one signed receipt and one coverage block. The public endpoint is keyed by Business Number, so a name alone cannot reach it; provincial and territorial corporations are a different register this file does not read; director and officer names and beneficial owners are not published on this path. Returns found, not_found or unknown; unknown is a first-class answer and is not charged. Not advice, not a credit check and not a KYB service. Comes with an Ed25519-signed receipt covering the question, the verdict, the sources and the time, checkable offline against the published key at /.well-known/factstamp-issuer.json — so the check itself can be audited later by someone who was not here.

    Annotations the server declares

    • title: Canada: one company file, 6 sections
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • check_entity_file_ilIsraeli company lookup and company register check by company number (nine digits, with its own check digit) or by registered name, Hebrew or English: identity, corporation type, th…Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Israeli company lookup and company register check by company number (nine digits, with its own check digit) or by registered name, Hebrew or English: identity, corporation type, the register's own status and sub-status, description and stated purpose, incorporation date, government-company flag and restrictions, last annual-report year and the structured registered address, in seven sections from one live read of the Registrar of Companies dataset on data.gov.il, with one signed receipt and one coverage block. No officers, directors, shareholders or beneficial owners as people, and no financial statements: those sit behind the Registrar's paid company extract, which this file does not read. Amended returns and a change registered after the dataset's last refresh may not yet appear. Returns found, ambiguous, not_found or unknown; unknown is a first-class answer and is not charged. Not advice, not a credit check and not a KYB service. Comes with an Ed25519-signed receipt covering the question, the verdict, the sources and the time, checkable offline against the published key at /.well-known/factstamp-issuer.json — so the check itself can be audited later by someone who was not here.

    Annotations the server declares

    • title: Israel: one company file, 7 sections
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • check_figureSubmit the dated figure you are about to act on.Reads text others write1 finding

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

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

      Matched text

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

      What this check looks for
    Description, as the server wrote it
    Submit the dated figure you are about to act on. Returns verified, stale, contradicted or unknown, cited to the publisher's own series with its as-of date. Relevant wherever a number is going onto a page, deck or decision. Not advice. Comes with an Ed25519-signed receipt covering the question, the verdict, the sources and the time, checkable offline against the published key at /.well-known/factstamp-issuer.json — so the check itself can be audited later by someone who was not here.

    Annotations the server declares

    • title: Check a figure claim
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • check_sanctionsSanctions screening of a name, for whether a person or company is on a sanctions list — and which one.Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Sanctions screening of a name, for whether a person or company is on a sanctions list — and which one. Reads OFAC SDN, the UN consolidated list, the EU Financial Sanctions File and the UK Sanctions List, and returns listed, mismatch, not_found or unknown. The answer names the lists that were consulted with each one's retrieval date (and the UK list's own report date); a list that was not consulted is named as not consulted, and unknown is the answer when we cannot tell. A near name is never reported as the same party, and a listed verdict stands even when another list was not consulted. Not advice, not a legal determination. Comes with an Ed25519-signed receipt covering the question, the verdict, the sources and the time, checkable offline against the published key at /.well-known/factstamp-issuer.json — so the check itself can be audited later by someone who was not here.

    Annotations the server declares

    • title: Screen a name against sanctions lists
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • check_vatAn EU VAT number check — VAT validity, and the VAT registration behind it.Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    An EU VAT number check — VAT validity, and the VAT registration behind it. Reads the official VIES service (European Commission), keyless. Returns valid, invalid or unknown — an outage is NEVER reported as invalid — with the member state, the register's own request date, and the trader identity only where that member state discloses it. Some member states disclose nothing; the answer says so rather than showing an empty string. GB is out of scope after Brexit (XI, Northern Ireland, is covered). Not tax advice, not a credit check. Comes with an Ed25519-signed receipt covering the question, the verdict, the sources and the time, checkable offline against the published key at /.well-known/factstamp-issuer.json — so the check itself can be audited later by someone who was not here.

    Annotations the server declares

    • title: Check an EU VAT number
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • route_claimIncluded.Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Included. Shows which series a claim would be routed to, the value and date extracted, and the signals behind the score. Returns NO verdict — pay for check_figure when you want one.

    Annotations the server declares

    • title: Route a claim to a series (no verdict)
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • verify_bulkCheck a whole list in one call: a bibliography or a dependency manifest.Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Check a whole list in one call: a bibliography or a dependency manifest. Send items[] of {tool, input} or the citations[]/packages[] shorthand. Up to 12 items at a flat US$0.12 on this door; longer lists pay 0.016667 an item on the pack-funded HTTP door (POST /bulk, up to 25 items). Every item is answered by the same door that answers a single call, so the verdicts cannot disagree. This door takes a LIST of references or package versions, not prose: to check the claims inside a document, use check_document, and to check one reference use verify_citation or verify_package. Comes with an Ed25519-signed receipt covering the question, the verdict, the sources and the time, checkable offline against the published key at /.well-known/factstamp-issuer.json — so the check itself can be audited later by someone who was not here.

    Annotations the server declares

    • title: Check a whole list
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • verify_citationSays whether a citation can be repeated.Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Says whether a citation can be repeated. Submit a DOI, an arXiv ID or a paper title: returns whether it exists, what it is (title, authors, year, container) and whether it has been retracted, cited to Crossref and arXiv. Optionally send what your document claims (title, authors, year, journal) and every field is compared one by one — a disagreement is reported as mismatch, never as verified. A near title match is never reported as verified; a title that is absent from both returns not_found. Not advice. Comes with an Ed25519-signed receipt covering the question, the verdict, the sources and the time, checkable offline against the published key at /.well-known/factstamp-issuer.json — so the check itself can be audited later by someone who was not here.

    Annotations the server declares

    • title: Verify a citation
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • verify_packageReports on a dependency at the point of installation.Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Reports on a dependency at the point of installation. Submit a package and version plus its ecosystem: returns whether that exact version exists, whether it is yanked or deprecated, and every advisory OSV lists against it. An invented version returns not_found with the real versions nearest to it, and an invented name returns the published names that look like it — which is the point, because that is how slopsquatting gets installed. Not a security audit. Comes with an Ed25519-signed receipt covering the question, the verdict, the sources and the time, checkable offline against the published key at /.well-known/factstamp-issuer.json — so the check itself can be audited later by someone who was not here.

    Annotations the server declares

    • title: Verify a package version
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • watch_addWatch ONE citation or ONE package version instead of checking it once.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "watch_add" says "add": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.webhook): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Watch ONE citation or ONE package version instead of checking it once. Send kind ('citation' or 'package') and the subject (a DOI, an arXiv ID or a title; or npm:express@4.18.2). The first check is answered immediately and signed, then re-checked daily for 30 days; every real change (a retraction, a new advisory, a yanked version) is recorded with its own signed receipt. Returns a read URL and a token shown once; optionally send an https webhook and each change is POSTed to it. For a whole list of references under one purchase use watch_portfolio; for a one-off answer that does not need watching, use verify_citation or verify_package. Comes with an Ed25519-signed receipt covering the question, the verdict, the sources and the time, checkable offline against the published key at /.well-known/factstamp-issuer.json — so the check itself can be audited later by someone who was not here.

    Annotations the server declares

    • title: Watch a citation or package
    • readOnlyHint: false
    • idempotentHint: false
    • openWorldHint: true
  • watch_portfolioWatch a whole list instead of one reference at a time: up to 25 citations or package versions re-checked every day for 30 days under one token.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.webhook): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Watch a whole list instead of one reference at a time: up to 25 citations or package versions re-checked every day for 30 days under one token. US$5 a portfolio — 20 cents a reference, under a cent a check — and the first check on every reference is answered and signed immediately. Each real change carries its own signed receipt, and nothing is sent when nothing changed. ONE purchase covers the whole list: for a single subject on its own, use watch_add. Returns a read URL and a token shown once. Comes with an Ed25519-signed receipt covering the question, the verdict, the sources and the time, checkable offline against the published key at /.well-known/factstamp-issuer.json — so the check itself can be audited later by someone who was not here.

    Annotations the server declares

    • title: Watch a list of references
    • readOnlyHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • list_card_packagesIncluded.No findings

    Why it is in this group

    • The name "list_card_packages" says "list": a word for reading.
    Description, as the server wrote it
    Included. The one-off card packages as one machine-readable catalogue: the 11 products and their 13 prices in Australian dollars, the unit one payment buys for each SKU, what the package returns, and where the input is sent. One payment each, nothing metered, nothing subscribed. The per-call doors stay open beside them.

    Annotations the server declares

    • title: List the one-off card packages
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • list_seriesIncluded.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Included. What this engine covers, the publisher and as-of date behind each series, and the no-guess rule.

    Annotations the server declares

    • title: List what this engine covers
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: 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 private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write17
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
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:30 UTC, unchanged since Nov 20, 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
18
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://agents.factstamp.dev/.well-known/oauth-protected-resource/mcp
Authorization servers
https://agents.factstamp.dev
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 18 tools that change things (18 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://agents.factstamp.dev/mcp: tools/list returned 20 tools to an anonymous client, including route_claim (write), buy_card_package (write), check_figure (write), check_entity (write), check_entity_file (write) and 13 more

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Tools that change things, listed without credentials: 16 to 18
  2. Oct 29, 2026
    • Tools that change things, listed without credentials: 15 to 16

Findings

Matches of fixed checks, with the text they matched.

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

    Matched text

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

    What this check looks for

History

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

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 16 -> 18.View diff
    • Tools that change things, listed without credentials: 16 to 18
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 15 -> 16.View diff
    • Tools that change things, listed without credentials: 15 to 16
  3. Tools1 added, 5 changed.+1 added~5 changedView diff

Install

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

claude mcp add --transport http factstamp https://agents.factstamp.dev/mcp
claude mcp add --transport http factstamp https://agents.factstamp.dev/mcp

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__factstamp__list_series",
      "mcp__factstamp__list_card_packages"
    ],
    "ask": [
      "mcp__factstamp__route_claim",
      "mcp__factstamp__buy_card_package",
      "mcp__factstamp__check_figure",
      "mcp__factstamp__check_entity",
      "mcp__factstamp__check_entity_file",
      "mcp__factstamp__check_entity_file_il",
      "mcp__factstamp__check_entity_file_ca",
      "mcp__factstamp__check_sanctions",
      "mcp__factstamp__check_vat",
      "mcp__factstamp__verify_citation",
      "mcp__factstamp__verify_package",
      "mcp__factstamp__watch_add",
      "mcp__factstamp__watch_portfolio",
      "mcp__factstamp__verify_bulk",
      "mcp__factstamp__check_document",
      "mcp__factstamp__audit_claims"
    ],
    "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 factstamp. Review it before you use it.

Capability tags behind 17 rules
  • mcp__factstamp__list_series untrusted-input
  • mcp__factstamp__route_claim untrusted-input
  • mcp__factstamp__buy_card_package untrusted-input
  • mcp__factstamp__check_figure untrusted-input
  • mcp__factstamp__check_entity untrusted-input
  • mcp__factstamp__check_entity_file untrusted-input
  • mcp__factstamp__check_entity_file_il untrusted-input
  • mcp__factstamp__check_entity_file_ca untrusted-input
  • mcp__factstamp__check_sanctions untrusted-input
  • mcp__factstamp__check_vat untrusted-input
  • mcp__factstamp__verify_citation untrusted-input
  • mcp__factstamp__verify_package untrusted-input
  • mcp__factstamp__watch_add untrusted-input, outbound
  • mcp__factstamp__watch_portfolio untrusted-input, outbound
  • mcp__factstamp__verify_bulk untrusted-input
  • mcp__factstamp__check_document untrusted-input
  • mcp__factstamp__audit_claims untrusted-input

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/au.com.alpineai/factstamp/verify?hash=20b7e2645c5cd3e827fbeebc01b569bc6cfb24a192d09f9739b3d1d6d5553976" | jq -e '.changed == false'

Pinned hash 20b7e2645c5c, from Nov 10, 2026, 00:18 UTC.

Watch

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

https://radar.anlyon.com/servers/au.com.alpineai/factstamp/changes.xml

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

Badge

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

Source: MCP Registry · repository. Synced Oct 28, 2026, 16:17 UTC.

FactStamp MCP server: questions and answers

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

Is the FactStamp MCP server safe?

No scan can promise that. What its definitions show: 18 tools, 16 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 FactStamp MCP server delete data?

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

Can the FactStamp 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 FactStamp MCP server have?

18 tools: 16 write, 2 read. route_claim, buy_card_package, check_figure, check_entity, check_entity_file, check_entity_file_il, check_entity_file_ca, check_sanctions and 10 more.

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

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

Does the FactStamp MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): watch_add and watch_portfolio.

Has the FactStamp MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 28, 2026. Every change is on this page and in its Atom feed.