Custom-MCP-Server
Provides a Python-based Model Context Protocol (MCP) server exposing tools to scrape social media profile data (LinkedIn, Facebook, Instagram) and perform Google search via Serper/Google search. It is intended to be run locally (e.g., with Claude Desktop) and uses external APIs (RapidAPI and Serper) authenticated via environment variables.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Security posture is inferred from README: uses API keys via a .env file (better than hardcoding) but provides no evidence of TLS enforcement, key redaction, audit logging behavior, or scope minimization. The server also performs scraping via third-party providers, which may introduce data-handling and privacy/compliance risks not addressed in the documentation. Dependency hygiene and specific CVE status cannot be confirmed from provided content.
⚡ Reliability
Best When
You need an MCP tool interface to quickly connect an agent to third-party scraping/search APIs for occasional, user-driven URL lookups and you can manage API keys securely.
Avoid When
You require strong guarantees around compliance, provenance, or stability of scraped fields; or you need a well-defined public API contract (OpenAPI/SDK) with predictable schemas beyond the described example.
Use Cases
- • Scrape public/profile information from LinkedIn, Facebook, and Instagram URLs for research workflows
- • Augment an agent with web search results for investigation workflows using Serper
- • Feed structured (JSON) scraped profile/search data into downstream analysis or summarization by an AI assistant
Not For
- • High-volume scraping at scale without careful rate limiting/compliance review
- • Scraping non-public data or bypassing access controls
- • Production systems needing audited compliance guarantees for data sources and scraping legality
- • Environments that cannot securely manage third-party API keys or where data handling must be contractually restricted
Interface
Authentication
Authentication to the underlying providers is via API keys stored in a .env file as described. The README does not describe fine-grained scopes or any user-level OAuth flow.
Pricing
No pricing is documented in the repository README; costs would depend on RapidAPI and Serper plans and usage.
Agent Metadata
Known Gotchas
- ⚠ Tool output schema is only exemplified; exact fields and error formats are not documented in the README.
- ⚠ Scraping/search depends on third-party APIs (RapidAPI/Serper), which may rate limit or fail intermittently; agent retry/backoff guidance is not provided.
- ⚠ Requires environment variables (.env) to be set; without them tools likely fail at runtime.
- ⚠ LinkedIn/Facebook/Instagram scraping may have access and policy constraints—results may vary or fail depending on the upstream provider and URL type.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Custom-MCP-Server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.