com.onegoodarea/oga-mcp
com.onegoodarea/oga-mcp
Is the com.onegoodarea/oga-mcp MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-04.
Sourced facts, explained scores and change alerts for every GB neighbourhood, from one API.
needs auth probed 2026-11-15 · unchanged since 2026-11-04 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"Missing credentials. Send Authorization: Bearer oga_... (an API key) or connect through OAuth."}- Endpoint
- https://api.onegoodarea.com/mcp (streamable-http)
- Host
- api.onegoodarea.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://api.onegoodarea.com/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server api.onegoodarea.com, PKCE S256, grants authorization_code, refresh_token.
Scopes mcp.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://www.onegoodarea.com/docs/mcp
- Registry
- active, updated 2026-11-03 · registry entry
- Changes
- 2 recorded, reachable in 1 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Servers that mention neighbourhood or explained.
- HoodEx app.hoodex/hoodex · needs auth
- CaptureOneAI Web Perception com.captureoneai/web-perception · alive
- CVElens Vulnerability Intelligence com.cvelens/cvelens · TLS error
- Dogechain com.dogechain/dogechain · alive
- Simma com.getsimma/simma · needs auth
- Yatmo neighbourhood data for real estate com.yatmo/yatmo · needs auth
- Voxhouses (Portugal) eu.voxs/voxhouses-pt · alive
- Vigi-Sky fr.vigi-sky/vigisky · alive
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-10-23 09:42 | needs auth | ||||
| 2026-10-16 06:23 | needs env |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.