Marketing
primitivebench.com
Provides tools to list and query brand monitoring signals from various sources, returning normalized data for analysis.
ENDPOINT 1
https://api.primitivebench.com/mcp
MCP server metadata
- Name
- mcp-typescript server on vercel
- Version
- 0.1.0
Brand-monitoring signals from five sources (Reddit, software reviews, app stores, competitor pages, news) in one normalized JSON shape. Call list_sources first to discover sources, then get_signals to fetch them.
Known tools 2
list_sourcesList every available brand-monitoring signal source, what its `q` parameter means, and whether it is ready to query.
Inferred read-onlyget_signalsFetch brand-monitoring signals from one source in the shared normalized shape (platform, id, url, title, text, author, published_at, rating, score, upvote_ratio).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.mcp-typescript-server-on-vercel]
url = "https://api.primitivebench.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"mcp-typescript-server-on-vercel": {
"type": "http",
"url": "https://api.primitivebench.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: mcp-typescript-server-on-vercel
Remote MCP URL: https://api.primitivebench.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"mcp-typescript-server-on-vercel": {
"url": "https://api.primitivebench.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"mcp-typescript-server-on-vercel": {
"type": "http",
"url": "https://api.primitivebench.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "mcp-typescript-server-on-vercel",
"transport": "streamable-http",
"url": "https://api.primitivebench.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.