Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.t3ratech/market-pulse

REMOTE · MARKET-PULSE.T3RATECH.CO.ZW · 2 COMPONENTS

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

−71 this week 0 Trust /100

Last scanned (19 days ago)

Scores higher than 0% of remote servers

Unreachable for 7 days in a row. Last reached 7 Oct 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

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.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 17 Oct 26 −14

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

  • 16 Oct 26 −14

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

  • 15 Oct 26 −15

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

  • 14 Oct 26 −14

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

  • 13 Oct 26 −14

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

  • 10 Oct 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • HSTS header: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.23 → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: fail → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 7 Oct 26 +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.

  • 4 Oct 26 −1
    • 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 security
    • Schema quality: pass → fail ▼ functional
    • Tool “pulse_resources” now declares an output schema ▲ functional
    • Tool “pulse_should_i_bid” now declares an output schema ▲ functional
    • Tool “pulse_stats” now declares an output schema ▲ functional
    • Tool “pulse_evidence” now declares an output schema ▲ functional
    • Tool “pulse_jobs” now declares an output schema ▲ functional
    • Tool “pulse_lane_detail” now declares an output schema ▲ functional
    • Tool “pulse_lanes” now declares an output schema ▲ functional
    • Tool “pulse_methodology” now declares an output schema ▲ functional
    • 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” functional
    • “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 cosmetic
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 17 Oct 2026 · Probed https://market-pulse.t3ratech.co.zw/mcp

TLS unreached
DNSSEC insecure

Validation of market-pulse.t3ratech.co.zw. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
zw. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://market-pulse.t3ratech.co.zw/mcp Unreachable
http (plaintext) http://market-pulse.t3ratech.co.zw/mcp HTTPS enforced
MCP tools · 10 exposed · ~2,123 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
pulse_account ~158

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
accountUrlstringyesWhere API keys are created.
authenticatedbooleanyesTrue when an API key was recognised.
freshnessstringyesData freshness the tier buys.
pricingUrlstringyesWhere plans are listed.
quotaPerDayinteger|nullyesDaily pull quota; null means unmetered.
remainingTodayinteger|nullyesPulls left today; null when anonymous or unmetered.
tierstringyesTier the connection is served at.

No examples provided.

pulse_evidence ~235

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.

NameTypeReqDescription
idstring–Evidence record id to fetch on its own, as found in a lane's evidence[] or a previous call. Takes precedence over lane.
lanestring–Lane slug (from pulse_lanes): returns every evidence record linked to that lane.
NameTypeReqDescription
countintegeryesNumber of records returned.
recordsarrayyesEvidence records with id, kind, lane, source, captureMethod, capturedAt, summary, payloadSha256, previousChainHash and chainHash.

No examples provided.

pulse_jobs ~257

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.

NameTypeReqDescription
lanestring–Lane slug to restrict to, e.g. "hackernews" or "algora". Omit for every collected lane.
limitinteger–Max listings to return (default 100, maximum 500).
qstring–Free-text match over title, org and skills.
statusstring–Listing status; omit for open listings.
NameTypeReqDescription
countintegeryesListings returned.
listingsarrayyesListings with lane, title, org, url, reward, bids, posted and status.
redactedintegeryesNewer listings hidden by this tier's freshness window.
tierstringyesTier the call was served at: free, basic, pro, max or operator.
totalintegeryesMatching listings visible to this tier.
upgradeUrlstring|null–Pricing URL when listings were redacted, otherwise null.

No examples provided.

pulse_lane_detail ~199

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.

NameTypeReqDescription
slugstringyesLane slug exactly as returned in the slug field of pulse_lanes, e.g. "algora" or "jobforagent". Lowercase, hyphenated.
NameTypeReqDescription
evidencearrayyesEvidence records linked to the lane.
gradestringyesAssay grade: A, B, C, F or Unknown.
namestring–Display name of the lane.
slugstringyesThe lane slug.
verdictobjectyesFull verdict with reasons, liveness, access, automation, payout, confidence and freshness.

No examples provided.

pulse_lanes ~345

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.

NameTypeReqDescription
accessstring–Whether an agent can reach the lane at all: accessible or blocked. Omit for both.
automationstring–What the lane's terms say about automated participation. Omit for every policy.
categorystring–Lane category, e.g. bounty, agent-marketplace, jobs-feed, agent-network. Free text matched exactly; omit for every category.
freshnessstring–How recently the lane was observed: fresh (<=24h), aging (<=7d), stale (<=30d), historical (older). Omit for every age.
gradestring–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…
NameTypeReqDescription
countintegeryesNumber of lanes returned.
lanesarrayyesLane summaries: slug, name, category, grade, gradeLabel, liveness, agentAccess, automation, payout, confidence, freshness, lastVerifiedAt, attempts, settlements.
methodologyVersionstring–Grading methodology version the grades were produced under.

No examples provided.

pulse_methodology ~134

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}.

Input schema present but exposes no named parameters.

NameTypeReqDescription
gradesobjectyesLabel for each grade.
independencestringyesThe independence guarantee.
rulesarrayyesThe grading rules in order of precedence.
versionstringyesMethodology version.

No examples provided.

pulse_resource_detail ~135

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.

NameTypeReqDescription
slugstringyesResource slug exactly as returned in the slug field of pulse_resources.
NameTypeReqDescription
kindstringyesResource kind.
namestringyesDisplay name.
slugstringyesResource slug.

No examples provided.

pulse_resources ~328

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.

NameTypeReqDescription
capstring–Capability tag a resource must have, e.g. video-gen, rag, tts.
categorystring–Category within a kind, as shown on the directory page.
freeboolean–true = only resources with a free tier; false = only paid ones. A JSON boolean, not the string "true".
kindstring–Resource kind to filter by; omit for every kind.
minStarsinteger–Minimum GitHub stars, for open-source entries.
qstring–Free-text match over name, slug, tags and capabilities.
sortstring–Sort order; the sorts a kind supports are listed on its directory page.
tagstring–Comma-separated tags a resource must carry, all of them.
NameTypeReqDescription
countintegeryesNumber of resources returned.
kindsobjectyesDirectory size per resource kind.
resourcesarrayyesDirectory entries with slug, name, kind, description, tags, caps and links.

No examples provided.

pulse_should_i_bid ~201

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.

NameTypeReqDescription
lanestringyesLane slug to judge, exactly as returned in the slug field of pulse_lanes, e.g. "algora".
NameTypeReqDescription
caveatsarrayyesLimits on how far the recommendation can be trusted.
gradestringyesThe lane's assay grade.
lanestringyesThe lane slug that was judged.
rationalestringyesWhy, in one sentence.
recommendationstringyesWhat the evidence supports doing.

No examples provided.

pulse_stats ~131

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
evidenceRecordsinteger–Records in the evidence ledger.
gradedLanesinteger–Lanes with a grade other than Unknown.
gradesobjectyesCount of lanes per grade.
lanesintegeryesTotal lanes in the index.
methodologyVersionstring–Grading methodology version.
settlementsinteger–Recorded settlements.
snapshotAtstringyesDate the snapshot describes.

No examples provided.

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.

remote · market-pulse.t3ratech.co.zw

# add to Claude Code
claude mcp add --transport http t3ratech-market-pulse 'https://market-pulse.t3ratech.co.zw/mcp'
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.