# SparkVibeAI Spec Committee (remote · api.sparkvibeai.com)

Commission a multi-model AI spec committee from your agent; get rubric-scored, build-ready specs.

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `api.sparkvibeai.com`: 84/100 (this document), [markdown](https://verifymcp.io/servers/com-sparkvibeai-spec-committee/api.md), [page](https://verifymcp.io/servers/com-sparkvibeai-spec-committee/api)

## Channel facts

- Endpoint: `https://api.sparkvibeai.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-09-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 141 tokens (~141/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 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).
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the SparkVibeAI Spec Committee MCP server?

SparkVibeAI Spec Committee is a hosted endpoint at https://api.sparkvibeai.com/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 com-sparkvibeai-spec-committee 'https://api.sparkvibeai.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-sparkvibeai-spec-committee": {
      "url": "https://api.sparkvibeai.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-sparkvibeai-spec-committee": {
      "type": "http",
      "url": "https://api.sparkvibeai.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-sparkvibeai-spec-committee]
url = "https://api.sparkvibeai.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-sparkvibeai-spec-committee": {
      "type": "remote",
      "url": "https://api.sparkvibeai.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-sparkvibeai-spec-committee --url 'https://api.sparkvibeai.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-sparkvibeai-spec-committee:
    url: "https://api.sparkvibeai.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-sparkvibeai-spec-committee": {
      "Transport": "http",
      "Url": "https://api.sparkvibeai.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-sparkvibeai-spec-committee -t streamable-http -u 'https://api.sparkvibeai.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-sparkvibeai-spec-committee": {
      "type": "http",
      "url": "https://api.sparkvibeai.com/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-09-20 (score 84, +1)

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

### 2026-09-18 (score 83, +1)

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

### 2026-09-16 (score 82, +1)

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

### 2026-09-14 (score 81, +1)

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

### 2026-09-12 (score 80, +1)

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

### 2026-09-10 (score 79, +1)

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

### 2026-09-08 (score 78, +1)

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

### 2026-09-05 (score 77, +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.

## MCP tools (1)

### `sparkvibe.get_started` (~78 tokens)

How to get access to SparkVibeAI

Works WITHOUT a credential. Returns the preferred OAuth 2.1 connection flow, the Pro plan price and build-credit allowance, the agent-initiated checkout flow, the manual-key fallback, and a ready-to-relay message for your user. Call this when another tool returned UNAUTHORIZED / FEATURE_LOCKED or you need setup instructions.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-sparkvibeai-spec-committee/api#diagnostics

## Score history

- 2026-09-21: 84
- 2026-09-20: 84
- 2026-09-19: 83
- 2026-09-18: 83
- 2026-09-17: 82
- 2026-09-16: 82
- 2026-09-15: 81
- 2026-09-14: 81
- 2026-09-13: 80
- 2026-09-12: 80
- 2026-09-11: 79
- 2026-09-10: 79
- 2026-09-09: 78
- 2026-09-08: 78
- 2026-09-07: 77
- 2026-09-06: 77
- 2026-09-05: 77
- 2026-09-04: 76
- 2026-09-03: 76

## Common questions

### What is the SparkVibeAI Spec Committee MCP server?

SparkVibeAI Spec Committee is an MCP server listed in the public MCP registry as com.sparkvibeai/spec-committee. Commission a multi-model AI spec committee from your agent; get rubric-scored, build-ready specs. This page covers its hosted endpoint (https://api.sparkvibeai.com/mcp).

### Is the SparkVibeAI Spec Committee MCP server safe to use?

SparkVibeAI Spec Committee scores 84 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 SparkVibeAI Spec Committee MCP server expose?

SparkVibeAI Spec Committee exposes 1 tool: sparkvibe.get_started. Their descriptions and schemas cost roughly 78 tokens of context every time the server is loaded.

### Does the SparkVibeAI Spec Committee MCP server require authentication?

Yes. SparkVibeAI Spec Committee asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the SparkVibeAI Spec Committee MCP server still maintained?

SparkVibeAI Spec Committee is still listed as active in the MCP registry. We last reached this channel on 21 September 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://api.sparkvibeai.com/mcp
- Website: https://sparkvibeai.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-sparkvibeai-spec-committee/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-sparkvibeai-spec-committee/api.json
- HTML version of this page: https://verifymcp.io/servers/com-sparkvibeai-spec-committee/api