Algolia Productivity MCP (official, remote)
Score = points from 5 automated checks. Not a quality or security rating. Methodology
- Install20/20
- Handshake5/30
- Maintenance25/25
- Docs15/15
- License0/10
Vendor-hosted
Official Algolia hosted MCP (Productivity MCP), listed under the vendor-hosted rule. Maintenance date comes from the docs page metadata (schema.org dateModified), not a changelog. Algolia also runs Public MCP (per-application URL) and DevEx MCP; not tested.
Maintenance date 2026-10-05: date from page metadata (schema.org dateModified 2026-10-05T12:37:59.000Z (WebPage and TechArticle JSON-LD)) of https://www.algolia.com/doc/guides/model-context-protocol/productivity-mcp, fetched 2026-10-28. Not a changelog entry.
Sources: https://www.algolia.com/doc/guides/model-context-protocol/productivity-mcp
Transport: Needs credentials to confirm transport · probed 2026-10-28 without credentials
Score 65/100 · Tools — · Token cost — · Compare · Last tested 2026-10-28 · Server version not reported · Remote endpoint https://mcp.algolia.com/mcp (streamable-http)
Summary: Algolia Productivity 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-28
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | Endpoint https://mcp.algolia.com/mcp reachable over streamable-http (HTTP 401) in 0.2s; 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://mcp.algolia.com/.well-known/oauth-protected-resource; metadata lists authorization server https://dashboard.algolia.com). We do not sign in; not counted as working until a credentialed test exists. |
| maintenance | pass | 25 | Vendor-hosted rule: scored from vendor docs page 2026-10-05, date from page metadata (schema.org dateModified 2026-10-05T12:37:59.000Z (WebPage and TechArticle JSON-LD), fetched 2026-10-28) (https://www.algolia.com/doc/guides/model-context-protocol/productivity-mcp), 23 days before test. Registry: Not used for scoring (maintenance comes from the vendor page metadata date). For reference, the official MCP registry lists io.github.algolia/algolia-productivity with remote https://mcp.algolia.com/mcp (newest seen 1.28.0, published 2026-10-27; checked 2026-10-28). |
| docs | pass | 15 | official MCP docs page; states the endpoint URL; client setup instructions. Vendor-hosted rule: scored from the vendor's official MCP docs (https://www.algolia.com/doc/guides/model-context-protocol/productivity-mcp). |
| license | fail | 0 | Vendor-hosted service with no public repo: no license to cite, so 0 (rule: no points without a cited source). |
Local-model readiness
Not yet tested (no tools/list response without credentials).
What we tested and what we didn't
Tested on 2026-10-28
- We attempted an MCP initialize to the vendor's hosted endpoint with no credentials and got HTTP 401, so we never reached the tool list (Method details:
initializePOST answered 401;tools/listnot sent) - Auth response: HTTP 401, WWW-Authenticate resource_metadata https://mcp.algolia.com/.well-known/oauth-protected-resource, OAuth metadata lists authorization server https://dashboard.algolia.com. Login is an OAuth sign-in; we did not sign in
- Vendor docs: official MCP docs page; states the endpoint URL; client setup instructions (15/15)
- Maintenance: dated vendor source, vendor docs page (date from page metadata) 2026-10-05 (25/25)
- License: a hosted service has no license to cite (0/10)
Not tested
- Security: not audited (hosted service; no code to review, no permission or data-flow analysis)
- Behaviour after signing in, or with a real account
- Source code, repository activity or an open-source license (none published for the hosted service)
- Performance, rate limits or load
- Real tasks (no functional task runs yet)
Methodology: how we test (vendor-hosted rule). A high score means it responds and its vendor documents and dates it, 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": "algolia-remote",
"version": null,
"registry": "remote",
"status": "auth-gated",
"tested": "2026-10-28",
"tools_count": null,
"tools_schema_tokens_est": null,
"deprecated": false,
"archived": null,
"tests": {
"install": [
"pass",
20,
"Endpoint https://mcp.algolia.com/mcp reachable over streamable-http (HTTP 401) in 0.2s; 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://mcp.algolia.com/.well-known/oauth-protected-resource; metadata lists authorization server https://dashboard.algolia.com). We do not sign in; not counted as working until a credentialed test exists."
],
"maintenance": [
"pass",
25,
"Vendor-hosted rule: scored from vendor docs page 2026-10-05, date from page metadata (schema.org dateModified 2026-10-05T12:37:59.000Z (WebPage and TechArticle JSON-LD), fetched 2026-10-28) (https://www.algolia.com/doc/guides/model-context-protocol/productivity-mcp), 23 days before test. Registry: Not used for scoring (maintenance comes from the vendor page metadata date). For reference, the official MCP registry lists io.github.algolia/algolia-productivity with remote https://mcp.algolia.com/mcp (newest seen 1.28.0, published 2026-10-27; checked 2026-10-28)."
],
"docs": [
"pass",
15,
"official MCP docs page; states the endpoint URL; client setup instructions. Vendor-hosted rule: scored from the vendor's official MCP docs (https://www.algolia.com/doc/guides/model-context-protocol/productivity-mcp)."
],
"license": [
"fail",
0,
"Vendor-hosted service with no public repo: no license to cite, so 0 (rule: no points without a cited source)."
]
}
}Install
https://mcp.algolia.com/mcp
Tools listed
Not available (handshake did not complete without credentials).
Quick config
{
"mcpServers": {
"algolia-productivity-mcp-official-remote": {
"type": "http",
"url": "https://mcp.algolia.com/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://mcp.algolia.com/.well-known/oauth-protected-resource; metadata lists authorization server https://dashboard.algolia.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://mcp.algolia.com/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": {
"algolia-productivity-mcp-official-remote": {
"type": "http",
"url": "https://mcp.algolia.com/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 Algolia Productivity MCP (official, remote) deprecated?
No. algolia-remote was not deprecated or archived when we last tested it on 2026-10-28.
What replaces Algolia Productivity MCP (official, remote)?
Nothing; Algolia Productivity MCP (official, remote) is not deprecated as of 2026-10-28.
Does Algolia Productivity 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.