Skip to content

SubscriptionFlow MCP server

io.github.AyeshaAtif-techloyce/subscriptionflowAyeshaAtif-techloycestreamable-httpv1.0.0Scanned

Read and update SubscriptionFlow billing data: customers, invoices, subscriptions and reports.

9 tools: 1 do something that can't be undone, 1 change things and 7 only read.

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

Tools listed without sign-in. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the SubscriptionFlow MCP server can do

The SubscriptionFlow MCP server is published by the GitHub account AyeshaAtif-techloyce. It has 9 tools. It can do things that cannot be undone, such as sending, paying or publishing (sf_contact) and create or change data (1 tool: sf_request_demo), but cannot delete data. 7 tools only read.

2 tools read private data (sf_find_instance and sf_contact_form); 1 tool brings in text other people can write (sf_find_instance); 1 tool can send data out of your system (sf_contact). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

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

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 1.0.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.

9 tools

Can't be undone 1Claude Code: ask
  • sf_contactSend a message to the SubscriptionFlow team.Can send data out1 finding

    Why it is in this group

    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe description's first verb is "send": it sends or publishes something to other people.
    • outboundThe input takes a destination (input.phone): what the tool writes goes there.

    Findings

    • Warn

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

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "send": a word for sending, and what is sent cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Send a message to the SubscriptionFlow team. Requires a name, work email, company and message; a phone number is optional. Returns a reference id the sender can quote. Nothing submitted is echoed back. Public, read-only.

    Annotations the server declares

    • title: Contact the SubscriptionFlow team
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
Changes things 1Claude Code: ask
  • sf_request_demoSubmit a request for a SubscriptionFlow demo.1 finding

    Why it is in this group

    • The name "sf_request_demo" says "request": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

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

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "sf_request_demo" says "request": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Submit a request for a SubscriptionFlow demo. Validates and stores/forwards the request and returns a generic acknowledgement. Public, read-only.

    Annotations the server declares

    • title: Request a SubscriptionFlow demo
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
Only reads 7Show 7 read-only tools
  • fetchFetch one published SubscriptionFlow knowledge article by id (an id returned by `search`).No findings

    Why it is in this group

    • The name "fetch" says "fetch": a word for reading.
    Description, as the server wrote it
    Fetch one published SubscriptionFlow knowledge article by id (an id returned by `search`). Draft or unknown ids are not found. Public, read-only.

    Annotations the server declares

    • title: Fetch a knowledge article
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • sf_connection_statusCheck whether this connection is signed in to a SubscriptionFlow account.No findings

    Why it is in this group

    • The name "sf_connection_status" says "status": a word for reading.
    Description, as the server wrote it
    Check whether this connection is signed in to a SubscriptionFlow account. Call it when the user asks for their own SubscriptionFlow data (customers, subscriptions, invoices, payments, billing, reports) or for a change, and no account tools are listed. Right now the connection is not signed in; the result says how to reconnect. Read-only.

    Annotations the server declares

    • title: Check SubscriptionFlow sign-in
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • sf_contact_formDisplay an interactive form for getting in touch with the SubscriptionFlow team.Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "display": a word for reading.

    What it can reach

    • private-dataThe name "sf_contact_form" says "contact": it reads contacts.
    Description, as the server wrote it
    Display an interactive form for getting in touch with the SubscriptionFlow team. The form collects a name, work email, company, optional phone number and a message, and submits them through `sf_contact`.

    Annotations the server declares

    • title: Show a contact form
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • sf_demo_bookingShow a form to book a product demo.No findings

    Why it is in this group

    • The description's first verb is "show": a word for reading.
    Description, as the server wrote it
    Show a form to book a product demo. Collects name, email and company, then opens the scheduling page with those details pre-filled. The lead itself is captured by `sf_request_demo`. Public, read-only.

    Annotations the server declares

    • title: Book a SubscriptionFlow demo
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • sf_find_instanceGiven a work email, start the enumeration- and timing-safe instance lookup.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "sf_find_instance" says "find": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Given a work email, start the enumeration- and timing-safe instance lookup. For privacy the response is deliberately generic and constant — it never confirms or denies whether an account exists; if a match is found, instructions are sent to that email. Public, read-only.

    Annotations the server declares

    • title: Find my SubscriptionFlow instance
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • sf_product_infoShow what SubscriptionFlow does — features, the industries it serves, integrations, benefits or how pricing works.No findings

    Why it is in this group

    • The description's first verb is "show": a word for reading.
    Description, as the server wrote it
    Show what SubscriptionFlow does — features, the industries it serves, integrations, benefits or how pricing works. Use topic "all" to show everything at once. Public, read-only.

    Annotations the server declares

    • title: About SubscriptionFlow
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

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.

2 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__subscriptionflow__sf_contact"
    ]
  }
}

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 18, 2026, 16:19 UTC, unchanged since Nov 18, 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
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.subscriptionflow.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://mcp.subscriptionflow.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

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

    Matched text

    https://mcp.subscriptionflow.com/mcp: tools/list returned 9 tools to an anonymous client, including sf_contact (irreversible), sf_request_demo (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

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

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "sf_request_demo" says "request": a word for a change.

    What this check looks for
  • The server marks "sf_contact" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "send": a word for sending, and what is sent cannot be taken back.

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

claude mcp add --transport http subscriptionflow https://mcp.subscriptionflow.com/mcp
claude mcp add --transport http subscriptionflow https://mcp.subscriptionflow.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__subscriptionflow__search",
      "mcp__subscriptionflow__fetch",
      "mcp__subscriptionflow__sf_find_instance",
      "mcp__subscriptionflow__sf_product_info",
      "mcp__subscriptionflow__sf_demo_booking",
      "mcp__subscriptionflow__sf_contact_form",
      "mcp__subscriptionflow__sf_connection_status"
    ],
    "ask": [
      "mcp__subscriptionflow__sf_request_demo",
      "mcp__subscriptionflow__sf_contact"
    ],
    "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 subscriptionflow. Review it before you use it.

Capability tags behind 3 rules
  • mcp__subscriptionflow__sf_find_instance private-data, untrusted-input
  • mcp__subscriptionflow__sf_contact outbound
  • mcp__subscriptionflow__sf_contact_form 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/io.github.AyeshaAtif-techloyce/subscriptionflow/verify?hash=d05e16cb3d7995cad240d92c3ef53a068e5f90c5aa78c86fcb20fb364cf41d19" | jq -e '.changed == false'

Pinned hash d05e16cb3d79, from Nov 18, 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/io.github.AyeshaAtif-techloyce/subscriptionflow/changes.xml

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

Badge

Anlyon Radar badge for io.github.AyeshaAtif-techloyce/subscriptionflow
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.AyeshaAtif-techloyce/subscriptionflow.svg)](https://radar.anlyon.com/servers/io.github.AyeshaAtif-techloyce/subscriptionflow)

Source: MCP Registry. Synced Nov 18, 2026, 10:17 UTC.

SubscriptionFlow MCP server: questions and answers

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

Is the SubscriptionFlow MCP server safe?

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

Can the SubscriptionFlow MCP server delete data?

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

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

Yes. 1 tool can send, pay, publish or merge: sf_contact.

What tools does the SubscriptionFlow MCP server have?

9 tools: 1 irreversible, 1 write, 7 read. sf_contact, sf_request_demo, search, fetch, sf_find_instance, sf_product_info, sf_demo_booking, sf_contact_form and 1 more.

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

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

Does the SubscriptionFlow MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): sf_contact.

Has the SubscriptionFlow MCP server changed its tools?

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