Weekly Report Checker MCP Server

Created By
kaneyxxa year ago
An MCP server that checks weekly report submissions in a Google Sheet
Overview

What is Weekly Report Checker MCP Server?

The Weekly Report Checker MCP Server is an MCP (Model Context Protocol) server designed to check weekly report submissions in a Google Sheet.

How to use Weekly Report Checker MCP Server?

To use the server, install the package and run it in development mode or directly using Python. Ensure you have the necessary prerequisites, including Python 3.10 or higher and a Google Sheets service account JSON file.

Key features of Weekly Report Checker MCP Server?

  • Checks who hasn't submitted their weekly reports.
  • Provides detailed information about a specific person's report status.
  • Displays submission statistics.
  • Lists all team members who should submit reports.

Use cases of Weekly Report Checker MCP Server?

  1. Monitoring weekly report submissions in a team.
  2. Identifying team members who are lagging in report submissions.
  3. Analyzing submission statistics for performance reviews.

FAQ from Weekly Report Checker MCP Server?

  • What are the prerequisites for using the server?

You need Python 3.10 or higher and a Google Sheets service account JSON file.

  • How do I install the Weekly Report Checker MCP Server?

You can install it using pip and run the installation script provided in the documentation.

  • Can I run the server directly?

Yes, you can run the server directly using Python or through the provided command.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kaneyxx
Star
0
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

32 minutes ago