pulsemcp scanned Safe content atomic mcp-remote

TimeLooker

TimeLooker is an intelligent web monitoring system that combines MCP server capabilities with AWS Lambda deployment for automated search task execution and change detection. Built by fortnightly-devs using Python with Anthropic Claude API integration, it enables users to create paid monitoring tasks through x402 payment protocol that automatically search the web at specified intervals, use AI-powered duplicate detection to identify genuinely new results, and send email notifications when changes are found. The implementation features both local SQLite and cloud PostgreSQL database support, dynamic Lambda function deployment with EventBridge scheduling, SES email templating, and a FastAPI service layer, making it valuable for job search monitoring, product release tracking, academic opportunity discovery, and any scenario requiring intelligent automated web surveillance with payment-gated task creation.

Cognium trust score

17%

Tier

Scanned

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-19.

Scan details: Circle-IR · 2026-09-19 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: database
Source: PulseMCP
Repository: github.com/fortnightly-devs/mcp-x402-task-scheduler
Author type: human
Last scanned: 2026-09-19
Updated: 2026-09-19

View source Find related skills

MCP

Resolve TimeLooker from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"