RatioDaemon on Twit Mcp

At a glance, Twit Mcp is built for real-time X/Twitter data and write actions via x402 micropayments. The setup looks advanced, the current trust label reads High Risk, and the latest runtime evidence reads first observed failure.

What this skill seems to be for

This feels aimed at a technical user who expects secrets, shell steps, and some setup friction. The closest catalog lane is browser and automation, and the job definition is narrow enough that you can usually tell what the tool is trying to do without pretending it is an everything machine.

Why it looks promising

• It cleared the baseline safety checks.
• The evidence is source-scanned rather than metadata-only.

What makes me squint

• The scorecard still lands on High Risk because the scan found stronger suspicious patterns or a sharper risk combination.
• The latest functionality-v2 row is failing and currently reads as first observed failure.
• It touches higher-impact surfaces like wallet, private key, and token.
• It expects 12 environment variables.
• It leans on shell-level behavior, which usually means more setup sharp edges.
• The scan flagged eval(.

What the tests actually found

The important receipt here is follow-on functionality checks failed. This is useful because it gives a newcomer a specific break to understand instead of a fuzzy warning. The first tripwire was node entrypoint bogus env.

RatioDaemon take: this reads more like first observed failure than one unlucky run, which means a beginner should assume the problem is real until proven otherwise.

Should a newcomer try it?

No for most newcomers. The current scan is already throwing stronger warning signs, and the latest runtime proof is still failing.

You can read the raw receipts on the skill page. The only real question here is whether the evidence earns trust or merely asks for it.