HutchDB MCP (official, remote)
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
Vendor-hosted
Transport: Needs credentials to confirm transport · probed 2026-10-29 without credentials
Score 70/100 · Tools — · Token cost — · Compare · Last tested 2026-10-29 · Server version not reported · Remote endpoint https://app.hutchdb.com/api/mcp (streamable-http) · Repo ExpeditedProjects/hutchdb
Summary: HutchDB MCP (official, remote) requires credentials or a backing service before it will list tools.
Evidence summary
- Handshake
- auth-gated
- Tools listed
- —
- Context cost
- Not measured ranking
- Login
- Needs OAuth sign-in
- Tested
- 2026-10-29
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | Endpoint https://app.hutchdb.com/api/mcp reachable over streamable-http (HTTP 401) in 0.4s; no install step for remote servers. |
| handshake | auth-gated | 5 | Needs credentials: vendor-hosted, OAuth sign-in required. HTTP 401 with OAuth challenge (WWW-Authenticate resource_metadata https://app.hutchdb.com/.well-known/oauth-protected-resource; metadata lists authorization server https://app.hutchdb.com). We do not sign in; not counted as working until a credentialed test exists. |
| maintenance | pass | 25 | Repo pushed 0 days before test; 22 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 (vendor repo README (github.com/ExpeditedProjects/hutchdb)). |
| license | pass | 10 | AGPL-3.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-10-29
- Install from the registry (remote endpoint: connection only)
- We attempted an MCP initialize with no credentials and got HTTP 401, so we never reached the tool list (Method details:
initializePOST answered 401;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": "hutchdb-remote",
"version": null,
"registry": "remote",
"status": "auth-gated",
"tested": "2026-10-29",
"tools_count": null,
"tools_schema_tokens_est": null,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"Endpoint https://app.hutchdb.com/api/mcp reachable over streamable-http (HTTP 401) in 0.4s; no install step for remote servers."
],
"handshake": [
"auth-gated",
5,
"Needs credentials: vendor-hosted, OAuth sign-in required. HTTP 401 with OAuth challenge (WWW-Authenticate resource_metadata https://app.hutchdb.com/.well-known/oauth-protected-resource; metadata lists authorization server https://app.hutchdb.com). We do not sign in; not counted as working until a credentialed test exists."
],
"maintenance": [
"pass",
25,
"Repo pushed 0 days before test; 22 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 (vendor repo README (github.com/ExpeditedProjects/hutchdb))."
],
"license": [
"pass",
10,
"AGPL-3.0 (OSI-approved)."
]
}
}Install
https://app.hutchdb.com/api/mcp
Tools listed
Not available (handshake did not complete without credentials).
Quick config
{
"mcpServers": {
"hutchdb-mcp-official-remote": {
"type": "http",
"url": "https://app.hutchdb.com/api/mcp"
}
}
}Add to config Opens the config generator with this server selected.
Setup
Without credentials it said (verbatim): Needs credentials: vendor-hosted, OAuth sign-in required. HTTP 401 with OAuth challenge (WWW-Authenticate resource_metadata https://app.hutchdb.com/.well-known/oauth-protected-resource; metadata lists authorization server https://app.hutchdb.com). We do not sign in; not counted as working until a credentialed test exists.
- Install. No install step: it is a remote server at https://app.hutchdb.com/api/mcp.
- Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools. In our test it did not list tools without credentials.
{
"mcpServers": {
"hutchdb-mcp-official-remote": {
"type": "http",
"url": "https://app.hutchdb.com/api/mcp"
}
}
}Not tested with credentials We have not tested this with real credentials.
Test history
No dated events yet.
Related: MCP servers that need an OAuth sign-in · How to secure AI API keys
FAQ
Is HutchDB MCP (official, remote) deprecated?
No. hutchdb-remote was not deprecated or archived when we last tested it on 2026-10-29.
What replaces HutchDB MCP (official, remote)?
Nothing; HutchDB MCP (official, remote) is not deprecated as of 2026-10-29.
Does HutchDB MCP (official, remote) need an API key?
Not an API key: it needs an OAuth sign-in. Without signing in, the endpoint returned HTTP 401 with an OAuth challenge and did not list tools.
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.