pulsemcp verified Safe content atomic mcp-remote

TMDB

This TMDB MCP server provides integration with The Movie Database API for accessing movie, TV show, and entertainment industry data through ten specialized tools including search functionality, detailed information retrieval, trending content discovery, and people lookup capabilities. Built with TypeScript using Express and Axios, it features dual deployment modes with both standard MCP protocol support via stdin/stdout communication and HTTP server mode for web-based integrations, plus Docker containerization and comprehensive error handling for TMDB API responses. The implementation automatically constructs image URLs for posters and backdrops, supports pagination and advanced query parameters like year filtering and additional data appending, and includes legacy tool discovery for backward compatibility, making it valuable for AI assistants building entertainment recommendation systems, movie databases, or content discovery applications.

Cognium trust score

97%

Tier

Verified

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/dervish666/tmdb-mcp-server
Author type: human
Last scanned: 2026-09-19
Updated: 2026-09-19

View source Find related skills

MCP

Resolve TMDB 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"