A web application for curated news about MCP servers, clients, protocol updates and everything else MCP. Includes Firebase Cloud Functions for RSS generation, image processing, metadata management, and Algolia search integration.
This is NOT an MCP server. The codebase is a Firebase Cloud Functions backend + Next.js web frontend for a Web3 scam tracker. Tools are Firebase function exports, not MCP tool definitions. No MCP protocol implementation detected. Tool definitions lack proper schemas, parameter descriptions are minimal or absent, and there is no MCP transport layer. The 10 'tools' are inferred from function exports in functions/src/index.ts, but most lack explicit schema registration. This fails the fundamental requirement: it is not an MCP server.
HTTP endpoint that adds or updates social media post IDs for an entry. Accepts twitter, mastodon, bluesky, instagram, and threads post IDs, validates them against network-specific formats, and updates the entry's socialPostIds field.
HTTP endpoint that returns the count of entries with a date before 2022-01-01.
HTTP endpoint that moves an entry from one document ID to another in Firestore. Copies the document data to the new ID and deletes the old document if the new ID doesn't already exist.
Cloud Storage trigger that processes image uploads to the entryImages folder. Validates content type, downloads the original image, resizes it to multiple sizes (300px, 500px, 1000px for regular images; 300px for logos), converts to WebP format, uploads resized versions, and deletes the original if all resizes succeed.
HTTP endpoint that recalculates the total entry count by counting all documents in the entries collection and updates the metadata document.
HTTP endpoint that recalculates the total grift amount by summing all scamAmountDetails.total values from entries where total > 0 and updates the metadata document.
Not an MCP server. This is a Firebase Cloud Functions backend, not an MCP-compliant tool server. No MCP protocol implementation, no transport layer, no tool registration via MCP spec.
8 of 10 tools have NO input schema visible in source code. Only transformEntryForSearch and addSocialPostIds show partial schemas.
Tool descriptions are generic and under 100 chars. E.g., 'Firestore trigger that updates the RSS feed...' lacks WHEN to use, prerequisites, or recovery guidance. LLMs cannot distinguish similar tools.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 27 | 2026-07-28+ | v2 |
HTTP endpoint that transforms all entries in the database. Converts string values in scamAmountDetails fields (preRecoveryAmount, lowerBound, upperBound, recovered) to integers and sets hasScamAmount to true if total > 0.
Transforms an entry for Algolia search by extracting and cleaning title and body text, removing HTML tags and non-breaking spaces, and organizing filter metadata.
Firestore trigger that updates metadata document when entries are written. Tracks entry count and grift total (sum of scam amounts). Increments/decrements entry count on create/delete and updates grift total based on scamAmountDetails changes.
Firestore trigger that updates the RSS feed when entries are created, updated, or deleted. Fetches the 20 most recent entries, renders them using an EJS template, validates the XML with W3C validator, and publishes to Cloud Storage.
No output schemas documented. Tools like getEntryCount, recalculateGriftTotal return data but no schema is visible. LLMs cannot plan downstream calls or extract fields.
Destructive operations (moveEntry, runTransform) lack confirmation or dry-run support. No error handling guidance. Agents could accidentally delete or corrupt data.