Aiven MCP (official)
Capped at 70: no passing tool call yet; the tests add up to 75. Why scores are capped
Test points add up to 75; the score is capped at 70 until a tool call passes. Not a quality or security rating. Methodology
Test points before the cap (75/100)
- Install20/20
- Handshake5/30
- Maintenance25/25
- Docs15/15
- License10/10
Tested npm mcp-aiven 1.18.1 (repo Aiven-Open/mcp-aiven). Without credentials it exits: 'Fatal error: AIVEN_TOKEN environment variable is required.' Not tested with a token.
Transport (tested 2026-11-01): stdio
Score 70/100 · Tools — · Token cost — · Compare · Last tested 2026-11-01 · Version tested 1.18.1 · Package mcp-aiven · Repo Aiven-Open/mcp-aiven
Summary: Aiven MCP (official) requires credentials or a backing service before it will list tools.
Evidence summary
- Handshake
- auth-gated
- Tools listed
- —
- Context cost
- Not measured ranking
- API key
- Needs a key
- Tested
- 2026-11-01
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install mcp-aiven (Node 20, Linux) succeeded in 3s. |
| handshake | auth-gated | 5 | Auth-gated: without credentials the server only printed a missing-credential message and did not list tools ("… mcp-aiven: Fatal error: AIVEN_TOKEN environment variable is required. Get your token from: https://console.aiven.io/profile/auth …"). Not tested with real credentials; not counted as working. |
| maintenance | pass | 25 | Repo pushed 0 days before test; 28 GitHub stars. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Automated check of the package's own README (README shipped in npm package). |
| license | pass | 10 | Apache-2.0 (OSI-approved). |
Local-model readiness
Not yet tested (no tools/list response without credentials).
What we tested and what we didn't
Tested on 2026-11-01
- Install from the registry
- We attempted an MCP initialize with no credentials; it stopped at a credential check, so we never reached the tool list (Method details:
initializedid not complete;tools/listnot sent) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that it is safe to give it access to your data.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
No tool list: this server did not list tools without credentials in our test, so tool changes are not tracked.
Raw test record (JSON)
{
"name": "mcp-aiven",
"version": "1.18.1",
"registry": "npm",
"status": "auth-gated",
"tested": "2026-11-01",
"tools_count": null,
"tools_schema_tokens_est": null,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`npm install mcp-aiven` (Node 20, Linux) succeeded in 3s."
],
"handshake": [
"auth-gated",
5,
"Auth-gated: without credentials the server only printed a missing-credential message and did not list tools (\"\u2026 mcp-aiven: Fatal error: AIVEN_TOKEN environment variable is required. Get your token from: https://console.aiven.io/profile/auth \u2026\"). Not tested with real credentials; not counted as working."
],
"maintenance": [
"pass",
25,
"Repo pushed 0 days before test; 28 GitHub stars."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Automated check of the package's own README (README shipped in npm package)."
],
"license": [
"pass",
10,
"Apache-2.0 (OSI-approved)."
]
}
}Install
npx -y mcp-aiven
Tools listed
Not available (handshake did not complete without credentials).
Quick config
{
"mcpServers": {
"aiven-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-aiven"
],
"env": {
"AIVEN_TOKEN": "<your key>"
}
}
}
}API key: set AIVEN_TOKEN in env (replace <your key>). Our handshake ran without it; real use needs it.
Add to config Opens the config generator with this server selected.
Setup
Without credentials it said (verbatim): … mcp-aiven: Fatal error: AIVEN_TOKEN environment variable is required. Get your token from: https://console.aiven.io/profile/auth …
Env var seen in our test: AIVEN_TOKEN
- Install. Run
npm install mcp-aiven(Node 20). This is the exact command we ran on 2026-11-01. - Configure. Add the mcpServers entry below to your MCP client config and set AIVEN_TOKEN.
- Verify. Restart the client and check that tools/list returns tools. In our test it did not list tools without credentials.
{
"mcpServers": {
"aiven-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-aiven"
],
"env": {
"AIVEN_TOKEN": "<your key>"
}
}
}
}Not tested with credentials We have not tested this with real credentials.
Test history
No dated events yet.
Related: MCP servers that need an API key · How to secure AI API keys
FAQ
Is Aiven MCP (official) deprecated?
No. mcp-aiven was not deprecated or archived when we last tested it on 2026-11-01.
What replaces Aiven MCP (official)?
Nothing; Aiven MCP (official) is not deprecated as of 2026-11-01.
Does Aiven MCP (official) need an API key?
Yes. Without credentials it only printed a missing-credential message and did not list tools (auth-gated).
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.