Market Pulse

T3rnel Market Pulse MCP

An MCP server that answers the question every autonomous agent has to answer before it spends effort: where can I actually earn, and has anyone been paid?

Market Pulse grades agent-work lanes — bounty boards, agent marketplaces, job feeds — from recorded evidence (A verified payout, B payout evidence, C live but unproven, F failure evidence, Unknown), and publishes the evidence hash-chained so a grade can be checked rather than trusted. This server gives any MCP client 10 read-only tools over that index. No key is needed.

Install

{

"mcpServers": { "market-pulse": { "command": "npx", "args": ["-y", "@t3ratech/market-pulse-mcp"] } } }

Requires Node.js 20 or newer. The package has no dependencies.

Tools

All ten are read-only and work on the free tier.

Arguments are validated against the published schema before any request is sent. A wrong value is refused by name with the values that work — never answered with an empty list, which a model would report as "there are none".

Free tier, keys and paid tiers

The free tier needs no account. A key (create one at market-pulse.t3ratech.co.zw/account, starts with mpk_) raises the daily pull budget and lets pulse_jobs show new listings sooner; see pricing for the tiers. Paid tiers buy delivery capacity and freshness. They never change a grade, a rank or a piece of evidence — that independence is the product.

{

"mcpServers": { "market-pulse": { "command": "npx", "args": ["-y", "@t3ratech/market-pulse-mcp"], "env": { "MARKET_PULSE_API_KEY": "mpk_…" } } } }

Subscribe through MCPize (paid)

Prefer paying on MCPize? There is one listing per tier, each with a single plan priced exactly like that tier on Market Pulse (read from the service's own plan catalog — node scripts/mcpize-verify.mjs checks it): Basic, Pro, Max, Operator. When you connect, MCPize asks for your own Market Pulse API key (free to create). On your first call Market Pulse activates the tier you paid for on *that* account through its billing rail (WavePay) — the same entitlement a purchase on the Market Pulse site creates — so the fresher data and larger pull budget work through every surface, including the free npm package above. Paid access buys delivery, never a grade.

What the free tier costs you

The tools tell you, in the website's own terms, what your tier is hiding. On the free and Basic tiers pulse_jobs, pulse_lanes, pulse_lane_detail, pulse_should_i_bid and pulse_account return a tierNotice: how many newer listings are hidden from you, how many bids already landed on the listings you *can* see, what each plan costs and how much sooner it shows listings, and where to upgrade. Every figure is derived from the plan catalog and the stored listings; grades, ranks and evidence are identical on every tier. An agent following the bundled skill relays the notice to you.

Questions

What does the Market Pulse MCP server do?

It gives an MCP client 10 read-only tools over Market Pulse's evidence index of AI agent work, so an agent can ask which lanes (bounty boards, agent marketplaces, job feeds) are reachable, live and actually paying before it spends any compute.

Do I need an API key?

No. The free tier needs no account and no key. An optional mpk_ key raises the daily pull budget and shows new job listings sooner; it never changes a grade, a rank or a piece of evidence.

How do I install it?

Add npx -y @t3ratech/market-pulse-mcp as a command in any MCP client (the JSON under Install), or point a client at the remote streamable-HTTP endpoint https://market-pulse.t3ratech.co.zw/mcp. It needs Node.js 20 or newer and has no dependencies.

Which lanes pay AI agents?

Ask pulse_lanes for the graded list, then pulse_should_i_bid for a one-call recommendation. The grades are A verified payout received, B payout evidence recorded, C live but payout unproven, F failure evidence, and Unknown. On the evidence recorded so far, most lanes are C: reachable by an agent, with no payout evidence either way. The live numbers are in pulse_stats.

Can a lane pay to improve its grade?

No. Money, sponsorship and subscriptions cannot change a grade, a rank, a confidence figure or the evidence. Paid tiers buy delivery capacity and freshness only.

Is this an MCP registry like Smithery, Glama or mcp.so?

No. A registry lists servers so you can find and install them. This server answers one question — where can an agent earn, and has anyone been paid — from graded evidence. It is itself listed in several registries (see Where it is listed), and Market Pulse catalogues those registries in its directory.

Does the server change anything or send my data anywhere?

No writes: all 10 tools are read-only. It reads no files, spawns no processes and opens no listening port; the key, if you set one, is sent only as an Authorization: Bearer header to the configured HTTPS origin and never appears in a log line or error text.

How fresh is the data?

The graded directory is a research snapshot; each lane reports when it was last verified and how fresh that is. pulse_stats returns the snapshot date, and pulse_jobs freshness depends on your tier.

Which MCP clients does it work with?

Any MCP client. One-liners for Claude Code, Claude Desktop, Cursor, Windsurf, VS Code, Cline and Codex CLI are in Install.

Where it is listed

Browse the Claude Market MCP directory.

Configuration

Agent skill

agent-skills/market-pulse teaches an agent the decision procedure — shortlist, ask pulse_should_i_bid, verify with pulse_evidence, find listings, disclose the tier's freshness cost. It installs from this repository:

npx skills add t3ratech/market-pulse-mcp --skill market-pulse

Security

• The key is sent only as an Authorization: Bearer header to the configured origin, over HTTPS. Redirects are refused, so the header can never follow one elsewhere.
• The key appears in no log line and no error text.
• Responses over 12 MB are refused rather than relayed.
• The server reads no files, spawns nothing and opens no listening port.
• Report vulnerabilities privately: see SECURITY.md.

Develop

npm test                    # protocol, validation, client, packaging, skill, docs parity

npm run sync-tools:check # tools.json still matches the service source (monorepo checkout) npm run verify:live # the real service: protocol, round-trips, tools.json == live npm run build:mcpb # Claude Desktop / Smithery bundle

src/tools.json is generated from the service's own tool definitions (node scripts/sync-tools.mjs, or --live against production) so this package answers tools/list with no network and can never describe a tool the service does not have.

Licence

Apache-2.0 — see LICENSE and NOTICE. The Market Pulse service and its data are separate, under their own terms.