com.neatlisting/neatlisting
NeatListing
Is the NeatListing MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-06.
Manage Google Business Profiles (Google My Business): hours, posts, photos, reviews and insights.
needs auth probed 2026-11-15 · unchanged since 2026-11-06 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"unauthorized","message":"Connect this MCP server (https://app.neatlisting.com/mcp); your MCP client - Endpoint
- https://app.neatlisting.com/mcp (streamable-http)
- Host
- app.neatlisting.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://app.neatlisting.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 app.neatlisting.com, PKCE S256, grants authorization_code, refresh_token.
Scopes listings.read listings.write.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/neatlisting/neatlisting
- Website
- https://neatlisting.com/setup
- Registry
- active, updated 2026-11-05 · registry entry
Compare this server with others.
More servers
Servers that mention business or insights.
- Business Contact Finder agency.ottobot/business-contact-finder · alive
- AdWeave — Meta Ads MCP Server ai.adweave/meta-ads-mcp · needs auth
- 1325.AI ai.1325/mcp · needs auth
- AI-Advisors ai.ai-advisors/mcp · needs auth
- ai.aivonic/mcp · alive
- ai.astrofabric/mcp · not found
- Atalay ai.atalay/mcp · needs auth
- Bezal — Local Business Intelligence for AI Agents ai.bezal/local-commerce · alive
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.