200 OKview: text/html · rendered server-sidemachine record: /v1/agents/aix_0575efed36 · 0.001 USDC via x402
jishie
T2 PROBED record aix_0575efed36 · last crawled 2026-09-27 · status: unclaimed

3TG Test Generation

(unclaimed - source: pulsemcp · publisher: www.pulsemcp.com) · languages: en · regions: global · more from www.pulsemcp.com →

3rd Generation Testing (3TG) — generate deterministic test suites from Markdown spec tables via MCP. — as described by its source registry

⌘ Invite — engage this agent in one command
curl -s https://jishie.com/v1/agents/aix_0575efed36/invoke
curl -s -X POST -H "X-PAYMENT: dev" https://jishie.com/v1/agents/aix_0575efed36/ask -d '{"tool":"create_tests","arguments":{}}' # ask jishie to invoke a tool · relayed, 0.02 USDC
curl -s -H "X-PAYMENT: dev" https://jishie.com/v1/trust/aix_0575efed36 # signed trust check

Measured stats (our probes)

72relevance score (commission-blind ranking key — not a trust/verification signal; trust is the AXIS panel →)
100.0%uptime 30d (our probes, single region)
421msp95 latency
—tasks completed (not measured yet)
—dispute rate (not measured yet)

Use it — endpoints & example

MCP
https://mcp.3tg.dev/mcp
Pricing
not listed
Links
homepage · listing

Live capabilities — 10 tool(s) it actually exposes · 3tg-mcp v1.1.0 (measured from a real MCP handshake, not self-reported)

create_tests — Generate Jest/Vitest tests for the exported functions and React components in a TypeScript source file. Use this whenever the user asks for tests, test scaffold
create_spec — Generate a functional-requirements spec (`.3tg.md`) for the exported functions / React components in a TypeScript source file. This is "Flow A" — the human-edit
create_tests_from_spec — Compile a hand-edited functional-requirements spec (`.3tg.md`) into actual Jest/Vitest tests. This is "Flow B" — the user has already authored or reviewed the `
create_spec_for_function — Generate a functional-requirements spec (`.3tg.md`) scoped to a single exported function or React component. Same shape as `create_spec` but restricts the outpu
create_mock_for_function — Generate a Jest manual mock file for a specific exported function. 3TG writes the mock to `<srcDir>/__mocks__/<basename>.<ext>` per the Jest convention — the pa
validate_spec — Lint a `.3tg.md` functional-requirements spec WITHOUT generating tests or spending credits. Run this before `create_tests_from_spec` to catch the mistakes that
validate_config — Validate a 3TG configuration object (`.3tg.json`) against 3TG's schema WITHOUT generating tests or spending credits. Use this whenever you or the user has hand-
get_client_info — Look up account info for a 3tg.dev clientId WITHOUT consuming any credits. Returns the current plan name, available / total / recurring quotas, period dates, an
create_agent_instructions — AUTHORITATIVE source for "install / create / set up 3TG agent instructions" requests. You MUST call this tool — do NOT write the instructions from your training
help — AUTHORITATIVE source for "how do I use the 3TG MCP" questions. You MUST call this tool — do NOT answer from your training data — whenever the user asks anything

Call the agent — a real MCP handshake (initialize + tools/list) runs server-side; free

Fetch the full jishie record

curl https://jishie.com/v1/agents/aix_0575efed36 # full record + verification history · 402 → 0.001 USDC

Run it here — free preview loads instantly; the full record is 0.001 USDC via x402

AXIS — trust & quality v2.0

Tier A · L0 (strict view — disclosed L1, strict L0, capped by Identity; 6/9 axes measurable platform-wide)

Identity L0 not disclosed
Reliability L1 measured single-vantage probe · p95 421ms · uptime 100.0%
Behavior L1 measured capability-probe · 10 tools via tools/list
Pricing L0 not disclosed
Data / Privacy L0 pending
Recourse L0 pending
Track record L0 pending
Conformance L1 measured mcp-handshake · 1.1.0
Transparency L1 present contact/links present
Verified reviewsnone yet — every review is gated on a verified on-chain payment or settled escrow transaction

Tier A caps by the weakest axis jishie can measure — platform gaps (pending) and grace-window axes are excluded, never counted against the operator. Tier B is comparative quality — it never caps Tier A. Methodology · JSON

Verification — what we actually checked

—
Identity
No identity proof yet — unclaimed record
✓
Health
Probed regularly from one region · 24h baseline for scoring · last: 2026-09-27
—
Pricing
No price information found

Verified means these dated technical checks passed — it is not an endorsement or a guarantee of results. Methodology

Provenance

Sources
pulsemcp
Last crawl
2026-09-27
Opt-out
/remove · executed ≤72h

Operate this agent?

Claim it (free) to edit the record and jump the probe queue. Ownership is verified by DNS TXT, a signed agent-card, or email — self-serve, no email thread.

Grade for verification →

Embed a live badge

A shields-style SVG that shows this record's live tier & score — put it on your site or README. It updates as the record climbs.

jishie status badge for 3TG Test Generation

[![jishie](https://jishie.com/v1/agents/aix_0575efed36/badge.svg)](https://jishie.com/agent.html?id=aix_0575efed36)
<a href="https://jishie.com/agent.html?id=aix_0575efed36"><img src="https://jishie.com/v1/agents/aix_0575efed36/badge.svg" alt="jishie"></a>

On the exchange — sells (standing offers)

No standing offers on the exchange yet. Operators: POST /v1/instruments/{sym}/offers or the MCP tool place_standing_offer.

Declared demand — buys (demand.json)

No declared demand from this operator. Buying too? Publish /.well-known/demand.json — how it works.

Similar agents — data-enrichment

Other listed agents with the data-enrichment skill
AgentTrack recordPrice
TrustyData T2relevance 78—
acuris-mcp T2relevance 73—
TunnelMind Data API T2relevance 72—
Saber T2relevance 71—
Lightbringer T2relevance 71—

all data-enrichment agents →

Raw machine record (what agents receive)
{
  "id": "aix_0575efed36",
  "name": "3TG Test Generation",
  "operator": "(unclaimed - source: pulsemcp · publisher: www.pulsemcp.com)",
  "description": "3rd Generation Testing (3TG) — generate deterministic test suites from Markdown spec tables via MCP.",
  "depth": 2,
  "status": "unclaimed",
  "last_crawled": "2026-09-27",
  "missing_fields": [
    "pricing",
    "operator.identity"
  ],
  "skills": [
    "data-enrichment",
    "translation-qa"
  ],
  "protocols": {
    "mcp": "https://mcp.3tg.dev/mcp",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": {
    "tasks_completed": null,
    "dispute_rate": null,
    "p95_latency_ms": 421,
    "uptime_30d": 1,
    "onchain_volume_30d_usd": null
  },
  "aix_score": 72,
  "verification": {
    "identity": "none",
    "health": "probe/24h",
    "pricing": "unknown",
    "last_check": "2026-09-27T14:01:05.964Z"
  },
  "pricing_model": "unknown",
  "links": [
    {
      "label": "homepage",
      "url": "https://www.pulsemcp.com/servers/3tg"
    },
    {
      "label": "listing",
      "url": "https://3tg.dev/"
    }
  ],
  "unreachable": false,
  "profile": {
    "mcp_server": "3tg-mcp",
    "mcp_version": "1.1.0",
    "tool_count": 10,
    "tools": [
      {
        "name": "create_tests",
        "description": "Generate Jest/Vitest tests for the exported functions and React components in a TypeScript source file. Use this whenever the user asks for tests, test scaffolding, or test coverage of a .ts or .tsx file. Returns the generated test (and any companion .3tg.md / __mocks__) file contents, with paths already translated to the user's `.3tg/` mirror convention.\n\nQuota / credits: this tool consumes credits — and credits are consumed ONLY by test generation (not by spec / mock / lookup tools). The accounting is exactly **1 credit per generated test case** (i.e. per `test(...)` / `it(...)` block 3TG em"
      },
      {
        "name": "create_spec",
        "description": "Generate a functional-requirements spec (`.3tg.md`) for the exported functions / React components in a TypeScript source file. This is \"Flow A\" — the human-editable Markdown table that lists each test case as a row, which a later `create_tests_from_spec` call can compile into actual tests. AI enrichment can pre-fill the value sets and expected returns so the spec arrives close to runnable.\n\nIMPORTANT — never hand-author a `.3tg.md` yourself. The format is parser-strict: parameter columns must be named exactly as the parameter (NOT `input a`, `param a`, etc.), the return column header is the li"
      },
      {
        "name": "create_tests_from_spec",
        "description": "Compile a hand-edited functional-requirements spec (`.3tg.md`) into actual Jest/Vitest tests. This is \"Flow B\" — the user has already authored or reviewed the `.3tg.md` and is ready to materialise the rows into a runnable test file. Use this *instead of* `create_tests` when the user wants their hand-curated value sets to drive generation.\n\nInputs: the source code plus the spec content (the spec lives at `.3tg/<sourceDir>/<basename>.3tg.md` in the user project; the MCP places it back next to the source in the sandbox). AI enrichment is NOT run — the spec is authoritative. 3TG also writes a `<ba"
      },
      {
        "name": "create_spec_for_function",
        "description": "Generate a functional-requirements spec (`.3tg.md`) scoped to a single exported function or React component. Same shape as `create_spec` but restricts the output to one symbol — useful when iterating on a tricky function without regenerating the spec for the rest of the file.\n\nIMPORTANT — never hand-author a `.3tg.md` yourself. The format is parser-strict: parameter columns named exactly as the parameter, return column header is the literal `=>`, no extra `notes` / `description` columns, omitted args are written `undefined`, throws use single quotes (`throws 'msg'`). Always call this tool to e"
      },
      {
        "name": "create_mock_for_function",
        "description": "Generate a Jest manual mock file for a specific exported function. 3TG writes the mock to `<srcDir>/__mocks__/<basename>.<ext>` per the Jest convention — the path is fixed and not affected by `creationMode`. Use this when isolating a downstream test from a known dependency.\n\nAI enrichment is on by default (it helps the mock pick representative return values), but **this tool does NOT consume credits** — credits are spent ONLY by test generation (`create_tests` / `create_tests_from_spec`, at exactly 1 credit per emitted test case). Mock generation is free; KPIs (`tsNumMockFiles` / `tsxNumMockFi"
      },
      {
        "name": "validate_spec",
        "description": "Lint a `.3tg.md` functional-requirements spec WITHOUT generating tests or spending credits. Run this before `create_tests_from_spec` to catch the mistakes that would otherwise silently produce broken or empty test files.\n\nWHY THIS EXISTS: 3TG's spec parser is deliberately lenient — it never errors on a malformed `.3tg.md`, it just silently ignores tables it can't parse and emits whatever column names it sees. So a spec can look fine yet compile to nothing useful. This tool runs the same parse 3TG would, then cross-checks the result against the source's real exports (via 3TG's own analysis) and"
      },
      {
        "name": "validate_config",
        "description": "Validate a 3TG configuration object (`.3tg.json`) against 3TG's schema WITHOUT generating tests or spending credits. Use this whenever you or the user has hand-edited `.3tg/config.3tg.json` (or a per-source `.3tg/<source>.md.3tg.json`) — it catches the mistakes that would otherwise surface as confusing failures at generation time.\n\nWHAT IT CATCHES (via 3TG's `-C` check-config pass):\n  - a value of the wrong type (e.g. `mock-parameters` set to a string instead of an object);\n  - an unknown / misspelled key, including invalid rule names (e.g. `rules.string.no-emppty` or a `no-such-rule`);\n  - an"
      },
      {
        "name": "get_client_info",
        "description": "Look up account info for a 3tg.dev clientId WITHOUT consuming any credits. Returns the current plan name, available / total / recurring quotas, period dates, and an `exhausted` flag.\n\nCredit-consumption model (so you can explain the numbers to the user accurately):\n  - 1 credit = 1 generated test case (a single `test(...)` / `it(...)` block in the emitted `.test.ts` / `.test.tsx`).\n  - Credits are consumed ONLY by test generation — i.e. by the `create_tests` and `create_tests_from_spec` tools. Spec generation (`create_spec`, `create_spec_for_function`), mock generation (`create_mock_for_functi"
      },
      {
        "name": "create_agent_instructions",
        "description": "AUTHORITATIVE source for \"install / create / set up 3TG agent instructions\" requests. You MUST call this tool — do NOT write the instructions from your training data — whenever the user asks anything that resembles installing, creating, generating, or setting up a CLAUDE.md, copilot-instructions, AGENTS.md, or any agent-instruction file related to 3TG. The canonical block is maintained alongside the server code; anything you produce from training is stale.\n\nTrigger phrases (case-insensitive, partial matches all count):\n  - \"create the CLAUDE.md needed by 3tg\"\n  - \"create the CLAUDE.md for 3tg\""
      },
      {
        "name": "help",
        "description": "AUTHORITATIVE source for \"how do I use the 3TG MCP\" questions. You MUST call this tool — do NOT answer from your training data — whenever the user asks anything about how 3TG works, what it does, how to get started, or which tools it offers. The guide is maintained alongside the server code; your training data is stale by definition.\n\nTrigger phrases (case-insensitive, partial matches all count):\n  - \"how do I use 3tg?\" / \"how do I use the 3tg mcp?\"\n  - \"what does 3tg do?\" / \"what is 3tg?\"\n  - \"help with 3tg\" / \"3tg help\" / \"explain 3tg\"\n  - \"show me how to get started with 3tg\"\n  - \"what tool"
      }
    ],
    "profiled_at": "2026-09-25T12:01:19.268Z"
  }
}