mcpbeat Sign in

MediaPact MCP Server

by mediapact Your server? Claim it
answering

MediaPact is answering right now. Last checked 4 min ago.

Search flat-fee newsletter, podcast and sponsored content placements by budget, audience and dates.

Uptime history 25 days of history · worst day 96%
25 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
604 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

MediaPact missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add mcp --transport http https://api.mediapact.ai/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.mediapact.ai/mcp
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://api.mediapact.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://api.mediapact.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://api.mediapact.ai/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://api.mediapact.ai/mcp streamable-http sign-in 599 ms 4 min ago

Alternatives to MediaPact

same job, measured the same way
Grep.FM
by grep

Podcast database: search 3M+ shows by guests, sponsors, charts and reviews; get contact emails.

answering
Rephonic
by rephonic

Research 3M+ podcasts with audience data, contacts, episodes, transcripts, charts, and sponsors.

answering
G
Granola Search
by jcpsimmons

Search Granola meeting notes by attendees, dates, content, and workspaces.

local only
Substack Newsletter MCP
by dancerdan15

Substack newsletter, posts & podcast search

answering
SponsorHound
by sponsorhound

Find brands that sponsor podcasts and newsletters like yours, with dated public ad reads.

answering
MCP Gera Nexus
by gera

Search Gera marketplaces and create consent-first booking intents. No payment taken by server.

82 installs/wk local only
Chipp Newsletters
by chipp

Chipp: newsletter topics, audiences, contacts, campaigns and sends

answering
NewsletterFIT
by newsletterfit

Search 89,000+ Substack and beehiiv newsletters, their sponsors, topics and mentioned companies.

answering

MediaPact — questions

Answers built from our own checks of this server.

Why is there no tool list for MediaPact?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is MediaPact working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 604 ms. The bar chart above shows every period we have measured.
How do I connect MediaPact?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to MediaPact?
No API key is involved. MediaPact answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is MediaPact?
It answers our handshake in 604 ms on average, which is faster than 17% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.