🤖 AsyncPraiseRebuke MCP Server

Created By
fabianwilliamsa year ago
MCP Server to get access to Reviews that are posted using the Async Praise Rebuke App
Overview

What is AsyncPraiseRebuke MCP?

AsyncPraiseRebuke MCP is a Model Context Protocol (MCP) server designed to provide access to customer reviews and business contact discovery tools, integrating seamlessly with Claude Desktop or any MCP-compliant client.

How to use AsyncPraiseRebuke MCP?

To use AsyncPraiseRebuke MCP, install it via npm and configure it in your Claude Desktop setup. You can also run it manually to scan and log new business emails.

Key features of AsyncPraiseRebuke MCP?

  • List and search customer feedback reviews
  • View top-rated and lowest-rated establishments
  • Discover business contact emails using scraping and heuristics
  • Log new entries to a Cosmos DB-based directory
  • Automate multi-step flows with agent-based tools

Use cases of AsyncPraiseRebuke MCP?

  1. Analyzing customer feedback for business improvement
  2. Discovering contact information for marketing outreach
  3. Automating the logging of business emails to a directory

FAQ from AsyncPraiseRebuke MCP?

  • Can AsyncPraiseRebuke MCP be used with any MCP-compliant client?

Yes! It is designed to work with any MCP-compliant client, including Claude Desktop.

  • Is AsyncPraiseRebuke MCP free to use?

The project is open-source and can be used freely under the MIT license.

  • How do I log new business emails?

You can use the discoverAndLogBusinessEmail agent tool to automate the process of discovering and logging new business emails.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
fabianwilliams
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago