# Anythink all-in-one backend: data, auth, files, workflows, payments, APIs (nuget · anythink-mcp)

Sick of stitched-together services? Anythink is the all-in-one backend, configured with AI.

- Trust score: 69/100 (medium)
- Change this week: −12
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- nuget · `anythink-mcp`: 69/100 (this document), [markdown](https://verifymcp.io/servers/cloud-anythink-anythink/anythink-mcp.md), [page](https://verifymcp.io/servers/cloud-anythink-anythink/anythink-mcp)

## Channel facts

- Registry: `nuget`
- Package: `anythink-mcp`
- Version: `0.2.21`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 35 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2151 tokens (~134/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add cloud-anythink-anythink -- dnx anythink-mcp@0.2.21 --yes
```

### Codex

```bash
codex mcp add cloud-anythink-anythink -- dnx anythink-mcp@0.2.21 --yes
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloud-anythink-anythink": {
      "type": "local",
      "command": [
        "dnx",
        "anythink-mcp@0.2.21",
        "--yes"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  cloud-anythink-anythink:
    command: "dnx"
    args: ["anythink-mcp@0.2.21", "--yes"]
```

### Other

```json
{
  "mcpServers": {
    "cloud-anythink-anythink": {
      "command": "dnx",
      "args": [
        "anythink-mcp@0.2.21",
        "--yes"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 69, +1)

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

### 2026-08-02 (score 68, +18)

- [security improvement] Malware scan: unverified → pass
- [functional improvement] Stability: unverified → 0.23

### 2026-08-01 (score 50, −13)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 63, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-27 (score 81, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 81)

First indexed and scored.

## MCP tools (16)

### `config_use` (~103 tokens)

Switch the active project profile that the 'cli' tool's commands operate against. Use this to move between already-connected projects without re-authenticating. The profile must already exist (created by 'projects_use' or 'login_direct'); run 'config_show' to see available profile names. Returns confirmation, or an error if the profile does not exist.

Input parameters:

- `profile` (string, required): Name of an existing profile to make active. See 'config_show' for valid names.

### `projects_delete` (~143 tokens)

Permanently delete a project and tear down its backend instance, including its database and stored data. This is destructive and irreversible — always confirm with the user first, and prefer matching by a specific id over a short prefix to avoid removing the wrong project. Requires an active billing account (set one with 'accounts_use'). Returns the deleted project's name and id on success.

Input parameters:

- `accountId` (string): Billing account id the project belongs to. Defaults to the active account set via 'accounts_use'.
- `id` (string, required): Project to delete — its UUID, name, or a unique prefix. Use a specific id to avoid accidental matches. Find ids via 'projects_list'.

### `login_direct` (~101 tokens)

Store credentials directly for a project (bypasses billing login). Use this when you already have an org ID and API key or JWT token.

Input parameters:

- `apiKey` (string): API key (ak_...)
- `baseUrl` (string): Override API base URL
- `orgId` (string, required): Organization/tenant ID
- `profile` (string): Profile name to save as (defaults to org ID)
- `token` (string): JWT access token

### `projects_use` (~193 tokens)

Connect to a project and save it as the active profile so the 'cli' tool's data, entities, users, and other commands target it. Resolves the project, then either stores the API key you pass or exchanges a transfer token for project-scoped credentials automatically. Requires an active billing account (set one with 'accounts_use'); the project must be Active (see 'projects_list'). Returns the saved profile name, org id, API URL, and auth method.

Input parameters:

- `accountId` (string): Billing account id the project belongs to. Defaults to the active account set via 'accounts_use'.
- `apiKey` (string): Optional project API key (ak_...). If omitted, a project-scoped token is generated automatically via transfer-token exchange.
- `id` (string, required): Project to connect to — its name, org id, or UUID (a unique prefix is accepted). Find these via 'projects_list'.

### `logout` (~101 tokens)

Remove the saved credentials for a project profile from local CLI config. Use this to disconnect from a project or clear a stale token; it deletes only the stored profile locally and does not revoke the token server-side or affect the project. Omit the profile to remove the currently active one. Run 'config_show' to see profile names.

Input parameters:

- `profile` (string): Name of the profile to remove. Defaults to the active profile. See 'config_show' for names.

### `signup` (~184 tokens)

Register a brand-new Anythink platform account with email and password. Use this only when the user has no account yet; if they already have one, use 'login' instead. This creates the top-level user identity — it does not create a billing account or project (do that with 'accounts_create' and 'projects_create' after logging in). On success the user may need to click an email confirmation link before 'login' works; tell them to confirm, then call 'login'.

Input parameters:

- `email` (string, required): Email address — becomes the login identifier and must be unique
- `firstName` (string, required): User's first name
- `lastName` (string, required): User's last name
- `password` (string, required): Password for the new account; choose a strong value
- `referralCode` (string): Optional referral code, if the user was invited by another customer

### `accounts_create` (~171 tokens)

Create a new billing account (organization) to hold projects and payment details. Requires a prior platform login (use the 'login' tool first). The new account is automatically set as the active account, so subsequent 'projects_create' / 'projects_list' calls target it without further setup. Returns the new account's id and name. Most users need only one account — call 'accounts_list' first to check whether a suitable one already exists.

Input parameters:

- `currency` (string): ISO currency for billing: 'gbp', 'usd', or 'eur'. Defaults to 'gbp'. Cannot be changed later.
- `email` (string, required): Billing email address that receives invoices and receipts
- `name` (string, required): Organization name, e.g. 'Acme Inc' — shown on invoices and in the dashboard

### `config_remove` (~95 tokens)

Delete a saved project profile from the local CLI configuration. Removes only the locally stored credentials and settings — it does not delete the project or revoke tokens server-side (to remove the project itself, use 'projects_delete'). Run 'config_show' to see profile names. Returns confirmation, or a not-found message.

Input parameters:

- `profile` (string, required): Name of the profile to remove from local config. See 'config_show' for valid names.

### `projects_list` (~123 tokens)

List the projects (provisioned backend instances) in a billing account. Requires platform login and an active billing account (set one with 'accounts_use'). Returns each project's id, name, description, region, org id, status (Initializing/Provisioning/Active/Suspended/Terminated/Error), API URL, and creation date. Use this to find a project's id before connecting with 'projects_use' or removing it with 'projects_delete'.

Input parameters:

- `accountId` (string): Billing account id to list projects for. Defaults to the active account set via 'accounts_use'.

### `login` (~60 tokens)

Log in to the Anythink platform with email and password. Returns a session token used for account and project management. For Google sign-in, use the 'login_google' tool.

Input parameters:

- `email` (string, required): Email address
- `password` (string, required): Password

### `accounts_use` (~111 tokens)

Set the active billing account that project commands operate on. Call this after 'login' when you belong to more than one account, before using 'projects_list', 'projects_create', or 'projects_use'. Accepts a full account UUID or a unique prefix; run 'accounts_list' to see valid ids. Returns the resolved account name and id, or an error if no account matches.

Input parameters:

- `id` (string, required): Billing account id — full UUID or a unique leading prefix. Get ids from 'accounts_list'.

### `login_google` (~110 tokens)

Sign in to the Anythink platform with Google. Opens the user's browser to Google's consent screen and waits for them to approve, then stores the session token. The browser step must be completed by the user; everything before and after is tool-driven. This does NOT pick a billing account or project — after it returns, call 'accounts_list' then 'accounts_use', and 'projects_list' then 'projects_use'. Needs a local browser, so it only works over stdio (not the hosted HTTP server).

### `cli` (~221 tokens)

Run any Anythink CLI command and return its output. Use this for commands not covered by dedicated tools (entities, fields, data, workflows, roles, menus, secrets, users, files, pay, oauth, migrate, fetch, api, docs, etc.). Pass the command exactly as you would after 'anythink', e.g. 'entities list' or 'data list posts'. Menu commands: 'menus list' shows dashboard menus with tree structure; 'menus add-item <menu_id> <entity> --icon <Icon> --parent <parent_id>' adds an entity to a dashboard menu. For destructive commands add '--yes' to skip confirmation prompts. Add '--json' where supported for machine-readable output.

Input parameters:

- `command` (string, required): CLI arguments after 'anythink', e.g. 'entities list', 'users me', 'data list blog_posts --json', 'migrate --from a --to b --dry-run', 'fetch /some/path'. Do NOT include 'anythink' itself or '--profil…

### `accounts_list` (~90 tokens)

List the billing accounts (organizations) the logged-in user belongs to. Requires a prior platform login (use the 'login' tool first). Returns each account's id, organization name, billing email, currency, and status (Active/Suspended/Canceled), and flags which one is currently active. A billing account holds your projects and payment details — pick one with 'accounts_use' before creating or listing projects.

### `projects_create` (~234 tokens)

Provision a new project — a dedicated, isolated Anythink backend instance with its own database, API, auth, and storage. Requires platform login and an active billing account (set one with 'accounts_use'). Provisioning runs asynchronously: the project starts in a Provisioning state, so poll 'projects_list' until it is Active. Returns the new project's id, name, org id, and API URL. Connect to it with 'projects_use'.

Input parameters:

- `accountId` (string): Billing account id to create the project in. Defaults to the active account set via 'accounts_use'.
- `description` (string): Optional free-text description shown in the dashboard
- `name` (string, required): Human-readable project name, e.g. 'production' or 'my-app'
- `planId` (string, required): Plan id (UUID) that sets the project's resource tier and pricing. Run the 'plans' CLI command (via the 'cli' tool) to list available plan ids.
- `region` (string): Deployment region slug, e.g. 'lon1'. Defaults to 'lon1'. Choose the region closest to your users.

### `config_show` (~111 tokens)

Show the local CLI configuration: all saved project profiles and platform logins, and which of each is active. For every profile it returns the name, org id, auth method (api-key or token), alias, and platform; for every platform it returns the URLs, billing account, and login status. Use this to discover profile names for 'config_use', 'config_remove', or 'logout', and to check which project the 'cli' tool currently targets. Reads local config only — makes no network calls.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloud-anythink-anythink/anythink-mcp#diagnostics

## Score history

- 2026-08-03: 69
- 2026-08-02: 68
- 2026-08-01: 50
- 2026-07-31: 63
- 2026-07-29: 81
- 2026-07-28: 81
- 2026-07-27: 81
- 2026-07-26: 81

## Links

- NuGet package: https://www.nuget.org/packages/anythink-mcp
- Socket report: https://socket.dev/nuget/package/anythink-mcp
- Repository: https://github.com/anythink-cloud/anythink-cli
- Website: https://anythink.cloud/
- Changelog RSS feed: https://verifymcp.io/servers/cloud-anythink-anythink/anythink-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloud-anythink-anythink/anythink-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/cloud-anythink-anythink/anythink-mcp