Skip to content

AutoPay MCP server

com.synairo.api/autopayapi.synairo.comstreamable-httpv1.6.0Scanned

Paid tools for agents: search, verify, web-to-Markdown, PDF extraction, security scans. x402 USDC

13 tools: 10 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 10 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 8
  • 2 findings, 2 high

Tools listed without sign-in. Remote posture

With Anlyon

10 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 AutoPay MCP server can do

The AutoPay MCP server is published by api.synairo.com, a domain the MCP Registry verified. It has 13 tools. It can create or change data (10 tools: verify, research, wallet, extract and 6 more), but cannot delete data. 3 tools only read.

2 tools bring in text other people can write (search and fetch); 8 tools can send data out of your system (fetch, extract, security_scan and 5 more).

The fixed checks matched 2 findings, 2 of them high severity (sensitive-path). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 1.6.0.

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.

13 tools

Changes things 10Claude Code: ask
  • extractDocument extraction: PDF/image (url or file_base64, max 10 MB) -> typed fields, line items, OCR text, document type ($0.025 per page, max 5 pages billed; synchronous, charged only …Can 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

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Document extraction: PDF/image (url or file_base64, max 10 MB) -> typed fields, line items, OCR text, document type ($0.025 per page, max 5 pages billed; synchronous, charged only on success). Pay with X-PAYMENT (x402 USDC on Base) or a prepaid API key.
  • researchQueue a short cited brief ($0.30).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.
    Description, as the server wrote it
    Queue a short cited brief ($0.30). Pay with X-PAYMENT (x402 USDC on Base) or a prepaid API key. Returns 202 with job_id. Typical ETA 10–20 minutes; poll get_job.
  • security_scanQuick passive security scan (passive only): TLS/cert, HTTPS redirect, HSTS + security headers, SPF/DMARC/DKIM/CAA/DNSSEC, exposed .git/.env/server-status/directory listing, securit…Can send data out1 finding

    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

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • High

      The description refers to ".git/.env/server-status/directory".

      Matched text

      description: "...ers, SPF/DMARC/DKIM/CAA/DNSSEC, exposed .git/.env/server-status/directory listing, security.txt; score + grade. $..."

      What this check looks for
    Description, as the server wrote it
    Quick passive security scan (passive only): TLS/cert, HTTPS redirect, HSTS + security headers, SPF/DMARC/DKIM/CAA/DNSSEC, exposed .git/.env/server-status/directory listing, security.txt; score + grade. $0.01; synchronous, charged only on success. Pay with X-PAYMENT (x402 USDC on Base) or a prepaid API key.
  • security_scan_dnsDNS / e-mail security check (passive only): SPF, DMARC, DKIM (common selectors), MX, CAA, DNSSEC; score + grade.Can 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

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    DNS / e-mail security check (passive only): SPF, DMARC, DKIM (common selectors), MX, CAA, DNSSEC; score + grade. $0.003; synchronous, charged only on success. Pay with X-PAYMENT (x402 USDC on Base) or a prepaid API key.
  • security_scan_exposureExposed files check (passive only): single GETs for /.git/HEAD, /.env, /server-status, directory listing, security.txt; score + grade.Can send data out1 finding

    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

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • High

      The description refers to "/.env".

      Matched text

      description: "...sive only): single GETs for /.git/HEAD, /.env, /server-status, directory listing, sec..."

      What this check looks for
    Description, as the server wrote it
    Exposed files check (passive only): single GETs for /.git/HEAD, /.env, /server-status, directory listing, security.txt; score + grade. $0.005; synchronous, charged only on success. Pay with X-PAYMENT (x402 USDC on Base) or a prepaid API key.
  • security_scan_fullFull passive security review (passive only): everything in quick + cookie flags, mixed content, server/version disclosure, RDAP domain age/expiry, up to 5 same-site subpages, prior…Can 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

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Full passive security review (passive only): everything in quick + cookie flags, mixed content, server/version disclosure, RDAP domain age/expiry, up to 5 same-site subpages, prioritized step-by-step remediation plan. $0.99; synchronous, charged only on success. Pay with X-PAYMENT (x402 USDC on Base) or a prepaid API key.
  • security_scan_headersSecurity headers check (passive only): HTTPS redirect, HSTS, CSP, X-Frame-Options/frame-ancestors, X-Content-Type-Options, Referrer-Policy, Permissions-Policy; score + grade.Can 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

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Security headers check (passive only): HTTPS redirect, HSTS, CSP, X-Frame-Options/frame-ancestors, X-Content-Type-Options, Referrer-Policy, Permissions-Policy; score + grade. $0.003; synchronous, charged only on success. Pay with X-PAYMENT (x402 USDC on Base) or a prepaid API key.
  • security_scan_tlsTLS certificate check (passive only): certificate trust, issuer, SAN, expiry, negotiated TLS version; score + grade.Can 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

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    TLS certificate check (passive only): certificate trust, issuer, SAN, expiry, negotiated TLS version; score + grade. $0.002; synchronous, charged only on success. Pay with X-PAYMENT (x402 USDC on Base) or a prepaid API key.
  • verifyQueue a claim/company/URL verification ($0.08).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.
    Description, as the server wrote it
    Queue a claim/company/URL verification ($0.08). Pay with X-PAYMENT (x402 USDC on Base) or a prepaid API key. Returns 202 with job_id. Typical ETA 10–20 minutes; poll get_job.
  • walletBase wallet snapshot: ETH and USDC balance, nonce, contract check, optional ERC-20 balance ($0.01, synchronous, charged only on success).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.
    Description, as the server wrote it
    Base wallet snapshot: ETH and USDC balance, nonce, contract check, optional ERC-20 balance ($0.01, synchronous, charged only on success). Pay with X-PAYMENT (x402 USDC on Base) or a prepaid API key.
Only reads 3Show 3 read-only tools
  • fetchFetch one public web page and return clean Markdown ($0.01, synchronous, charged only on success).Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "fetch" says "fetch": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "fetch" and "web": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Fetch one public web page and return clean Markdown ($0.01, synchronous, charged only on success). Pay with X-PAYMENT (x402 USDC on Base) or a prepaid API key.
  • get_jobPoll a previously queued AutoPay job by id until status is done.No findings

    Why it is in this group

    • The name "get_job" says "get": a word for reading.
    Description, as the server wrote it
    Poll a previously queued AutoPay job by id until status is done.

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 write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out8
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:19 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
12
Protocol version
2024-11-05
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

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

    Matched text

    https://api.synairo.com/mcp: tools/list returned 21 tools to an anonymous client, including wallet (write), email_check (write), verify (write), research (write), extract (write) and 7 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 high
  • The description refers to ".git/.env/server-status/directory".

    Matched text

    description: "...ers, SPF/DMARC/DKIM/CAA/DNSSEC, exposed .git/.env/server-status/directory listing, security.txt; score + grade. $..."

    What this check looks for
  • The description refers to "/.env".

    Matched text

    description: "...sive only): single GETs for /.git/HEAD, /.env, /server-status, directory listing, sec..."

    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 1.6.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http autopay https://api.synairo.com/mcp
claude mcp add --transport http autopay https://api.synairo.com/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__autopay__search",
      "mcp__autopay__get_job"
    ],
    "ask": [
      "mcp__autopay__verify",
      "mcp__autopay__research",
      "mcp__autopay__fetch",
      "mcp__autopay__wallet",
      "mcp__autopay__extract",
      "mcp__autopay__security_scan",
      "mcp__autopay__security_scan_headers",
      "mcp__autopay__security_scan_tls",
      "mcp__autopay__security_scan_dns",
      "mcp__autopay__security_scan_exposure",
      "mcp__autopay__security_scan_full"
    ],
    "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 autopay. Review it before you use it.

Capability tags behind 9 rules
  • mcp__autopay__search untrusted-input
  • mcp__autopay__fetch untrusted-input, outbound
  • mcp__autopay__extract outbound
  • mcp__autopay__security_scan outbound
  • mcp__autopay__security_scan_headers outbound
  • mcp__autopay__security_scan_tls outbound
  • mcp__autopay__security_scan_dns outbound
  • mcp__autopay__security_scan_exposure outbound
  • mcp__autopay__security_scan_full outbound

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.synairo.api/autopay/verify?hash=6d62ad8affb68282174fba83d39171501bf7ee23ca884b5b85afd1897a112490" | jq -e '.changed == false'

Pinned hash 6d62ad8affb6, from Nov 20, 2026, 09:18 UTC.

Watch

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

https://radar.anlyon.com/servers/com.synairo.api/autopay/changes.xml

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

Badge

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

Source: MCP Registry. Synced Nov 20, 2026, 09:17 UTC.

AutoPay MCP server: questions and answers

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

Is the AutoPay MCP server safe?

No scan can promise that. What its definitions show: 13 tools, 10 of which can change, send or delete something, and 2 findings (2 high) from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the AutoPay MCP server delete data?

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

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

13 tools: 10 write, 3 read. verify, research, wallet, extract, security_scan, security_scan_headers, security_scan_tls, security_scan_dns and 5 more.

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

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

Does the AutoPay MCP server send data to outside services?

8 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): fetch, extract, security_scan, security_scan_headers, security_scan_tls, security_scan_dns and 2 more.

Has the AutoPay MCP server changed its tools?

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