Waitlister MCP (official, remote)
Capped at 65: vendor-hosted, source not published. The tests add up to 65.
Test points add up to 65; the score is capped at 65 (vendor-hosted, source not published). Not a quality or security rating. Capped listings are not promoted in our rankings or on the homepage. Why scores are capped
Test points before the cap (65/100)
- Install20/20
- Handshake5/30
- Maintenance25/25
- Docs15/15
- License0/10
Vendor-hosted
What we probed (2026-11-18 UTC, no credentials): an MCP initialize POST to https://mcp.waitlister.me/mcp returned HTTP 401 with an OAuth challenge (scope 'read write'; resource_metadata https://mcp.waitlister.me/.well-known/oauth-protected-resource/mcp; authorization server https://mcp.waitlister.me, authorization code + PKCE S256, public clients, client ID metadata documents supported). We did not sign in, so no tools were listed or called. Waitlister's docs describe what the connector can view and change but publish no tool names, so tool count and schema size are unknown. Not the older local npm server @waitlister/mcp (API key). Vendor-hosted, no public source: 65 cap, not source-audited, core tools not tested.
Waitlister-hosted endpoint. Initialize returned HTTP 401 with an OAuth challenge (scope 'read write'; resource metadata lists https://mcp.waitlister.me as the authorization server). We did not sign in, so no tools were listed or called. Source isn't public: vendor-hosted 65 cap (Our review, Nov 17, 2026 UTC).
Maintenance date 2026-11-15 UTC: date from page metadata (sitemap.xml <lastmod>2026-11-15 UTC</lastmod> for https://waitlister.me/docs/mcp) of https://waitlister.me/docs/mcp, fetched 2026-11-18T04:12Z. Not a changelog entry.
Sources: https://waitlister.me/docs/mcp
Transport: Streamable HTTP · not tested
Token cost (estimate): the figure is pending. We have no tools/list capture to estimate from.
Permissions: tool permissions pending · Auth: OAuth · Rate limit: unknown · Pricing unit: unknown
Auth: OAuth. Rate limit: unknown. Pricing unit: unknown.
HTTP 401, WWW-Authenticate resource_metadata https://mcp.waitlister.me/.well-known/oauth-protected-resource/mcp, OAuth metadata lists authorization server https://mcp.waitlister.me
Score 65/100 · Tools 0 · Token cost pending · Compare · Last tested 2026-11-18 UTC · Server version not reported · Remote endpoint https://mcp.waitlister.me/mcp (streamable-http)
Summary: Waitlister MCP (official, remote) requires credentials or a backing service before it will list tools.
Evidence summary
- Handshake
- auth-gated
- Tools listed
- 0
- Context cost
- Pending The token cost figure is pending. ranking
- Login
- Needs OAuth sign-in
- Tested
- 2026-11-18 UTC
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | Endpoint https://mcp.waitlister.me/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://mcp.waitlister.me/.well-known/oauth-protected-resource/mcp; metadata lists authorization server https://mcp.waitlister.me). 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-11-15 UTC, date from page metadata (sitemap.xml <lastmod>2026-11-15 UTC</lastmod> for https://waitlister.me/docs/mcp, fetched 2026-11-18T04:12Z) (https://waitlister.me/docs/mcp), 3 days before test. Registry: hosted connector not found in the official MCP registry pass of 2026-11-17 UTC (the older local npm server @waitlister/mcp is a separate, API-key product) |
| 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://waitlister.me/docs/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 tested
Not yet tested (no tools/list response without credentials).
What we tested and what we didn't
Tested on 2026-11-18 UTC
- 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.waitlister.me/.well-known/oauth-protected-resource/mcp, OAuth metadata lists authorization server https://mcp.waitlister.me. 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-11-15 UTC (25/25)
- License: a hosted service has no license to cite (0/10)
- Token cost (estimate)
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 giving it access to your data carries no risk.
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": "waitlister-remote",
"version": null,
"registry": "remote",
"status": "auth-gated",
"tested": "2026-11-18",
"tools_count": null,
"deprecated": false,
"archived": null,
"tests": {
"install": [
"pass",
20,
"Endpoint https://mcp.waitlister.me/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://mcp.waitlister.me/.well-known/oauth-protected-resource/mcp; metadata lists authorization server https://mcp.waitlister.me). 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-11-15, date from page metadata (sitemap.xml <lastmod>2026-11-15</lastmod> for https://waitlister.me/docs/mcp, fetched 2026-11-18T04:12Z) (https://waitlister.me/docs/mcp), 3 days before test. Registry: hosted connector not found in the official MCP registry pass of 2026-11-17 (the older local npm server @waitlister/mcp is a separate, API-key product)"
],
"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://waitlister.me/docs/mcp)."
],
"license": [
"fail",
0,
"Vendor-hosted service with no public repo: no license to cite, so 0 (rule: no points without a cited source)."
]
},
"testedAt": "2026-11-18T03:36:20.821Z"
}Install
https://mcp.waitlister.me/mcp
Tools listed
Not available (handshake did not complete without credentials).
Quick config
{
"mcpServers": {
"waitlister-mcp-remote": {
"type": "http",
"url": "https://mcp.waitlister.me/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.waitlister.me/.well-known/oauth-protected-resource/mcp; metadata lists authorization server https://mcp.waitlister.me). 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.waitlister.me/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": {
"waitlister-mcp-remote": {
"type": "http",
"url": "https://mcp.waitlister.me/mcp"
}
}
}Not tested with credentials We have not tested this with real credentials.
Test history
- 2026-11-18 UTC: New
Related: Troubleshooting: 401 Unauthorized on remote servers · MCP servers that need an OAuth sign-in · How to protect AI API keys
FAQ
Is Waitlister MCP deprecated?
No. Waitlister MCP was not deprecated or archived when we last tested it on 2026-11-18 UTC.
What replaces Waitlister MCP?
Nothing; Waitlister MCP (official, remote) is not deprecated as of 2026-11-18 UTC.
Does Waitlister MCP 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.