io.github.TateLyman/x402-triage-mcp

Name: io.github.TateLyman/x402-triage-mcp
Author: io.github.TateLyman

MCPattested

v0.1.1io.github.TateLymanUnknownUpdated 4mo agonpm GitHub

MCP server for no-payment x402 surface triage, 402 Index health checks, and paid review handoff.

MCP server for no-payment x402 surface triage, 402 Index health checks, and paid review handoff. It exposes three MCP tools: checks one public x402, MPP, Pay.sh, OpenAPI, manifest, or HTTP 402 endpoint through the Tate Programs public triage API. searches public 402 Index metadata for provider health, payment-validity, and domain-verification signals. returns the paid x402 API endpoints, service…

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build

A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.

1GitHub stars

4mo agoLast update

Package

Authorio.github.TateLyman

LicenseUnknown

Version0.1.1

Sourcemcp-registry

npmx402-triage-mcp

GitHubTateLyman/x402-triage-mcp

SBOMCycloneDX 1.6 ↓

Trust Status

85/100Trusted

✓Listed in Forge index+10/10

✓Identity verified · attested build+20/20

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

✓npm Trusted Publishing (Sigstore)+5/5

—npm maintainer match+0/5

→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusIdentity verified

PublisherUnverified

SignatureUnsigned

Domain—

Provenance✓ Sigstore-verified · ea6b541

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface3 tools · none privileged

Security scan✓ Cleanv0.1.1 · 3mo agoHow well does this scan work?

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

3 tools · none privileged

Statically extracted from the published packagev0.1.1 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

triage_x402_surfaceNo description published

This tool published no description. Forge does not invent one.

watch_402_indexNo description published

This tool published no description. Forge does not invent one.

x402_paid_pathsNo description published

This tool published no description. Forge does not invent one.

0 of 3 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Keywords

mcp

Alternatives

Comparing tool surfaces…

io.github.TateLyman/x402-triage-mcp

Tools

Tools exposed

No dependency coverage