# Alphamotion (remote · alphamotion.in)

Digital, ecommerce, operations, compliance and finance for brands in India.

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `alphamotion.in`: 69/100 (this document), [markdown](https://verifymcp.io/servers/in-alphamotion-alphamotion/alphamotion.md), [page](https://verifymcp.io/servers/in-alphamotion-alphamotion/alphamotion)

## Channel facts

- Endpoint: `https://alphamotion.in/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-11-05.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 328 tokens (~109/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Alphamotion MCP server?

Alphamotion is a hosted endpoint at https://alphamotion.in/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http in-alphamotion-alphamotion 'https://alphamotion.in/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "in-alphamotion-alphamotion": {
      "url": "https://alphamotion.in/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "in-alphamotion-alphamotion": {
      "type": "http",
      "url": "https://alphamotion.in/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.in-alphamotion-alphamotion]
url = "https://alphamotion.in/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "in-alphamotion-alphamotion": {
      "type": "remote",
      "url": "https://alphamotion.in/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add in-alphamotion-alphamotion --url 'https://alphamotion.in/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  in-alphamotion-alphamotion:
    url: "https://alphamotion.in/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "in-alphamotion-alphamotion": {
      "Transport": "http",
      "Url": "https://alphamotion.in/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add in-alphamotion-alphamotion -t streamable-http -u 'https://alphamotion.in/mcp'
```

### Other

```json
{
  "mcpServers": {
    "in-alphamotion-alphamotion": {
      "type": "http",
      "url": "https://alphamotion.in/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-04 (score 69, +1)

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

### 2026-11-02 (score 68, +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-10-31 (score 67, +1)

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

### 2026-10-29 (score 66, +1)

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

### 2026-10-27 (score 65, +1)

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

### 2026-10-26 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-25 (score 64)

First indexed and scored.

## MCP tools (3)

### `list_services` (~57 tokens)

List the services Alphamotion (Mumbai, India) publishes on alphamotion.in: digital marketing, websites and ecommerce stores, marketplaces, operations, compliance and finance, with a summary and the page to read, plus the three published prices.

### `recommend_services` (~76 tokens)

Recommend the Alphamotion services that fit a business need, such as a website or ecommerce store, marketing, marketplace management, or operations in India. Returns the best matches with their pages. Only three services carry a published price; everything else is quoted to the work.

Input parameters:

- `need` (string, required): The user's need in their own words.

### `request_contact` (~135 tokens)

Ask Alphamotion to get in touch on the user's behalf. Only use this when the user has agreed to share these details with Alphamotion, and set user_consented to true. Nothing is booked, priced or agreed by this request.

Input parameters:

- `company` (string)
- `email` (string, required)
- `name` (string, required)
- `need` (string, required): What the user wants help with (at least a sentence).
- `phone` (string)
- `service` (string): Optional service id from list_services.
- `user_consented` (boolean, required): True only if the user agreed to share these details.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/in-alphamotion-alphamotion/alphamotion#diagnostics

## Score history

- 2026-11-05: 69
- 2026-11-04: 69
- 2026-11-03: 68
- 2026-11-02: 68
- 2026-11-01: 67
- 2026-10-31: 67
- 2026-10-30: 66
- 2026-10-29: 66
- 2026-10-28: 65
- 2026-10-27: 65
- 2026-10-26: 64
- 2026-10-25: 64

## Common questions

### What is the Alphamotion MCP server?

Alphamotion is an MCP server listed in the public MCP registry as in.alphamotion/alphamotion. Digital, ecommerce, operations, compliance and finance for brands in India. This page covers its hosted endpoint (https://alphamotion.in/mcp).

### Is the Alphamotion MCP server safe to use?

Alphamotion scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Alphamotion MCP server expose?

Alphamotion exposes 3 tools: list_services, recommend_services, request_contact. Their descriptions and schemas cost roughly 268 tokens of context every time the server is loaded.

### Does the Alphamotion MCP server require authentication?

No. We connected to Alphamotion without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Alphamotion MCP server still maintained?

Alphamotion is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://alphamotion.in/mcp
- Website: https://alphamotion.in/
- Changelog RSS feed: https://verifymcp.io/servers/in-alphamotion-alphamotion/alphamotion.xml
- Changelog JSON feed: https://verifymcp.io/servers/in-alphamotion-alphamotion/alphamotion.json
- HTML version of this page: https://verifymcp.io/servers/in-alphamotion-alphamotion/alphamotion