SparkVibeAI Spec Committee
REMOTE · API.SPARKVIBEAI.COM · SCANNED SEP 21
Commission a multi-model AI spec committee from your agent; get rubric-scored, build-ready specs.
Available components
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. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 141 tokens (~141/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · api.sparkvibeai.com
claude mcp add --transport http com-sparkvibeai-spec-committee 'https://api.sparkvibeai.com/mcp'
{
"mcpServers": {
"com-sparkvibeai-spec-committee": {
"url": "https://api.sparkvibeai.com/mcp"
}
}
} {
"servers": {
"com-sparkvibeai-spec-committee": {
"type": "http",
"url": "https://api.sparkvibeai.com/mcp"
}
}
} [mcp_servers.com-sparkvibeai-spec-committee] url = "https://api.sparkvibeai.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-sparkvibeai-spec-committee": {
"type": "remote",
"url": "https://api.sparkvibeai.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-sparkvibeai-spec-committee --url 'https://api.sparkvibeai.com/mcp' --transport streamable-http
mcp_servers:
com-sparkvibeai-spec-committee:
url: "https://api.sparkvibeai.com/mcp" {
"McpServers": {
"com-sparkvibeai-spec-committee": {
"Transport": "http",
"Url": "https://api.sparkvibeai.com/mcp"
}
}
} assistant mcp add com-sparkvibeai-spec-committee -t streamable-http -u 'https://api.sparkvibeai.com/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
- 10 Sept 26 +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.
- 8 Sept 26 +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.
- 5 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://api.sparkvibeai.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.sparkvibeai.com | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 14 May 2026 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | d2beb4d4387df6d279f78a6ea6b9e74 |
| SANs: api.sparkvibeai.com | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.sparkvibeai.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| sparkvibeai.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.sparkvibeai.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.sparkvibeai.com/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
sparkvibe.get_started How to get access to SparkVibeAI ~78
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.