other
- Location
SKILL.md:19- Finding
Unverified Remote MCP Service Exposes Agent Profile and Activity Data
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 19-55
Vulnerability Type: External MCP Trust and Privacy Exposure
Risk Level: MediumThe skill instructs users to connect their agent to a remotely controlled MCP endpoint hosted on a project-specific Supabase domain. The exposed tools accept identifying and preference data and provide access to subscription statistics and reading history.
Complete relevant snippet:
markdown ## Setup This skill uses a remote MCP server. Add the following to your MCP configuration: ```json { "mcpServers": { "finally-offline": { "url": "https://yaieomxrayxpvfjxxctg.supabase.co/functions/v1/human-culture-mcp", "transport": "http" } } }No API key required for browsing. Subscribe to unlock digest generation.
Available Tools
list_articles
Browse all published articles with optional filters.
category(optional): Filter by category (fashion, music, sneakers, design, tech)limit(optional): Number of articles to return (default 10)
search_articles
Search articles by keyword.
query(required): Search term
subscribe_agent
Subscribe your agent to Finally Offline.
agent_name(required): Your agent's display nameinterests(optional): Array of topic interests
generate_digest
Generate a branded HTML newsletter digest.
categories(optional): Array of categories to includelimit(optional): Number of articles in digest
get_agent_report
View your subscription stats and reading history.
text ### Technical Analysis The configured MCP server is hosted on a third-party Supabase project domain rather than the publication domain identified elsewhere in the skill. Invoking its tools can transmit an agent name, interests, search queries, requested categories, and usage metadata to the remote operator. The documented `get_agent_report` capability indicates tha ...[truncated 1799 chars]- Remediation
View remediation
Remediation Suggestions
- Host the MCP endpoint on the documented publication domain or provide verifiable documentation proving ownership of the Supabase endpoint.
- Require explicit user confirmation before invoking
subscribe_agentor transmitting identifiers, interests, searches, or reading activity. - Publish a clear privacy policy describing every transmitted field, its purpose, retention period, sharing policy, and deletion process.
- Minimize collection by using a random pseudonymous identifier instead of an agent display name and by avoiding persistent query or reading-history storage unless strictly necessary.
- Provide tools for users to inspect, export, and permanently delete their profiles and activity records.
- Authenticate the MCP service and validate or pin expected tool names and input schemas so unexpected capability changes are rejected.
- Restrict MCP client permissions to the minimum required capabilities and review server metadata before each sensitive operation.
- Treat all newsletter HTML and article content returned by the service as untrusted data. Sanitize HTML before rendering and prevent remote content from being interpreted as agent instructions.
