# io.github.t3ratech/market-pulse (remote · market-pulse.t3ratech.co.zw)

Evidence-graded agent-work lanes, bid advice, live agent jobs and a hash-chained evidence ledger.

- Trust score: 0/100 (low)
- Change this week: −71
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `market-pulse.t3ratech.co.zw`: 0/100 (this document), [markdown](https://verifymcp.io/servers/t3ratech-market-pulse/market-pulse.md), [page](https://verifymcp.io/servers/t3ratech-market-pulse/market-pulse)
- npm · `@t3ratech/market-pulse-mcp`: 82/100, [markdown](https://verifymcp.io/servers/t3ratech-market-pulse/t3ratech-market-pulse-mcp.md), [page](https://verifymcp.io/servers/t3ratech-market-pulse/t3ratech-market-pulse-mcp)

## Channel facts

- Endpoint: `https://market-pulse.t3ratech.co.zw/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the io.github.t3ratech/market-pulse MCP server?

io.github.t3ratech/market-pulse is a hosted endpoint at https://market-pulse.t3ratech.co.zw/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http t3ratech-market-pulse 'https://market-pulse.t3ratech.co.zw/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "t3ratech-market-pulse": {
      "url": "https://market-pulse.t3ratech.co.zw/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "t3ratech-market-pulse": {
      "type": "http",
      "url": "https://market-pulse.t3ratech.co.zw/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.t3ratech-market-pulse]
url = "https://market-pulse.t3ratech.co.zw/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "t3ratech-market-pulse": {
      "type": "remote",
      "url": "https://market-pulse.t3ratech.co.zw/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add t3ratech-market-pulse --url 'https://market-pulse.t3ratech.co.zw/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  t3ratech-market-pulse:
    url: "https://market-pulse.t3ratech.co.zw/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "t3ratech-market-pulse": {
      "Transport": "http",
      "Url": "https://market-pulse.t3ratech.co.zw/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add t3ratech-market-pulse -t streamable-http -u 'https://market-pulse.t3ratech.co.zw/mcp'
```

### Other

```json
{
  "mcpServers": {
    "t3ratech-market-pulse": {
      "type": "http",
      "url": "https://market-pulse.t3ratech.co.zw/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 0, −14)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-10-16 (score 14, −14)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-10-15 (score 28, −15)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-10-14 (score 43, −14)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-10-13 (score 57, −14)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-10-10 (score 71, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] HSTS header: fail → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.23 → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Transport: pass → fail
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: fail → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-07 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 23. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-04 (score 70, −1)

- [security] Tool “pulse_resources” rewrote its description, which is the text the model reads
- [security] Tool “pulse_should_i_bid” rewrote its description, which is the text the model reads
- [security] Tool “pulse_stats” rewrote its description, which is the text the model reads
- [security] Tool “pulse_evidence” rewrote its description, which is the text the model reads
- [security] Tool “pulse_jobs” rewrote its description, which is the text the model reads
- [security] Tool “pulse_lane_detail” rewrote its description, which is the text the model reads
- [security] Tool “pulse_lanes” rewrote its description, which is the text the model reads
- [security] Tool “pulse_methodology” rewrote its description, which is the text the model reads
- [security] Tool “pulse_resource_detail” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool “pulse_resources” now declares an output schema
- [functional improvement] Tool “pulse_should_i_bid” now declares an output schema
- [functional improvement] Tool “pulse_stats” now declares an output schema
- [functional improvement] Tool “pulse_evidence” now declares an output schema
- [functional improvement] Tool “pulse_jobs” now declares an output schema
- [functional improvement] Tool “pulse_lane_detail” now declares an output schema
- [functional improvement] Tool “pulse_lanes” now declares an output schema
- [functional improvement] Tool “pulse_methodology” now declares an output schema
- [functional improvement] Tool “pulse_resource_detail” now declares an output schema
- [functional] First check of Tool coverage: 100
- [functional] Schema quality: good → excellent
- [functional] New tool “pulse_account”
- [cosmetic] “pulse_should_i_bid” reworded the description of “lane”
- [cosmetic] “pulse_evidence” reworded the description of “id”
- [cosmetic] “pulse_evidence” reworded the description of “lane”
- [cosmetic] “pulse_jobs” reworded the description of “limit”
- [cosmetic] “pulse_jobs” reworded the description of “status”
- [cosmetic] “pulse_lane_detail” reworded the description of “slug”
- [cosmetic] “pulse_lanes” reworded the description of “access”
- [cosmetic] “pulse_lanes” reworded the description of “automation”
- [cosmetic] “pulse_lanes” reworded the description of “category”
- [cosmetic] “pulse_lanes” reworded the description of “freshness”
- [cosmetic] “pulse_lanes” reworded the description of “grade”
- [cosmetic] “pulse_resource_detail” reworded the description of “slug”
- [cosmetic] Tool “pulse_resources” changed its title: Search the agent directory
- [cosmetic] Tool “pulse_should_i_bid” changed its title: Should an agent bid on this lane?
- [cosmetic] Tool “pulse_stats” changed its title: Index-wide counts
- [cosmetic] Tool “pulse_evidence” changed its title: Read the evidence ledger
- [cosmetic] Tool “pulse_jobs” changed its title: Live agent job listings
- [cosmetic] Tool “pulse_lane_detail” changed its title: Get one lane's full record
- [cosmetic] Tool “pulse_lanes” changed its title: List agent-work lanes
- [cosmetic] Tool “pulse_methodology” changed its title: Grading methodology
- [cosmetic] Tool “pulse_resource_detail” changed its title: Get one directory resource

## MCP tools (10)

### `pulse_lanes` (~345 tokens)

List agent-work lanes

List the agent-work lanes in the Market Pulse index (bounty boards, agent marketplaces, job feeds, agent networks), each with its evidence-backed grade, liveness, agent-access verdict, freshness and confidence. Use this first to discover lane slugs and to shortlist where an autonomous agent can realistically earn; filters narrow the list and omitting all of them returns every lane. Use pulse_lane_detail for one lane's full record and pulse_should_i_bid for a spend recommendation; use pulse_jobs for individual open listings. Read-only snapshot data, same answer for the same arguments, never changes state. Works without an API key on the free tier. Returns {count, methodologyVersion, lanes[]}; a filter value outside its enum is refused with the values that work, never answered with an empty list.

Input parameters:

- `access` (string): Whether an agent can reach the lane at all: accessible or blocked. Omit for both.
- `automation` (string): What the lane's terms say about automated participation. Omit for every policy.
- `category` (string): Lane category, e.g. bounty, agent-marketplace, jobs-feed, agent-network. Free text matched exactly; omit for every category.
- `freshness` (string): How recently the lane was observed: fresh (<=24h), aging (<=7d), stale (<=30d), historical (older). Omit for every age.
- `grade` (string): Assay grade to filter by. A = a received settlement; B = payout evidence short of a received settlement; C = live but payout unproven; F = observed failure; Unknown = insufficient evidence. Omit for…

Output parameters:

- `count` (integer): Number of lanes returned.
- `lanes` (array): Lane summaries: slug, name, category, grade, gradeLabel, liveness, agentAccess, automation, payout, confidence, freshness, lastVerifiedAt, attempts, settlements.
- `methodologyVersion` (string): Grading methodology version the grades were produced under.

### `pulse_lane_detail` (~199 tokens)

Get one lane's full record

Get the complete record for one agent-work lane: grade and verdict rationale, how an agent accesses it, payout method and currency, adapter, recorded attempts and settlements, and every linked evidence record. Use after pulse_lanes when you need the reasoning behind a grade or the links to act on; do not use it to browse (call pulse_lanes) or to decide whether to spend attempts (call pulse_should_i_bid, which condenses this into a recommendation). Read-only and idempotent. Works without an API key on the free tier. Returns the lane summary fields plus description, website, workUrl, apiUrl, accessMethod, payoutMethod, verdict and an evidence[] array. An unknown slug is refused with an error naming it.

Input parameters:

- `slug` (string, required): Lane slug exactly as returned in the slug field of pulse_lanes, e.g. "algora" or "jobforagent". Lowercase, hyphenated.

Output parameters:

- `evidence` (array): Evidence records linked to the lane.
- `grade` (string): Assay grade: A, B, C, F or Unknown.
- `name` (string): Display name of the lane.
- `slug` (string): The lane slug.
- `verdict` (object): Full verdict with reasons, liveness, access, automation, payout, confidence and freshness.

### `pulse_should_i_bid` (~201 tokens)

Should an agent bid on this lane?

Get a one-call, evidence-backed recommendation on whether an autonomous agent should spend attempts on a lane: one of bid, bid_cautiously, probe_first, avoid or insufficient_evidence, with the rationale and caveats. Call pulse_lanes first to get the slug, then call this before committing an agent's time or an application to any lane; it is the decision tool, while pulse_lane_detail is the audit trail behind it. A recommendation reflects observed outcomes inside the snapshot window, never a guarantee, and Unknown means unmeasured rather than failed. Read-only and idempotent. Works without an API key on the free tier. Returns {lane, grade, confidence, freshness, methodologyVersion, recommendation, rationale, caveats[]}. An unknown lane is refused with an error naming it.

Input parameters:

- `lane` (string, required): Lane slug to judge, exactly as returned in the slug field of pulse_lanes, e.g. "algora".

Output parameters:

- `caveats` (array): Limits on how far the recommendation can be trusted.
- `grade` (string): The lane's assay grade.
- `lane` (string): The lane slug that was judged.
- `rationale` (string): Why, in one sentence.
- `recommendation` (string): What the evidence supports doing.

### `pulse_evidence` (~235 tokens)

Read the evidence ledger

Read the hash-chained evidence ledger that every grade is derived from: one record by id, every record linked to a lane, or the whole chain when no argument is given. Use it to verify a claim before relying on it, to cite sources, or to audit that a record has not been altered (each record carries payloadSha256, previousChainHash and chainHash). Call pulse_lanes to find a lane slug; pass id or lane, not both; with neither you receive the entire ledger, which is large, so prefer a lane. Read-only and idempotent. Works without an API key on the free tier. Returns {count, records[]} where each record has id, kind, lane, source, captureMethod, capturedAt, summary and the hashes. An unknown id or lane is refused with an error naming it.

Input parameters:

- `id` (string): Evidence record id to fetch on its own, as found in a lane's evidence[] or a previous call. Takes precedence over lane.
- `lane` (string): Lane slug (from pulse_lanes): returns every evidence record linked to that lane.

Output parameters:

- `count` (integer): Number of records returned.
- `records` (array): Evidence records with id, kind, lane, source, captureMethod, capturedAt, summary, payloadSha256, previousChainHash and chainHash.

### `pulse_stats` (~131 tokens)

Index-wide counts

Get the index's headline numbers: lanes, graded lanes, grade distribution, probes, evidence records, attempts, settlements and settlement value, directory resources, live job count, and the snapshot date they describe. Use it to size the index, to quote a current figure with its date, or to check data freshness before trusting a grade; use pulse_lanes when you need the lanes themselves. Takes no arguments, read-only and idempotent. Works without an API key on the free tier. Returns a flat object including snapshotAt, methodologyVersion, lanes, gradedLanes, grades, settlements and evidenceRecords.

Output parameters:

- `evidenceRecords` (integer): Records in the evidence ledger.
- `gradedLanes` (integer): Lanes with a grade other than Unknown.
- `grades` (object): Count of lanes per grade.
- `lanes` (integer): Total lanes in the index.
- `methodologyVersion` (string): Grading methodology version.
- `settlements` (integer): Recorded settlements.
- `snapshotAt` (string): Date the snapshot describes.

### `pulse_methodology` (~134 tokens)

Grading methodology

Get the grading rules themselves: what each grade (A, B, C, F, Unknown) requires, how freshness is derived, how Unknown is handled, and the independence guarantee that money, sponsorship and subscriptions cannot change a grade. Use it to explain or defend a grade to a human, or to interpret the grade filter on pulse_lanes; it describes policy, not any one lane, so use pulse_lane_detail for a specific verdict. Takes no arguments, read-only and idempotent. Works without an API key on the free tier. Returns {version, grades, rules[], independence, snapshotAt, dataset}.

Output parameters:

- `grades` (object): Label for each grade.
- `independence` (string): The independence guarantee.
- `rules` (array): The grading rules in order of precedence.
- `version` (string): Methodology version.

### `pulse_resources` (~328 tokens)

Search the agent directory

Search the agent directory of models, MCP servers, frameworks, tools, platforms, work lanes and other resources, filtered by kind, category, capability, tags, free tier or GitHub stars and sorted as you choose. Use it to find what exists (for example free open-source MCP servers with 1000+ stars, or models that do video-gen); use pulse_resource_detail for one entry's full record and pulse_lanes when the question is about earning work rather than tooling. Filters combine with AND; omit all to list everything in the directory. Read-only and idempotent. Works without an API key on the free tier. Returns {count, kinds, resources[]}. An unknown kind, sort or argument is refused with the accepted values, never silently ignored.

Input parameters:

- `cap` (string): Capability tag a resource must have, e.g. video-gen, rag, tts.
- `category` (string): Category within a kind, as shown on the directory page.
- `free` (boolean): true = only resources with a free tier; false = only paid ones. A JSON boolean, not the string "true".
- `kind` (string): Resource kind to filter by; omit for every kind.
- `minStars` (integer): Minimum GitHub stars, for open-source entries.
- `q` (string): Free-text match over name, slug, tags and capabilities.
- `sort` (string): Sort order; the sorts a kind supports are listed on its directory page.
- `tag` (string): Comma-separated tags a resource must carry, all of them.

Output parameters:

- `count` (integer): Number of resources returned.
- `kinds` (object): Directory size per resource kind.
- `resources` (array): Directory entries with slug, name, kind, description, tags, caps and links.

### `pulse_jobs` (~257 tokens)

Live agent job listings

List open job listings collected from the agent-accessible lanes, each with title, organisation, URL, reward and currency, bid count, posting time and status. Use it to find work an agent can take now; use pulse_lanes first if you need to know which lanes are trustworthy. Freshness is tiered by the caller's API key: free sees listings once they are up to 24h old, basic 4h, pro and above can trigger a live refresh, and newer listings are counted in redacted rather than shown. Read-only for the caller, though a keyed call consumes one pull from the daily quota and a pro+ call may refresh the live collection. Returns {tier, count, total, redacted, upgrade, upgradeUrl, listings[]}. Fails with a refusal if the persistent store is unavailable.

Input parameters:

- `lane` (string): Lane slug to restrict to, e.g. "hackernews" or "algora". Omit for every collected lane.
- `limit` (integer): Max listings to return (default 100, maximum 500).
- `q` (string): Free-text match over title, org and skills.
- `status` (string): Listing status; omit for open listings.

Output parameters:

- `count` (integer): Listings returned.
- `listings` (array): Listings with lane, title, org, url, reward, bids, posted and status.
- `redacted` (integer): Newer listings hidden by this tier's freshness window.
- `tier` (string): Tier the call was served at: free, basic, pro, max or operator.
- `total` (integer): Matching listings visible to this tier.
- `upgradeUrl` (string|null): Pricing URL when listings were redacted, otherwise null.

### `pulse_resource_detail` (~135 tokens)

Get one directory resource

Get the full directory record for one resource: description, kind, capabilities, tags, pricing flag, GitHub stars, links and source. Use after pulse_resources when you have chosen an entry and need its links or metadata; do not use it for work lanes you want to judge (use pulse_lane_detail). Read-only and idempotent. Works without an API key on the free tier. Returns the resource object, with a verdict block when the resource is a graded lane. An unknown slug is refused with an error naming it.

Input parameters:

- `slug` (string, required): Resource slug exactly as returned in the slug field of pulse_resources.

Output parameters:

- `kind` (string): Resource kind.
- `name` (string): Display name.
- `slug` (string): Resource slug.

### `pulse_account` (~158 tokens)

Check tier and daily quota

Report which Market Pulse tier this connection is served at (free, basic, pro, max or operator), whether an API key was recognised, the daily pull quota and how much of it remains, the freshness that tier buys, and where to upgrade. Call it after pulse_jobs reports redacted listings, when a call is refused for quota, or to confirm a freshly configured key works; it is the only tool whose answer depends on who is asking, and it returns no listings (use pulse_jobs for those). Read-only and idempotent; it consumes one pull when a key is sent and none when anonymous. Returns {tier, authenticated, quotaPerDay, remainingToday, freshness, pricingUrl, accountUrl}. Never returns the key itself.

Output parameters:

- `accountUrl` (string): Where API keys are created.
- `authenticated` (boolean): True when an API key was recognised.
- `freshness` (string): Data freshness the tier buys.
- `pricingUrl` (string): Where plans are listed.
- `quotaPerDay` (integer|null): Daily pull quota; null means unmetered.
- `remainingToday` (integer|null): Pulls left today; null when anonymous or unmetered.
- `tier` (string): Tier the connection is served at.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/t3ratech-market-pulse/market-pulse#diagnostics

## Score history

- 2026-10-17: 0
- 2026-10-16: 14
- 2026-10-15: 28
- 2026-10-14: 43
- 2026-10-13: 57
- 2026-10-12: 71
- 2026-10-10: 71
- 2026-10-07: 71
- 2026-10-04: 70
- 2026-10-03: 71
- 2026-10-02: 70
- 2026-10-01: 70
- 2026-09-30: 70

## Common questions

### What is the io.github.t3ratech/market-pulse MCP server?

io.github.t3ratech/market-pulse is an MCP server listed in the public MCP registry as io.github.t3ratech/market-pulse. Evidence-graded agent-work lanes, bid advice, live agent jobs and a hash-chained evidence ledger. This page covers its hosted endpoint (https://market-pulse.t3ratech.co.zw/mcp).

### Is the io.github.t3ratech/market-pulse MCP server safe to use?

io.github.t3ratech/market-pulse scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.t3ratech/market-pulse MCP server expose?

io.github.t3ratech/market-pulse exposes 10 tools: pulse_lanes, pulse_lane_detail, pulse_should_i_bid, pulse_evidence, pulse_stats, and 5 more. Their descriptions and schemas cost roughly 2,123 tokens of context every time the server is loaded.

### Does the io.github.t3ratech/market-pulse MCP server require authentication?

Its publisher declares no required credentials for io.github.t3ratech/market-pulse. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the io.github.t3ratech/market-pulse MCP server still maintained?

io.github.t3ratech/market-pulse has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the io.github.t3ratech/market-pulse MCP server?

VerifyMCP ran 3 checks on io.github.t3ratech/market-pulse, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about io.github.t3ratech/market-pulse: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://market-pulse.t3ratech.co.zw/mcp
- Repository: https://github.com/t3ratech/market-pulse-mcp
- Website: https://market-pulse.t3ratech.co.zw/
- Changelog RSS feed: https://verifymcp.io/servers/t3ratech-market-pulse/market-pulse.xml
- Changelog JSON feed: https://verifymcp.io/servers/t3ratech-market-pulse/market-pulse/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/t3ratech-market-pulse/market-pulse.json
- HTML version of this page: https://verifymcp.io/servers/t3ratech-market-pulse/market-pulse