The questions you'd ask before paying.

What exactly do I get for free?

Nine of the ten servers give you 3 tool calls in total — not three per tool, and not three per day. That one allowance is shared across every tool the server exposes and runs only once. The counter is written to ~/.aivp-mcp/usage.json so it survives restarts; if that path is not writable, the server falls back to an in-memory count for the life of the process.

Data Aggregator is the exception: it allows 100 tool calls per UTC day, and the allowance resets at midnight UTC. None of this needs an account, a credit card, or a sign-up.

Does it work offline, or does it phone home?

License checking never phones home. An Ed25519 public key is compiled into each package and is used only to verify the signature on your key — there is no account, no license server, and no usage reporting.

Whether a server needs the network for its actual work depends on the server. Data Aggregator and Market Data Analyzer fetch live third-party data such as Yahoo Finance, CoinGecko, and Frankfurter/ECB; SEO Audit Tool fetches the URLs you give it; and Social Media Analytics makes public-profile requests with a deterministic fallback. AI Cost Analyzer, Security Scanner, Schema Designer, API Doc Generator, Resume Optimizer, and Legal Doc Analyzer analyze the text or definitions you supply locally, with no external API calls. Check a package page for that server's exact data sources.

What does a license key actually unlock?

A key removes the no-key call limit for that one product, so you can keep calling its tools past the free allowance.

On seven of the ten servers the entry plan also withholds specific Pro-only tools, and a Pro or higher key unlocks those named tools as well. The table below lists exactly which tools each entry plan leaves locked. The other three servers — AI Cost Analyzer, Security Scanner, and Data Aggregator — include every tool on every paid plan.

Is one key good for all ten servers?

No. Every key encodes a single product, and each server enforces that binding: a key issued for product X is refused by product Y.

The key format does include a bundle value (product: all) that any server would accept, but bundle keys are not currently sold — so plan on one key per server you license.

How long does a key last, and what happens when it expires?

Every key sold today is valid for 365 days — including the keys minted by the monthly subscription plans.

The key is a signed offline token, and there is no revocation mechanism: a 365-day key keeps working for its full 365 days whether or not the monthly subscription behind it is still active.

When a key reaches its expiry, the client reports it as expired and the server stops honoring it, falling back to refusing calls just as it would with no key at all. Re-licensing issues a fresh key.

Can I use one key on more than one machine?

Nothing in the software stops you. Verification is offline and the key is just an environment variable, so the same key works on any machine where you set LICENSE_KEY.

The code contains no device binding and no seat enforcement, and the repository defines no separate seat or device licensing terms. This describes how the software behaves rather than granting a specific entitlement.

How do I activate after paying?

The success page you are returned to after checkout shows the key on screen once Stripe reports the payment as paid. That page is the authoritative copy of your key — copy or bookmark it.

Email is a secondary channel and it is not available today: the sending domain is not verified, so the provider rejects delivery to any address other than the account owner's. Email delivery is never guaranteed, and when it does become available it is only a convenience copy. Do not wait for an email and never rely on the inbox.

To activate, paste the key into the env block of that server's entry in your MCP client config as LICENSE_KEY, then restart the client.

{
  "mcpServers": {
    "seo-audit-tool": {
      "command": "npx",
      "args": ["-y", "seo-audit-tool"],
      "env": {
        "LICENSE_KEY": "paste-your-key-here"
      }
    }
  }
}

Lost it already? The recovery page can re-derive the same key.

I paid and closed the tab — how do I get my key back?

Open the recovery page and paste the Stripe checkout link — or just the cs_… session id — from the browser you paid in. It re-derives the exact same key deterministically and keeps working for as long as that key is still valid.

Treat the checkout link and session id as sensitive: anyone who has them can view the key. Stripe's receipt email does not contain the session id, so look in the history of the browser that made the purchase.

Which MCP clients are supported?

Any spec-compliant MCP client works. The ones we document are Claude Desktop, Claude Code, Cursor, and Windsurf. Three of them accept the identical JSON object under an mcpServers key and differ only in which file you edit.

• Claude Desktop ~/Library/Application Support/Claude/claude_desktop_config.json

  Windows: %APPDATA%\Claude\claude_desktop_config.json. In the app: Settings → Developer → Edit Config.

• Cursor ~/.cursor/mcp.json

  Or .cursor/mcp.json inside a single project.

• Windsurf ~/.codeium/windsurf/mcp_config.json

  Cascade panel → MCP icon → edit the raw config.

Claude Code takes no file — register a server with one command. The --transport stdio flag must sit between --env and the server name, so add a key by placing --env LICENSE_KEY=your-key before --transport.

$ claude mcp add --transport stdio <server-key> -- npx -y <package>

npx -y <package> just sits there — is it broken?

No — that is the expected behavior. These are stdio servers, so on its own npx -y <package> starts the process and then waits silently for an MCP client to talk to it over standard input; it never prints a prompt or returns.

Press Ctrl+C to stop it. You normally do not run it by hand at all — put it in your client config and the client launches and speaks to it for you.

What is it built on, and can I inspect the source?

Each server is a Node.js application that requires Node.js 18 or newer, published to npm under the names shown on its package page (for example ai-cost-analyzer, data-aggregator-mcp, and seo-audit-tool).

Every package declares the MIT license. The published tarballs ship compiled JavaScript only — no TypeScript sources and no source maps — and the development repository is private, so you cannot read the original sources today.

What you can inspect before buying: the compiled package itself (npm view <package>, or unpack the tarball), the exact tool schemas documented on each package page, and the tools themselves through the no-key trial calls.

How does billing work, and can I cancel?

All current plans are monthly Stripe subscriptions. You can cancel one yourself from the billing and receipt links Stripe sends you, which stops future charges.

Cancelling does not switch off a key you already hold. Every key minted today carries a fixed 365-day expiry and verification is fully offline, so there is no revocation mechanism: the key keeps working until that expiry date regardless of subscription state. Renewals do not currently issue a new key either.

There is no separate published refund or money-back guarantee. For a specific billing question or refund request, email wasuppeople3@gmail.com.

Do you offer team or enterprise pricing?

Two servers publish named higher tiers. AI Cost Analyzer is sold as Indie ($29/mo), Team ($99/mo), and Enterprise ($299/mo); Security Scanner is sold as Personal ($19/mo), Team ($79/mo), and Enterprise ($499/mo).

The remaining servers use a simple Basic/Pro split, except Data Aggregator, which uses Free ($0), Pro ($16/mo), and Premium ($32/mo). Higher tiers remove the no-key limit the same way the entry plans do, and neither AI Cost Analyzer nor Security Scanner gates any tool by tier — so a Team or Enterprise key ships the same tools as the entry key.

The Enterprise tier is a price point, not a feature set. The packages contain no seat counting, no device binding, no SSO or SAML, no audit-log or SIEM export, and no service-level agreement. Anything beyond the shipped software would have to be agreed separately in writing.