TVPulse

io.tvpulsePublished by tvpulse.ioOfficial publisherv1.0.14Updated Oct 24, 2026

Search OCR/ASR mentions on 15 terrestrial stations (Tokyo 7, Osaka 8); archive from 2026-01-01.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

TVPulse is a remote MCP server that lets an assistant search OCR and ASR mentions across 15 Japanese terrestrial TV stations, with an archive starting 2026-01-0

What you can do
Search OCR and ASR mentions across 15 terrestrial stations, including 7 in Tokyo and 8 in Osaka, through a single remote endpoint. Query the archive, which begins 2026-01-01, for mentions captured from broadcast text and speech. No individual tools are listed, so the exact search and result options are not documented in the supplied material.
When to use it
Use it when you need to find or check what was said or shown on Japanese terrestrial television, for example tracking mentions of a topic, brand or person across Tokyo and Osaka stations.
Requirements
A remote MCP endpoint at mcp.tvpulse.io over streamable HTTP. OAuth authentication is required, so an account with the provider is needed. No environment variables or headers are declared.
Before you install
Access requires OAuth sign-in, so the assistant will act under your TVPulse account; review what the provider stores and how results are used. Coverage is limited to 15 terrestrial stations and to material from 2026-01-01 onward.

Installation

In SourceWeft

  1. Open TVPulse in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.tvpulse%2Ftvpulse/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "tvpulse": {
      "type": "http",
      "url": "https://mcp.tvpulse.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.14LatestSep 27, 2026
  2. v1.0.12Sep 27, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.